-
Notifications
You must be signed in to change notification settings - Fork 62
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
Migrate from setup.py to pyproject.toml #315
Conversation
90252cf
to
f7e80f5
Compare
f7e80f5
to
6a2443d
Compare
Hi @danyeaw, thank you for this PR! I took some time to look over the changes and tested it myself and everything was working well on my end. I will go ahead and merge this! As a side note, I noticed a consistent increase in the build time, even after the initial editable install. This led me to look at |
Hi @RRosio, thanks for reviewing, testing, and merging the PR! Great point on the performance. One thing that will slow things down a bit is the new npm scripts are not taking in to account whether a rebuild is needed based on timestamps, and it is just rebuilding everything. However, the building of the JavaScript, CSS, and translations takes less than 10 seconds on my MacBook. We could make this a bit smarter if we wanted. I have a feeling that the performance issue is because Hatch is traversing all folders and files, and I noticed that there is an option around this here under a performance section: I added this to the TODO list on the issue, and I'll investigate more if that is the cause and if we can tweak the settings. |
This PR is part of #307 to replace the setup.py with a pyproject.toml.
package.json
pyproject.toml
Since I have never done a release with Jupyter Releaser, I could use some guidance on how to test this.
I used wheeldiff to compare the wheels created by the setup.py build and this new one. Both wheels are 25.6MB: