-
-
Notifications
You must be signed in to change notification settings - Fork 67
Upload wheels to PyPI #37
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
Comments
Hi there, I have an issue with I'm guessing that missing I'm going to try to publish wheel file on our private registry and will keep you posted if it helps solving my probelm. |
nevermind, it's absolutely not related. My problem was due to a conflict with |
Installing I'm getting following error
|
Would you be interested in help by creating a PR that included support for uploading wheels of this package? |
@Ambro17 : are we sure this repo is maintained and PR will be merged ? If so, I can do it |
No, i'm not sure but it's a dependency on the third most used web framework in python so i think it's worth the try |
Conditions look favorable. |
Hi @tomchristie, I'm having a look at the CI part of this repo and can't find anything related to package build. Do you know how build is currently done ? |
Hrmm, it's been a while... https://pypi.org/project/python-multipart/#history I assume we've always released manually in the past. The instructions at the top of this thread look useful. #37 (comment) |
This section of the tutorial might be relevant too. Packaging in python has improved a lot lately so one can not depend on setuptools if one doesn't want to. |
Yep, this is the way :) What i can do in the PR is add an action when a tag is pushed to the repo that will build & publish package to PyPi. What do you think about that? |
I just saw that this issue got opened today : #50 Could be a good idea as you suggested to also move setup.py to pyproject.toml |
First PR opened : #52 Review appreciated :) |
Prompted by #40 (comment) Supposing we wanted pushed a new release now...
|
@tomchristie latest relase (0.0.5) is based on py==1.10 which has a reported, unclosed CVE. While this might be a really weird issue (if you read into the whole drama regarding py module, pytest and the recent CVE publication) it is a pain when you have to explain this to every single security guy in your organization... |
Any progress on this? |
give me 10 min, hold on EDIT: ok, give me a bit more... I'll make a release in some hours. |
Automated? I'm using pants on an M1 and it requires wheels, at the moment I'm just vendoring it myself so no rush :) |
I was going to make a manual release, since we can't use this flow: #57 If you have a suggestion about a flow that could work, and want to push a PR, I'd check it... 👀 |
On tag? The issue is that you can't make releases on @andrew-d 's repo? |
That would work, yep.
Yep. I can't make GH releases. |
Did you want a PR raised to change this to be release on tag? |
There they are! 🚀 Thanks @Kludex ❤️ |
I just did
But my
is it 1.0.9 or 0.0.9 I tried 0.0.9 manually before but got an error on
|
Uh oh!
There was an error while loading. Please reload this page.
Wheels (
.whl
) for this package are currently missing from PyPI. Could wheels be uploaded for the current and future releases?Read more about the advantages of wheels to understand why generating wheel distributions are important.
To create a wheel along with source distribution:
(venv) $ pip install --upgrade pip setuptools wheel (venv) $ python setup.py sdist bdist_wheel # See dist/*.whl
To upload wheels:
(venv) $ pip install twine (venv) $ twine upload dist/*
The text was updated successfully, but these errors were encountered: