-
Notifications
You must be signed in to change notification settings - Fork 72
Pin to click<8.2.0, pin pypiserver based on the Python version
#607
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.
Thank you!
|
The |
| - uses: jupyterlab/maintainer-tools/.github/actions/base-setup@v1 | ||
| with: | ||
| dependency_type: pre | ||
| python_version: "3.12" |
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.
As noticed in #610, the job does not complete on 3.13. And with 3.12 we need the click<8.2.0 pin.
|
Running the tests locally hints at the following: Because of the exact pin on: jupyter_releaser/pyproject.toml Line 35 in 9e9abaf
And |
pyproject.toml
Outdated
| "packaging", | ||
| "pkginfo", | ||
| "pypiserver==2.2.0", | ||
| "pypiserver", |
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.
We'll probably hit pypiserver/pypiserver#630 now, let's see what CI says.
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.
Well, the problem is that this was only manifesting in JupyterLab as it has larger tarballs, so CI status here will not be super helpful.
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.
Oh well, I guess it now passes because of the new bottle==0.13.3 released April 21, 2025: https://pypi.org/project/bottle/0.13.3/
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.
I guess we could do pins conditional on Python version? So we pin to 2.2.0 on anything older than 3.13 and allow any version on 3.13 (and it should work for most repos, but not for repos with tarballs the size of lab).
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.
Ah, right pypiserver/pypiserver#630 is still open but a patch is out. So if it breaks we can now just set PYPISERVER_BOTTLE_MEMFILE_MAX_OVERRIDE_BYTES, perfect!
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.
I don't think it is tied to bottle releases as pypiserver is vendoring bottle, the patch is pypiserver/pypiserver#636.
Now I wonder, should we set PYPISERVER_BOTTLE_MEMFILE_MAX_OVERRIDE_BYTES to 100 MB to match PyPI?
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.
I don't think it is tied to
bottlereleases aspypiserveris vendoringbottle, the patch is pypiserver/pypiserver#636.
But this patch is not yet available in a pypiserver release it seems?
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.
Yes, It looks like there was no release since it was merged https://pypi.org/project/pypiserver/#history
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.
So is there anything more to be done for now until a new release is available, apart from pinning on Python versions (aada747)?
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.
No, I think we can merge :)
|
Also https://github.com/jupyter-server/jupyter_releaser/blob/main/.github/workflows/check-release.yml does not seem to be running anymore. Edit: Looks like it was automatically disabled, so I re-enabled it. |
click<8.2.0, remove pypiserver pinclick<8.2.0, pin pypiserver based on the Python version


Temporary workaround for #606
Maybe we need to fix our usage of
click, or maybeclickwill publish a fix for it.In the meantime we can pin
clickto unblock repos using the releaser.