-
Notifications
You must be signed in to change notification settings - Fork 30
Use an all pyproject.toml setup #297
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the manifest still necessary with pyproject.toml?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sadly we do. We have more control over the sdist with the MANIFEST. We can remove it and the sdist will be fine but we would be packaging some junk and making it a bit big. B/c PyPI has some size limitations I like to keep them small.
|
I'll address the docs failures in another PR, this one is already too big for its own sake.. This should be ready to go but I'd like to highlight this commits here in case it causes us problem in the future: ccfa937 Hopefully that addresses the memory leak caused by creating too many instances of the class without hurting the cache. |
|
@abkfenris thanks for the dynamic requirement file tip. Looks much cleaner now! |
I also moved the linting to ruff.