-
Is it possible to upload the current version to PyPI?
There is the "ImportError: No module named 'md5'" error on the PyPI release what breaks installation for py3. ATM i'm porting talon to py3. talon …
-
Installing from pypi can be simpler and more user friendly than cloning and running some scripts.
-
The build server should push to PyPI when we commit a new tag.
-
### Problem description
This feature should be very similar to what poetry has right now. By typing 'pixi publish', user should be able to upload their package to pypi or similar organizations.
…
-
We should document the actual process to create a release and get it pushed to pypi.
This is currently not fully automated or documented, as far as i can see.
-
I thought the pypi upload is just broken somehow but a quick look tells me it was intentionally removed in https://github.com/vapoursynth/vapoursynth/commit/4e45c5b21006ddf4864ae63c2cedc7366def3408
-
Now that we have switched to wheels for packages, our current distribution model reaches its limits as it doesn't allow,
- having multiple available versions of a package for a given Python/Emscript…
-
It's just a little bit easier to install than using a Git link.
-
Now I run these steps manually and they could as well be automatic.
-
Just following up after doing a pip install on another machine and it pulled 1.0.1 which doesn't include the Python 3 update. Sorry to bug you about it.