Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guidelines on what to import in __init__.py #384

Open
soininen opened this issue Apr 9, 2024 · 0 comments
Open

Guidelines on what to import in __init__.py #384

soininen opened this issue Apr 9, 2024 · 0 comments

Comments

@soininen
Copy link
Collaborator

soininen commented Apr 9, 2024

Discussed in the developer meeting 2024-04-09.

We import certain functions/classes/etc. in spinedb_api.__init__ so client code can import that stuff more easily, e.g. use from spinedb_api import DatabaseMapping instead of from spinedb_api.db_mapping import DatabaseMapping.

We do not want everything to be available in __init__.py so what should we import there? Some ideas from the developer meeting:

  • Core classes/functions:
    • Things that are specifically mentioned in the API reference
    • Selected functionality from spinedb_api.filters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant