PyPI support about i18nice HOT 11 CLOSED

Published as i18nice 🎉

from i18nice.

Hi

You're messing the ways of installing from git. Either of these two lines should work:
https://github.com/Krutyi-4el/python-i18n/archive/master.zip (without the git+!)

git+https://github.com/Krutyi-4el/python-i18n

I wasn't planning on publishing the package. It may be a good idea in the future, though.

from i18nice.

Indeed, I wasn't using the requirements file correctly.
Thanks for your help.

from i18nice.

Mind creating a tag meanwhile ?

from i18nice.

Just for the sake of sanity, using https://github.com/Krutyi-4el/python-i18n/archive/master.zip in requirements.txtwill end up with pkg_resources.extern.packaging.requirements.InvalidRequirement: Parse error at "'+https:/'": Expected string_end error.
The same applies when using the git+ form.

The syntax in requirements.txt needs to be:

python-i18n@https://github.com/Krutyi-4el/python-i18n/archive/master.zip

But then pypi package uploads will fail.
Unless you publish your package, one cannot use it in a requirements.txt file for both pypi and local setups.

from i18nice.

Looks like bizarre issue for me. However, I've never worked with PyPi.

from i18nice.

Btw, have you tried using commit hash or tag instead of branch name? Maybe PyPI doesn't allow branches to ensure dependency locking.

from i18nice.

Actually, it ends up with the following error message when trying to upload to PyPI

WARNING  Error during upload. Retry with the --verbose option for more details.
ERROR    HTTPError: 400 Bad Request from https://test.pypi.org/legacy/
         Invalid value for requires_dist. Error: Can't have direct dependency: 'python-i18n @ https://github.com/Krutyi-4el/python-i18n/archive/master.zip'

I've also tried following syntax as per PEP-0440 in requirements.txt:

python-i18n @ git+https://github.com/Krutyi-4el/[email protected]#8999a0d380be8a08beed785e46fbb31dfc03c605

Ends up the same. Reading PEP-0440, it states

Public index servers SHOULD NOT allow the use of direct references in uploaded distributions. Direct references are intended as a tool for software integrators rather than publishers.

It seems that twine just doesn't allow uploading packages to PyPI with direct references

I'm stuck for now. I only can directly bundle your python-i18n package directly into my app as workaround unless you can publish something on PyPI, even a python-i18n-v2 or so package.

from i18nice.

Hm, I see. I can also suggest another workaround: try adding my repository as a git submodule.

from i18nice.

Yeah... But multiplying different dependencies system doesn't seem healthy to me.
Any chance you're making a PyPI release ?

from i18nice.

Thank you for the time and effort you put into this ;)

from i18nice.