-
Notifications
You must be signed in to change notification settings - Fork 4
modernize: native namespace, pyproject.toml, py39+, src/, ... #14
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
63a41a1 to
efc819b
Compare
8333d9c to
be2f0f1
Compare
|
Looks like for Python 3.11+, xstatic 2.0.0 can't support legacy xstatic resource packages - when trying to install 2 legacy ones, the 2nd one will fail to install. |
|
@ReimarBauer @deshipu @jayvdb @RogerHaase @UlrichB22 @roland-ruedenauer Please review. |
This only happens with pip installation from source tree. Legacy XStatic wheels from pypi can still be installed. But the known issue with use of |
930da5f to
77c37bf
Compare
note: this is broken, because pyproject.toml does not support pkg_resources style namespace-packages any more!
pkg_resources style was deprecated since long and pyproject.toml has removed support for namespace-packages completely.
77c37bf to
6f48fbb
Compare
|
@roland-ruedenauer I tried in a separate, fresh venv and my impression is that it only works sometimes: |
Looks as if you did not clean the pip cache. |
|
What about making XStatic |
|
Just trying On pypi we have currently only the old XStatic-Font-Awesome. I had no trouble to install it together with the modernized XStatic. From #15 this should not work, or? I could also use the old API https://xstatic.readthedocs.io/en/latest/using.html#example-code-to-setup-local-file-serving |
|
@ReimarBauer The trouble with legacy packages often only showed when trying to install multiple of them. |
|
@roland-ruedenauer It's not related to the cache:
|
|
I have not upgrade pip, will do another one with the upgrade |
|
@ThomasWaldmann It's like I said before: you run into the problem with installing legacy XStatic packages from source distributions. Using wheels should be no problem. This time you picked a package that has no wheel deployed on pypi.
|
|
I did a mistake. I was not on the most recent version. sorry for that. |
|
With the recent changes, I get same trouble too. |
|
XStatic-Bootstrap 4.5.3.1 also has no wheel deployed on pypi |
likly conclusion deploy wheels first |
|
Because of the problematic with use of |
|
@ThomasWaldmann Is there anything left to do preventing a merge into master? |
|
@roland-ruedenauer Guess it can be merged into master, but before doing a pypi release, I would like more feedback about how we proceed (in #15) to avoid that project using xstatic packages run into troubles. |
|
From my pov: relelasing wheels to pypi for old packages (where possible) and your explicit hints should be sufficient. |
|
Perhaps it would help to create a pre-release version in pipy for testing. |
|
@UlrichB22 Could be done, but is quite some work as we would need all the required packages there. pip can also pull code directly from a github branch, so that might also work well enough for pre-release testing. |
xstatic 2.0.0
Fixes #12. Fixes #4. Fixes #7. Fixes #9.
See also #15 for migration hints.