pypa/pip

Deprecate legacy versions and version specifiers

sbidoul opened this issue ยท 97 comments

sbidoul commented

Towards #11715

What is changing

pip has historically allowed many arbitrary strings as versions and version specifiers. Going forward, all versions and version specifiers will need to conform to https://packaging.python.org/en/latest/specifications/version-specifiers/ (based on PEP 440).

Quoting pypa/packaging#530:

>>> packaging.version.parse("This is a completely random string")
<LegacyVersion('This is a completely random string')>

>>> packaging.version.parse("This is a completely random string")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "[...]/.venv/lib/python3.10/site-packages/packaging/version.py", line 52, in parse
    return Version(version)
  File "[...]/.venv/lib/python3.10/site-packages/packaging/version.py", line 197, in __init__
    raise InvalidVersion(f"Invalid version: '{version}'")
packaging.version.InvalidVersion: Invalid version: 'This is a completely random string'

This "feature" has been deprecated (pypa/packaging#321) for nearly two years now.

PyPI has not permitted uploading packages with invalid versions for even more years.

There are more details about this change in the aforementioned issue.

What you can do

Please do not comment on this issue with the message you're seeing.

x-ref https://pradyunsg.me/blog/2024/05/13/pip-24-1-betas/

If you reached this issue from the pip deprecation warning and lack information to know where the non-conforming string was used, please re-run your pip command with -v or -vv to show more detailed logs which will help in locating the problem.

If you are the user of a package that is causing pip to present this warning, reach out to the authors of the package. The message starts as DEPRECATION: [package name here] [version number here] has a non-standard [...].

If you are the author of the relevant package, please update your package version and dependency specifiers to use a compliant syntax. You can check those using packaging.version.parse("1.0") and packaging.requirements.Requirement("dependency >= 1.0") with the latest packaging release.

wescorp commented

DEPRECATION: torchsde 0.2.5 has a non-standard dependency specifier numpy>=1.19.*; python_version >= "3.7". pip 23.3 will enforce this behaviour change.

pfmoore commented

DEPRECATION: torchsde 0.2.5 has a non-standard dependency specifier

See #12146 - please report to torchsde

Edit: Looks like it's been reported as google-research/torchsde#131

  • ๐Ÿ‘2
uranusjr commented

Sorry, working on the wrong tab

asanka550-HACKER commented

DEPRECATION: masonite 4.17.4 has a non-standard dependency specifier watchdog>=2<3. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of masonite or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at #12063

  • ๐Ÿ˜•1
asanka550-HACKER commented

Help me..๐Ÿ˜ฅ

sbidoul commented

@asanka550-HACKER please reach out to the masonite project to ask them to fix their dependency specifiers.

eslerm commented

Is PEP 440 meant to override the version numbering schema of all downstreams? Will you make this feautre opt-out?

DEPRECATION: python-debian 0.1.43ubuntu1 has a non-standard version number. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of python-debian or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at https://github.com/pypa/pip/issues/12063
  • ๐Ÿ‘3
  • ๐Ÿ‘Ž2
FrostyNick commented

Is PEP 440 meant to override the version numbering schema of all downstreams? Will you make this feautre opt-out?

DEPRECATION: python-debian 0.1.43ubuntu1 has a non-standard version number. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of python-debian or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at https://github.com/pypa/pip/issues/12063

Updating the package seems to fix the issue. In my case, this also showed up for distro-info.
pip3 install python-debian distro-info -U

There should be a good error message when this is enforced in pip 23.3; not sure how this will be affected after the update.

  • โค๏ธ2
tfpf commented

Along with python-debian, the warning message is shown for gpg, too. On my system, updating it required the installation of some additional packages. Documenting here for anyone who comes by.

sudo apt install libgpgme-dev swig
pip install --upgrade gpg
  • ๐Ÿ‘15
  • โค๏ธ6
  • ๐Ÿš€2
evizcaino123 commented

Hi, I am facing issues downloading matlabengineforpython and pytorch-lightning. Both of these packages are required for another package so I cannot just download alternitives.

DEPRECATION: matlabengineforpython R2021a has a non-standard version number. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of matlabengineforpython or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at #12063
DEPRECATION: pytorch-lightning 1.6.4 has a non-standard dependency specifier torch>=1.8.*. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of pytorch-lightning or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at #12063

This is being built within a conda enviroment.

pradyunsg commented

@evizcaino123 Please reach out to the maintainers of pytorch-lightning and matlabengineforpython about this issue.

pradyunsg commented

@tfpf @eslerm @FrostyNick

python-debian

See https://bugs.launchpad.net/ubuntu/+source/distro-info/+bug/1991606 which tracks the Ubuntu-side work on this issue.

  • ๐Ÿ‘1
eslerm commented

Thank you for the information @pradyunsg.

Could the Python Packaging Authority please answer my questions above? I am worried that my comment will be hidden if I do not ask again.

edit: this satisfies my questions pypa/setuptools#3772 (comment)

  • ๐Ÿ‘Ž1
pradyunsg commented

Will you make this feautre opt-out?

No.

Is PEP 440 meant to override the version numbering schema of all downstreams?

No. Downstream tooling (eg: apt, yum) can use whatever versioning scheme they wish to use. The METADATA for the Python packages needs to be compliant with PEP 440 though -- it's similar to how Debian/Ubuntu can't set arbitrary version strings for npm packages or Rust crates they use, those need to comply with SemVer.

  • โค๏ธ3
Deleted user commented

gettting pep 517 on mac

  • ๐Ÿ‘Ž1
Amazon90 commented 
`C:\Users\28622>pip install --upgrade omegaconf
Requirement already satisfied: omegaconf in c:\users\28622\appdata\local\programs\python\python310\lib\site-packages (2.0.6)
Collecting omegaconf
  Downloading omegaconf-2.3.0-py3-none-any.whl (79 kB)
     โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ” 79.5/79.5 kB 119.8 kB/s eta 0:00:00
Collecting antlr4-python3-runtime==4.9.* (from omegaconf)
  Downloading antlr4-python3-runtime-4.9.3.tar.gz (117 kB)
     โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ” 117.0/117.0 kB 200.7 kB/s eta 0:00:00
  Preparing metadata (setup.py) ... done
Requirement already satisfied: PyYAML>=5.1.0 in c:\users\28622\appdata\local\programs\python\python310\lib\site-packages (from omegaconf) (6.0.1)
Building wheels for collected packages: antlr4-python3-runtime
  Building wheel for antlr4-python3-runtime (setup.py) ... done
  Created wheel for antlr4-python3-runtime: filename=antlr4_python3_runtime-4.9.3-py3-none-any.whl size=144578 sha256=4e1eba93687bcd4a45ca7e2a12da37f6af88ac54b41a3c4599f7d946bb5ee74e
  Stored in directory: c:\users\28622\appdata\local\pip\cache\wheels\12\93\dd\1f6a127edc45659556564c5730f6d4e300888f4bca2d4c5a88
Successfully built antlr4-python3-runtime
Installing collected packages: antlr4-python3-runtime, omegaconf
  Attempting uninstall: antlr4-python3-runtime
    Found existing installation: antlr4-python3-runtime 4.8
    Uninstalling antlr4-python3-runtime-4.8:
      Successfully uninstalled antlr4-python3-runtime-4.8
  Attempting uninstall: omegaconf
    Found existing installation: omegaconf 2.0.6
    Uninstalling omegaconf-2.0.6:
      Successfully uninstalled omegaconf-2.0.6
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
fairseq 0.12.2 requires omegaconf<2.1, but you have omegaconf 2.3.0 which is incompatible.
hydra-core 1.0.7 requires antlr4-python3-runtime==4.8, but you have antlr4-python3-runtime 4.9.3 which is incompatible.
hydra-core 1.0.7 requires omegaconf<2.1,>=2.0.5, but you have omegaconf 2.3.0 which is incompatible.
Successfully installed antlr4-python3-runtime-4.9.3 omegaconf-2.3.0

C:\Users\28622>pip install omegaconf==2.0.5
Collecting omegaconf==2.0.5
  Downloading omegaconf-2.0.5-py3-none-any.whl (36 kB)
Requirement already satisfied: PyYAML>=5.1.* in c:\users\28622\appdata\local\programs\python\python310\lib\site-packages (from omegaconf==2.0.5) (6.0.1)
Requirement already satisfied: typing-extensions in c:\users\28622\appdata\local\programs\python\python310\lib\site-packages (from omegaconf==2.0.5) (4.7.0)
DEPRECATION: omegaconf 2.0.5 has a non-standard dependency specifier PyYAML>=5.1.*. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of omegaconf or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at https://github.com/pypa/pip/issues/12063
Installing collected packages: omegaconf
  Attempting uninstall: omegaconf
    Found existing installation: omegaconf 2.3.0
    Uninstalling omegaconf-2.3.0:
      Successfully uninstalled omegaconf-2.3.0
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
hydra-core 1.0.7 requires antlr4-python3-runtime==4.8, but you have antlr4-python3-runtime 4.9.3 which is incompatible.
Successfully installed omegaconf-2.0.5

C:\Users\28622>pip install omegaconf==2.1.0
Collecting omegaconf==2.1.0
  Downloading omegaconf-2.1.0-py3-none-any.whl (74 kB)
     โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ” 74.5/74.5 kB 117.5 kB/s eta 0:00:00
Collecting antlr4-python3-runtime==4.8 (from omegaconf==2.1.0)
  Downloading antlr4-python3-runtime-4.8.tar.gz (112 kB)
     โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ” 112.4/112.4 kB 654.9 kB/s eta 0:00:00
  Preparing metadata (setup.py) ... done
Requirement already satisfied: PyYAML>=5.1.* in c:\users\28622\appdata\local\programs\python\python310\lib\site-packages (from omegaconf==2.1.0) (6.0.1)
Building wheels for collected packages: antlr4-python3-runtime
  Building wheel for antlr4-python3-runtime (setup.py) ... done
  Created wheel for antlr4-python3-runtime: filename=antlr4_python3_runtime-4.8-py3-none-any.whl size=141217 sha256=a91301742afff199d15e0e17af573f50197bf8c060267fe4a58f45c1fca774e6
  Stored in directory: c:\users\28622\appdata\local\pip\cache\wheels\a7\20\bd\e1477d664f22d99989fd28ee1a43d6633dddb5cb9e801350d5
Successfully built antlr4-python3-runtime
DEPRECATION: omegaconf 2.1.0 has a non-standard dependency specifier PyYAML>=5.1.*. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of omegaconf or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at https://github.com/pypa/pip/issues/12063
Installing collected packages: antlr4-python3-runtime, omegaconf
  Attempting uninstall: antlr4-python3-runtime
    Found existing installation: antlr4-python3-runtime 4.9.3
    Uninstalling antlr4-python3-runtime-4.9.3:
      Successfully uninstalled antlr4-python3-runtime-4.9.3
  Attempting uninstall: omegaconf
    Found existing installation: omegaconf 2.0.5
    Uninstalling omegaconf-2.0.5:
      Successfully uninstalled omegaconf-2.0.5
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
fairseq 0.12.2 requires omegaconf<2.1, but you have omegaconf 2.1.0 which is incompatible.
hydra-core 1.0.7 requires omegaconf<2.1,>=2.0.5, but you have omegaconf 2.1.0 which is incompatible.
Successfully installed antlr4-python3-runtime-4.8 omegaconf-2.1.0

C:\Users\28622>pip install omegaconf==2.0.6
Collecting omegaconf==2.0.6
  Downloading omegaconf-2.0.6-py3-none-any.whl (36 kB)
Requirement already satisfied: PyYAML>=5.1.* in c:\users\28622\appdata\local\programs\python\python310\lib\site-packages (from omegaconf==2.0.6) (6.0.1)
Requirement already satisfied: typing-extensions in c:\users\28622\appdata\local\programs\python\python310\lib\site-packages (from omegaconf==2.0.6) (4.7.0)
DEPRECATION: omegaconf 2.0.6 has a non-standard dependency specifier PyYAML>=5.1.*. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of omegaconf or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at https://github.com/pypa/pip/issues/12063
Installing collected packages: omegaconf
  Attempting uninstall: omegaconf
    Found existing installation: omegaconf 2.1.0
    Uninstalling omegaconf-2.1.0:
      Successfully uninstalled omegaconf-2.1.0
Successfully installed omegaconf-2.0.6`

Always give me the following warning and I don't know how to do.
DEPRECATION: omegaconf 2.0.6 has a non-standard dependency specifier PyYAML>=5.1.*. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of omegaconf or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at #12063

sbidoul commented

DEPRECATION: omegaconf 2.1.0 has a non-standard dependency specifier PyYAML>=5.1.*. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of omegaconf or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at #12063

@Amazon90 please contact the omagaconf project so they fix their dependencies.

zhenhuashao commented

DEPRECATION: ansys-dpf-core 0.8.1 has a non-standard dependency specifier ansys-dpf-gate>=0.3.*. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of ansys-dpf-core or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at #12063

moseti1 commented

DEPRECATION: torchsde 0.2.5 has a non-standard dependency specifier numpy>=1.19.*; python_version >= "3.7". pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of torchsde or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at #12063

  • ๐Ÿ‘€1
pradyunsg commented

I've added "Please do not comment on this issue with the message you're seeing." to the OP.

@moseti1 Please reach out to the maintainers of torchsde.

@zhenhuashao Please reach out to the maintainers of ansys-dpf-core.

  • ๐Ÿ‘1
  • โค๏ธ1
marshalleq commented

I'm a bit of a python noob and came here from the link in failing code. What would be useful rather than just saying go to maintainers is to provide that link. So this is my attempt to do that, though please advise if I have this incorrect.

Maintainers of torchsde are: https://github.com/google-research/torchsde yes?

pfmoore commented

That looks right, yes. We sometimes don't include the link, simply because we may not know (we aren't particularly familiar with most of the packages people use).

  • ๐Ÿ‘2
Jaxsii commented

I'm a bit of a python noob and came here from the link in failing code. What would be useful rather than just saying go to maintainers is to provide that link. So this is my attempt to do that, though please advise if I have this incorrect.

Maintainers of torchsde are: https://github.com/google-research/torchsde yes?

Check this google-research/torchsde#131

  • ๐Ÿ‘1
anupamjamatia commented

Hi, I have tried to install as per the command provided in the site. I have used :
pip install -r requirements.txt && pip install -e .

but it shows some subprocess error like :

an@aj:~/Desktop/Multimodal_SA_Work/resp$ pip install -r requirements.txt && pip install -e . 
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: async-generator==1.10 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 1)) (1.10)
Requirement already satisfied: attrs==21.4.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 2)) (21.4.0)
Requirement already satisfied: beautifulsoup4==4.11.1 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 3)) (4.11.1)
Requirement already satisfied: certifi==2022.6.15 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 4)) (2022.6.15)
Requirement already satisfied: cffi==1.15.1 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 5)) (1.15.1)
Requirement already satisfied: charset-normalizer==2.1.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 6)) (2.1.0)
Requirement already satisfied: cryptography==37.0.4 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 7)) (37.0.4)
Requirement already satisfied: google-search-results==2.4.1 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 8)) (2.4.1)
Requirement already satisfied: h11==0.13.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 9)) (0.13.0)
Requirement already satisfied: idna==3.3 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 10)) (3.3)
Requirement already satisfied: latexcodec==2.0.1 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 11)) (2.0.1)
Requirement already satisfied: outcome==1.2.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 12)) (1.2.0)
Requirement already satisfied: pandas in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 13)) (1.5.3)
Requirement already satisfied: numpy in /usr/local/lib/python3.8/dist-packages (from -r requirements.txt (line 14)) (1.22.2)
Requirement already satisfied: pybtex==0.24.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 15)) (0.24.0)
Requirement already satisfied: pycparser==2.21 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 16)) (2.21)
Requirement already satisfied: pyOpenSSL==22.0.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 17)) (22.0.0)
Requirement already satisfied: PySocks==1.7.1 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 18)) (1.7.1)
Requirement already satisfied: python-dateutil==2.8.2 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 19)) (2.8.2)
Requirement already satisfied: pytz==2022.1 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 20)) (2022.1)
Requirement already satisfied: PyYAML==6.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 21)) (6.0)
Requirement already satisfied: requests==2.28.1 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 22)) (2.28.1)
Requirement already satisfied: selenium==4.2.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 23)) (4.2.0)
Requirement already satisfied: shutup==0.2.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 24)) (0.2.0)
Requirement already satisfied: six==1.16.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 25)) (1.16.0)
Requirement already satisfied: sniffio==1.2.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 26)) (1.2.0)
Requirement already satisfied: sortedcontainers==2.4.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 27)) (2.4.0)
Requirement already satisfied: soupsieve==2.3.2.post1 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 28)) (2.3.2.post1)
Requirement already satisfied: tqdm==4.64.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 29)) (4.64.0)
Requirement already satisfied: trio==0.21.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 30)) (0.21.0)
Requirement already satisfied: trio-websocket==0.9.2 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 31)) (0.9.2)
Requirement already satisfied: urllib3==1.26.10 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 32)) (1.26.10)
Requirement already satisfied: wsproto==1.1.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 33)) (1.1.0)
Defaulting to user installation because normal site-packages is not writeable
Obtaining file:///home/anupam/Desktop/Work/resp
  Preparing metadata (setup.py) ... done
Installing collected packages: resp
  Running setup.py develop for resp
    error: subprocess-exited-with-error
    
    ร— python setup.py develop did not run successfully.
    โ”‚ exit code: 1
    โ•ฐโ”€> [4 lines of output]
        running develop
        running egg_info
        creating resp.egg-info
        error: could not create 'resp.egg-info': Permission denied
        [end of output]
    
    note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

ร— python setup.py develop did not run successfully.
โ”‚ exit code: 1
โ•ฐโ”€> [4 lines of output]
    running develop
    running egg_info
    creating resp.egg-info
    error: could not create 'resp.egg-info': Permission denied
    [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.

Please help me in this regard

pradyunsg commented

Hi @anupamjamatia! This isn't the right place to ask for help for the problem you're facing.

I think that Python Discord's #help-* channels, python-list or python-tutor mailing lists, or StackOverflow would be better channels to get support for the issue you're facing.

Also, your comment seems to be poorly formatted. I request you to read https://help.github.com/articles/getting-started-with-writing-and-formatting-on-github/ -- for now, I've manually improved the formatting of your comment by editing it in place, using the pencil icon in the corner. :)

anupamjamatia commented

Ok, that has been solved after changing the access mode.
But now after successfully installation of resp, I am not able to run the software. Can anyone help me how to run the code to get all the paper information from ACL Anthology?

Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: async-generator==1.10 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 1)) (1.10)
Requirement already satisfied: attrs==21.4.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 2)) (21.4.0)
Requirement already satisfied: beautifulsoup4==4.11.1 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 3)) (4.11.1)
Requirement already satisfied: certifi==2022.6.15 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 4)) (2022.6.15)
Requirement already satisfied: cffi==1.15.1 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 5)) (1.15.1)
Requirement already satisfied: charset-normalizer==2.1.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 6)) (2.1.0)
Requirement already satisfied: cryptography==37.0.4 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 7)) (37.0.4)
Requirement already satisfied: google-search-results==2.4.1 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 8)) (2.4.1)
Requirement already satisfied: h11==0.13.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 9)) (0.13.0)
Requirement already satisfied: idna==3.3 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 10)) (3.3)
Requirement already satisfied: latexcodec==2.0.1 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 11)) (2.0.1)
Requirement already satisfied: outcome==1.2.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 12)) (1.2.0)
Requirement already satisfied: pandas in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 13)) (1.5.3)
Requirement already satisfied: numpy in /usr/local/lib/python3.8/dist-packages (from -r requirements.txt (line 14)) (1.22.2)
Requirement already satisfied: pybtex==0.24.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 15)) (0.24.0)
Requirement already satisfied: pycparser==2.21 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 16)) (2.21)
Requirement already satisfied: pyOpenSSL==22.0.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 17)) (22.0.0)
Requirement already satisfied: PySocks==1.7.1 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 18)) (1.7.1)
Requirement already satisfied: python-dateutil==2.8.2 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 19)) (2.8.2)
Requirement already satisfied: pytz==2022.1 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 20)) (2022.1)
Requirement already satisfied: PyYAML==6.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 21)) (6.0)
Requirement already satisfied: requests==2.28.1 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 22)) (2.28.1)
Requirement already satisfied: selenium==4.2.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 23)) (4.2.0)
Requirement already satisfied: shutup==0.2.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 24)) (0.2.0)
Requirement already satisfied: six==1.16.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 25)) (1.16.0)
Requirement already satisfied: sniffio==1.2.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 26)) (1.2.0)
Requirement already satisfied: sortedcontainers==2.4.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 27)) (2.4.0)
Requirement already satisfied: soupsieve==2.3.2.post1 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 28)) (2.3.2.post1)
Requirement already satisfied: tqdm==4.64.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 29)) (4.64.0)
Requirement already satisfied: trio==0.21.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 30)) (0.21.0)
Requirement already satisfied: trio-websocket==0.9.2 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 31)) (0.9.2)
Requirement already satisfied: urllib3==1.26.10 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 32)) (1.26.10)
Requirement already satisfied: wsproto==1.1.0 in /home/anupam/.local/lib/python3.8/site-packages (from -r requirements.txt (line 33)) (1.1.0)
Defaulting to user installation because normal site-packages is not writeable
Obtaining file:///home/anupam/Desktop/Multimodal_SA_Work/resp
Preparing metadata (setup.py) ... done
Installing collected packages: resp
Attempting uninstall: resp
Found existing installation: resp 0.0.0
Uninstalling resp-0.0.0:
Successfully uninstalled resp-0.0.0
Running setup.py develop for resp
Successfully installed resp-0.0.0

pfmoore commented

You need to ask in one of the places @pradyunsg suggested, not here.

Sabyaro commented

I can not be able to understand how can I solve this problem. If any could give me a solution then I will be grateful for that. My terminal shows this type of message.

"dresden@dresden:~$ pip install beautifulsoup4
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: beautifulsoup4 in /usr/local/lib/python3.10/dist-packages (4.12.0)
Requirement already satisfied: soupsieve>1.2 in /usr/local/lib/python3.10/dist-packages (from beautifulsoup4) (2.4)
DEPRECATION: distro-info 1.1build1 has a non-standard version number. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of distro-info or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at #12063
DEPRECATION: python-debian 0.1.43ubuntu1 has a non-standard version number. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of python-debian or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at #12063"

marshalleq commented

@Sabyaro what others are saying is this isn't actually a support forum, it's a bug channel. I do appreciate when starting out it's hard to tell the difference, I certainly don't get that right all the time.

  • ๐Ÿ‘1
  • โค๏ธ1
Louis-LLY commented

Hello God, this is how we should solve this kind of error reporting

WARNING: Ignoring invalid distribution -orch (d:\sd-webui-aki-v4.2\sd-webui-aki-v4.2\python\lib\site-packages)
DEPRECATION: torchsde 0.2.5 has a non-standard dependency specifier numpy>=1.19.*; python_version >= "3.7". pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of torchsde or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at #12063

pradyunsg commented

@Louis-LLY please scroll on the page, and see if what you're asking about has come up already.

#12063 (comment)

  • ๐Ÿ‘1
  • โค๏ธ1
STEMBytes commented

please update this version to conform to PiP .. there are a lot of people who are getting this error and need someone to update it.

pradyunsg commented

@STEMBytes I assume you intended to file the issue/make a comment in a different project?

sbidoul commented

Is this something we are willing to enforce now, or should we wait until next year?

Note I have not investigated how hard the packaging upgrade is going to be, and it is likely I will not have enough time to do it before the release.

pfmoore commented

I think we should probably just go for it. I suspect the main problem packages will have been reported by now, and a quick check of some of the linked issues seems to indicate they are getting fixed. And we did say in the message that it would be enforced in 23.3, so we should stick to that.

Note I have not investigated how hard the packaging upgrade is going to be, and it is likely I will not have enough time to do it before the release.

So are you proposing we just turn the current warning into an error, or are you saying that as soon as someone does have time to do the packaging upgrade, that should go in?

sbidoul commented

So are you proposing we just turn the current warning into an error, or are you saying that as soon as someone does have time to do the packaging upgrade, that should go in?

I'm proposing to keep the deprecation warning until someone has the time to do the packaging upgrade.

I gave it a quick try in #12300, let's see how this goes.

pfmoore commented

Cool. I'll keep an eye on #12300 and if I get time, try to look into any issues you can't resolve.

maehoo99 commented

I'm having error when trying to install textract.

DEPRECATION: textract 1.6.5 has a non-standard dependency specifier extract-msg<=0.29.*. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of textract or contact the author to suggest that they release a version with a conforming dependency specifiers.

sochak33t commented

DEPRECATION: adns 1.4-py1 has a non-standard version number. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of adns or contact the author to suggest that they release a version with a conforming version number.

Any solution for this?
Kali-Linux

  • ๐Ÿ‘1
  • โค๏ธ1
truongvanthong commented

Help me
DEPRECATION: omegaconf 2.0.6 has a non-standard dependency specifier PyYAML>=5.1.*. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of omegaconf or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at #12063

  • โค๏ธ1
sbidoul commented

@sochak33t @truongvanthong we have no additional advice to offer than what is written in the deprecation message.

adns has a non standard version number (1.4-py1). You should contact the author to get a new release, or patch the source code of adns yourself.

omegaconf has a dependency on PyYAML>=5.1.*. which must be rewritten as PyYAML>=5.1. Please contact the author of omegaconf to get a fix (or patch the source code of omegaconf yourself).

  • โค๏ธ1
truongvanthong commented

@sochak33t @truongvanthong we have no additional advice to offer than what is written in the deprecation message.

adns has a non standard version number (1.4-py1). You should contact the author to get a new release, or patch the source code of adns yourself.

omegaconf has a dependency on PyYAML>=5.1.*. which must be rewritten as PyYAML>=5.1. Please contact the author of omegaconf to get a fix (or patch the source code of omegaconf yourself).

Thank you for bringing these issues to our attention. We appreciate your input and will take the necessary steps to address them. Your help in ensuring our software and dependencies are up to date is invaluable. If you have any more feedback or concerns, please don't hesitate to share. Thanks again!

  • โค๏ธ1
un99known99 commented

Hi, just upgrade to pip 23.3 with following message:

DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of gpg or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at https://github.com/pypa/pip/issues/12063
Installing collected packages: pip
  Attempting uninstall: pip
    Found existing installation: pip 23.2.1
    Uninstalling pip-23.2.1:
      Successfully uninstalled pip-23.2.1
Successfully installed pip-23.3


# gpg --version
gpg (GnuPG) 2.2.27
libgcrypt 1.8.8
Copyright (C) 2021 Free Software Foundation, Inc.
License GNU GPL-3.0-or-later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: /root/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

Anything I need to update/upgrade/not working after that?

pradyunsg commented

@un99known99 please read the first comment on this issue.

un99known99 commented

@pradyunsg which comment? there are "official" ones and deprecated ... please point to the valid one - thx

pfmoore commented

The original post here, #12063 (comment), specifically "What you can do".

un99known99 commented

@pfmoore thx for the hint, but for now - can it be left without causing side effects or do I need to rollback the pip upgrade?

pfmoore commented

As the comment says, this is a deprecation warning. So you don't have to do anything immediately, but if you leave it unfixed, it will fail in the future. The warning was changed in 23.3 to say this would happen in 24.0, so you're just seeing the previous text of the message.

So as long as you fix the underlying problem before pip 24.0 is released, you'll be fine (you'll just see the warnings in the meantime).

  • ๐Ÿ‘2
un99known99 commented

@pfmoore what I dont unterstand is that testing on my system shows:

gpg --version

gpg (GnuPG) 2.2.27
libgcrypt 1.8.8

where does pip get info for a gpg 1.14.0-unknown????

pfmoore commented

It's an installed Python package, not the gpg command. Try pip show gpg. If you're not clear what the difference is between an installed gpg command and a Python package gpg managed by pip, you should probably ask in a more general help forum.

The gpg package on PyPI doesn't list a version 1.14.0-unknown, so I have no idea how you installed that package, sorry.

un99known99 commented

@pfmoore

good hint, seems to be here:

pi@pihole:[~] $ pip show gpg
Name: gpg
Version: 1.14.0-unknown
Summary: Python bindings to the GPGME API of the GnuPG cryptography library.
Home-page: https://www.gnupg.org
Author: The GnuPG hackers
Author-email: gnupg-devel@gnupg.org
License: LGPL2.1+ (the library), GPL2+ (tests and examples)
Location: /usr/lib/python3/dist-packages
Requires:
Required-by:

would an update pip install gpg or similar help?

also, what would happen if u bump version to 24.0, would pip stop working in general on the system?

In addition I opened a bug report at gnupg:
https://dev.gnupg.org/T6763

grafik

un99known99 commented

can someone help me to get around that:

pi@pihole:[/usr/lib/python3.9] $ pip check gpg
DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 24.0 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of gpg or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at #12063
No broken requirements found.

pi@pihole:[/usr/lib/python3.9] $ pip uninstall gpg
Found existing installation: gpg 1.14.0-unknown
ERROR: Cannot uninstall 'gpg'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall.

I dont know how that gpg 1.14.0-unknown came to the system

un99known99 commented

even "upgrading" doesnt work:

pi@pihole:[/usr/lib/python3.9] $ pip install --upgrade gpg
Defaulting to user installation because normal site-packages is not writeable
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: gpg in /usr/lib/python3/dist-packages (1.14.0-unknown)
Collecting gpg
Downloading gpg-1.10.0.tar.gz (39 kB)
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error

ร— python setup.py egg_info did not run successfully.
โ”‚ exit code: 1
โ•ฐโ”€> [1 lines of output]
Could not find gpgme-config. Please install the libgpgme development package.
[end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

ร— Encountered error while generating package metadata.
โ•ฐโ”€> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
WARNING: There was an error checking the latest version of pip.

pradyunsg commented

@un99known99 I'm sorry but this isn't the right place for asking for help with your issue.

I think that Python Discord's #help-* channels, #python on Libera.chat (IRC), python-list or python-tutor mailing lists,or StackOverflow would be better channels to get support for the issue you're facing.

Thanks!

  • ๐Ÿ‘1
khacho77 commented

the solution?

DEPRECATION: textract 1.6.5 has a non-standard dependency specifier extract-msg<=0.29.*. pip 24.0 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of textract or contact the author to suggest that they release a version with a conforming dependency specifiers

pfmoore commented

A possible replacement is to upgrade to a newer version of textract or contact the author to suggest that they release a version with a conforming dependency specifiers

People seem to have problems knowing what to do when faced with this message. Can you explain what's unclear about the above section - it's hard to know how we can usefully respond to your question without just repeating this advice ๐Ÿ™

  • ๐Ÿ‘3
nilslindemann commented

I reported the Issue with pip and devscripts on Linux Mint here.

  • ๐Ÿ‘1
  • โค๏ธ1
ecusts commented

pandas 0.23.4 has a non-standard dependency specifier pytz>=2011k. pip 24.0 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of pandas or contact the author to suggest that they release a version with a conforming dependency specifiers.

  • ๐Ÿš€1
pradyunsg commented

@ecusts Please report that to pandas or pytz, not here.

notatallshaw commented

Please report that to pandas or pytz, not here.

That's a very old version of Pandas, new versions of Pandas do not have this issue.

So to clarify, is there anything to report? Can Pandas actually do anything about it even if they wanted?

Secondly when legacy specifiers are finally dropped in Pip I take it old packages like this just won't be installable from Pip? And the advise for people needing legacy packages will to be to use legacy versions of Pip? Or manually vendor/fork and fix the packages themselves license permitting?

  • ๐Ÿš€1
pfmoore commented

Secondly when legacy specifiers are finally dropped in Pip I take it old packages like this just won't be installable from Pip? And the advise for people needing legacy packages will to be to use legacy versions of Pip? Or manually vendor/fork and fix the packages themselves license permitting?

Yes, I think that if people are using legacy packages like this, they need to be aware that they shouldn't necessarily expect modern versions of tools to work with those old versions. That version of Pandas is about 5 years old at this point. That doesn't just apply to pip, it's a more general point, but yes, it does apply here.

I don't know precisely what will happen when we drop support. At a minimum, yes, the old package won't be installable. It's possible that in some cases pip won't be able to manage environments with invalid pacakges installed - someone would need to test this to confirm. But essentially, don't use versions of pip that don't support the packages you're using.

I'd say the advice should be "If you're getting this issue with an old version of a library, you should upgrade the library. If some constraint prevents you from upgrading the library, you'll be forced to either fix the incompatibility yourself (library license permitting) or stick with older tools for compatibility, and that means using an old version of pip."

  • ๐Ÿ‘5
SishnuMobile commented

i can install pip but not the setup tools

  • ๐Ÿ‘1
  • ๐Ÿš€1
archbong commented

Please I'm trying to understand this warning message and how to solve this.
DEPRECATION: python-apt 1.6.6+elementary20~+ubuntu5.1.7.1 has a non-standard version number. pip 24.0 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of python-apt or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at #12063

frankaliberti commented

I'm not sure if this is the right place to request assistance, but I was told to come here from the prompt in case things didn't work out. I'm not to versed in coding and can't figure out how to get this to work.

FrostyNick commented

I'm not sure if this is the right place to request assistance, but I was told to come here from the prompt in case things didn't work out. I'm not to versed in coding and can't figure out how to get this to work.

If the issue is a warning message / broken package that you've installed elsewhere and you have been referred here, this usually will fix the issue (it won't work if the developer hasn't updated the package to respect PEP 440):

pip install <every package with your error> -U

For example I had to do this on my system to update the packages in pip (pip and pip3 usually do the same thing):
pip3 install python-debian distro-info -U

FrThib commented

Hi
I don't understand in each explanation what it is necessary to do for that.

DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 24.0 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of gpg or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at #12063
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv

What is the impact for this problem ?
I want to have more clearly on this subject if possible
Thank you for your help
Regards

pfmoore commented

@FrThib the initial post here explains what you need to do here under "what you can do". To put the impact in the simplest terms possible, when we remove support for legacy specifiers and versions (which will happen fairly soon, as upgrading our dependency on packaging is becoming urgent), pip will not recognise gpg 1.14.0-unknown as a valid package. How this will affect you depends on details of your environment that we cannot know - if you're trying to install that version, pip will simply not recognise that it exists and will fail to install it. If it's already installed, pip won't be aware of it, and may complain that things which depend on the package don't have their dependencies satisfied. Or pip may simply give an error saying that your environment is broken and you need to fix or recreate it manually.

Beyond that, there's not much we can say. gpg 1.14.0-unknown isn't (as far as I can see) distributed via PyPI, so wherever you got it from, you'll need to reach out to the suppliers and ask them how you can get (and install) a replacement that conforms to Python's standards for version numbers. Or if you're the maintainer of the gpg package, you'll need to fix your versioning.

FrThib commented

Hi all
This remains unclear to me. But I'm not a specialist
Well, itโ€™s true that I didnโ€™t give a lot of information.
I'm on raspberry Pi4 4Gb
PRETTY_NAME = โ€œRaspbian GNU/Linux 11 (bullseye)โ€
NAME = โ€œRaspbian GNU/Linuxโ€
VERSION_ID = โ€œ11โ€
VERSION = โ€œ11 (bullseye)โ€
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian

My version of python: Python 3.9.2

I am working on Linux and using the command line for each installation .
My aim is to install Open Cv but due to this message I cannot continue because of this message that trouble me for finishing the processing without random running.
Regards

BlueNihilist commented

Will you make this feautre opt-out?

I really think think there should be some sort of --force-install flag. Some vendors just throw their packages out there without a care in the world. And I don't know what's worse: waiting for ages for them to fix something or trying to fix it yourself.

kleschenko commented

Hi, we have an internal package using the version numbers compliant with PEP440, and now pip started to show the deprecation warning for it: DEPRECATION: ** has a non-standard dependency specifier package-internal>=3.2.0b0+300. pip 24.0 will enforce this behaviour change.

notatallshaw commented

Hi, we have an internal package using the version numbers compliant with PEP440, and now pip started to show the deprecation warning for it: DEPRECATION: ** has a non-standard dependency specifier package-internal>=3.2.0b0+300. pip 24.0 will enforce this behaviour change.

Reading the spec I do agree with you that looks valid: https://packaging.python.org/en/latest/specifications/version-specifiers/#local-version-identifiers

Pip uses packaging for specifiers though and it rejects it:

>>> from packaging.specifiers import SpecifierSet
>>> SpecifierSet('>=3.2.0b0+300')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "python3.11/site-packages/packaging/specifiers.py", line 714, in __init__
    parsed.add(Specifier(specifier))
               ^^^^^^^^^^^^^^^^^^^^
  File "python3.11/site-packages/packaging/specifiers.py", line 245, in __init__
    raise InvalidSpecifier(f"Invalid specifier: '{spec}'")
packaging.specifiers.InvalidSpecifier: Invalid specifier: '>=3.2.0b0+300'
>>> SpecifierSet('>=3.2.0b0')
<SpecifierSet('>=3.2.0b0')>

You should create an issue there: https://github.com/pypa/packaging/issues

notatallshaw commented

Hi, we have an internal package using the version numbers compliant with PEP440, and now pip started to show the deprecation warning for it: DEPRECATION: ** has a non-standard dependency specifier package-internal>=3.2.0b0+300. pip 24.0 will enforce this behaviour change.

Checking more carefully, while this is a valid version, I don't think this is a valid specifier. I.e. you can have a version 3.2.0b0+300 but you can't have a specifier >=3.2.0b0+300, the specifier should be >=3.2.0b0 and it will match the version 3.2.0b0+300 .

But I am not an expert, I've only recently been studying the nuances of Python versioning, please someone correct me if I am wrong.

  • ๐Ÿ‘1
pfmoore commented

From PEP 440 in the section on inclusive ordered comparisons:

Local version identifiers are NOT permitted in this version specifier.

  • ๐Ÿ‘2
notatallshaw commented

From PEP 440 in the section on inclusive ordered comparisons

Thanks for the specific link, further reading through this you also can't include them in exclusive comparison opertors and exclusive comparison operators will never match a local version: https://peps.python.org/pep-0440/#exclusive-ordered-comparison

pfmoore commented

Indeed ๐Ÿ™‚ Blame it on old habits and lack of time.

FrThib commented

Hi
I'm sorry but I still do not understand really what to do for my following message.

DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of gpg or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at https://github.com/pypa/pip/issues/12063

This one appear when i install or upgrade applications . For example the last one

pip -vv install packaging

The result :

Using pip 24.0 from /home/pi/.local/lib/python3.9/site-packages/pip (python 3.9)
Defaulting to user installation because normal site-packages is not writeable
Created temporary directory: /tmp/pip-build-tracker-8kxc61zz
Initialized build tracking at /tmp/pip-build-tracker-8kxc61zz
Created build tracker: /tmp/pip-build-tracker-8kxc61zz
Entered build tracker: /tmp/pip-build-tracker-8kxc61zz
Created temporary directory: /tmp/pip-install-l2ypplgq
Created temporary directory: /tmp/pip-ephem-wheel-cache-b52dogbi
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: packaging in ./.local/lib/python3.9/site-packages (23.2)
Created temporary directory: /tmp/pip-unpack-93yggjql
DEPRECATION: gpg 1.14.0-unknown has a non-standard version number. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of gpg or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at #12063
Remote version of pip: 24.0
Local version of pip: 24.0
Was pip installed by pip? True
Removed build tracker: '/tmp/pip-build-tracker-8kxc61zz'

The system used for these installation is raspberry pi4
PRETTY_NAME = ยซ Raspbian GNU/Linux 11 (bullseye) ยป
NAME = ยซ Raspbian GNU/Linux ยป
VERSION_ID = ยซ 11 ยป
VERSION = ยซ 11 (bullseye) ยป
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian

my Python Version :Python 3.9.2

Many thanks for your help
regards
Franรงois

  • ๐Ÿ‘1
pfmoore commented

I answered this above. There's not much more I can offer.

If you ignore the message, then when you upgrade to a pip version where the behaviour change has occurred, everything will still work as it does now, except that pip will start ignoring your installation of the gpg package. This means:

  1. If any other packages depend on gpg, pip will tell you they are broken.
  2. You won't be able to manage the gpg package (upgrade it, uninstall it, etc) using pip.
  3. If you try to install or upgrade a package depending on gpg, pip will try to find and install a version with a valid version number. In doing so, it won't uninstall the existing gpg package, and you'll end up with two copies installed, which will probably break.

If you want to address the message, you need to:

  1. Find out where you got gpg 1.14.0-unknown from. It's not on PyPI - the latest version there is 1.10.0, from 2018.
  2. Raise the problem with the people who supplied gpg 1.14.0-unknown. They may already have a newer version. If not, they need to create one.
  3. Upgrade your existing gpg 1.14.0-unknown to the newer, valid, version.

I did some searches for "gpg 1.14.0-unknown" for you, to see if I could find somewhere to direct you. There's a Raspberry Pi bug report for this at https://forums.raspberrypi.com/viewtopic.php?t=355615, but that says it's a upstream Debian issue. Adding "Debian" to my search, I found https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1977645 which claims to be a duplicate of https://bugs.launchpad.net/ubuntu/+source/distro-info/+bug/1991606. I can't tell from that latter bug whether you can get a fixed version, or whether you need an OS upgrade (there's some discussion about policy around stable releases that I don't understand).

So while I hope that helps, ultimately it comes down to the fact that you need to pick this up with your OS supplier and follow their advice. The pip project can't really help you any further.

FrThib commented

hi Pfmoore and thank you for your answer
I understand when I see your links that I have no concret solution regarding this problem except by complet Raspberry installing ( OS, applications) and paying attention to different messages especially for the pip remarks.
Never mind!
Thanks you again
Regards
Franรงois

slaseawoch commented

WARNING: tensorflow 2.13.0 does not provide the extra 'keras'
DEPRECATION: pyodbc 4.0.0-unsupported has a non-standard version number. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of pyodbc or contact the author to suggest that they release a version with a conforming version number.

77babyy commented

1.$ pip install --upgrade distro-info
Defaulting to user installation because normal site-packages is not writeable
Looking in indexes: https://mirrors.ustc.edu.cn/pypi/web/simple
Collecting distro-info
Downloading https://mirrors.bfsu.edu.cn/pypi/web/packages/b5/62/174e099aa2c033d10a1454e097bf5192cf28ac8e95a544388da0d6c7dd24/distro_info-1.0-py3-none-any.whl (4.0 kB)
DEPRECATION: pyodbc 4.0.0-unsupported has a non-standard version number. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of pyodbc or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at #12063
Installing collected packages: distro-info
Successfully installed distro-info-1.0
2.Collecting types-python-dateutil>=2.8.10 (from arrow>=0.15.0->isoduration->jsonschema[format-nongpl]>=4.18.0->jupyter-events>=0.9.0->jupyter-server<3,>=2.4.0->notebook->jupyter)
Downloading https://mirrors.bfsu.edu.cn/pypi/web/packages/c7/1b/af4f4c4f3f7339a4b7eb3c0ab13416db98f8ac09de3399129ee5fdfa282b/types_python_dateutil-2.9.0.20240316-py3-none-any.whl (9.7 kB)
DEPRECATION: pyodbc 4.0.0-unsupported has a non-standard version number. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of pyodbc or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at #12063
Installing collected packages: webencodings, wcwidth, pure-eval, ptyprocess, fastjsonschema, zipp, widgetsnbextension, websocket-client, webcolors, urllib3, uri-template, typing-extensions, types-python-dateutil, traitlets, tornado, tomli, tinycss2, soupsieve, sniffio, six, send2trash, rpds-py, rfc3986-validator, pyzmq, pyyaml, python-json-logger, pygments, pycparser, psutil, prompt-toolkit, prometheus-client, platformdirs, pexpect, parso, pandocfilters, packaging, overrides, nest-asyncio, mistune, markupsafe, jupyterlab-widgets, jupyterlab-pygments, jsonpointer, json5, idna, h11, fqdn, executing, exceptiongroup, defusedxml, decorator, debugpy, charset-normalizer, certifi, babel, attrs, terminado, rfc3339-validator, requests, referencing, qtpy, python-dateutil, matplotlib-inline, jupyter-core, jinja2, jedi, importlib-metadata, httpcore, comm, cffi, bleach, beautifulsoup4, async-lru, asttokens, anyio, stack-data, jupyter-server-terminals, jupyter-client, jsonschema-specifications, httpx, arrow, argon2-cffi-bindings, jsonschema, isoduration, ipython, argon2-cffi, nbformat, ipywidgets, ipykernel, qtconsole, nbclient, jupyter-events, jupyter-console, nbconvert, jupyter-server, notebook-shim, jupyterlab-server, jupyter-lsp, jupyterlab, notebook, jupyter
Successfully installed anyio-4.3.0 argon2-cffi-23.1.0 argon2-cffi-bindings-21.2.0 arrow-1.3.0 asttokens-2.4.1 async-lru-2.0.4 attrs-23.2.0 babel-2.14.0 beautifulsoup4-4.12.3 bleach-6.1.0 certifi-2024.2.2 cffi-1.16.0 charset-normalizer-3.3.2 comm-0.2.2 debugpy-1.8.1 decorator-5.1.1 defusedxml-0.7.1 exceptiongroup-1.2.0 executing-2.0.1 fastjsonschema-2.19.1 fqdn-1.5.1 h11-0.14.0 httpcore-1.0.4 httpx-0.27.0 idna-3.6 importlib-metadata-7.1.0 ipykernel-6.29.3 ipython-8.18.1 ipywidgets-8.1.2 isoduration-20.11.0 jedi-0.19.1 jinja2-3.1.3 json5-0.9.24 jsonpointer-2.4 jsonschema-4.21.1 jsonschema-specifications-2023.12.1 jupyter-1.0.0 jupyter-client-8.6.1 jupyter-console-6.6.3 jupyter-core-5.7.2 jupyter-events-0.10.0 jupyter-lsp-2.2.4 jupyter-server-2.13.0 jupyter-server-terminals-0.5.3 jupyterlab-4.1.5 jupyterlab-pygments-0.3.0 jupyterlab-server-2.25.4 jupyterlab-widgets-3.0.10 markupsafe-2.1.5 matplotlib-inline-0.1.6 mistune-3.0.2 nbclient-0.10.0 nbconvert-7.16.3 nbformat-5.10.3 nest-asyncio-1.6.0 notebook-7.1.2 notebook-shim-0.2.4 overrides-7.7.0 packaging-24.0 pandocfilters-1.5.1 parso-0.8.3 pexpect-4.9.0 platformdirs-4.2.0 prometheus-client-0.20.0 prompt-toolkit-3.0.43 psutil-5.9.8 ptyprocess-0.7.0 pure-eval-0.2.2 pycparser-2.21 pygments-2.17.2 python-dateutil-2.9.0.post0 python-json-logger-2.0.7 pyyaml-6.0.1 pyzmq-25.1.2 qtconsole-5.5.1 qtpy-2.4.1 referencing-0.34.0 requests-2.31.0 rfc3339-validator-0.1.4 rfc3986-validator-0.1.1 rpds-py-0.18.0 send2trash-1.8.2 six-1.16.0 sniffio-1.3.1 soupsieve-2.5 stack-data-0.6.3 terminado-0.18.1 tinycss2-1.2.1 tomli-2.0.1 tornado-6.4 traitlets-5.14.2 types-python-dateutil-2.9.0.20240316 typing-extensions-4.10.0 uri-template-1.3.0 urllib3-2.2.1 wcwidth-0.2.13 webcolors-1.13 webencodings-0.5.1 websocket-client-1.7.0 widgetsnbextension-4.0.10 zipp-3.18.1
3. python -m pip install pyodbc
Defaulting to user installation because normal site-packages is not writeable
Looking in indexes: https://mirrors.ustc.edu.cn/pypi/web/simple
Requirement already satisfied: pyodbc in /usr/lib64/python3.9/site-packages (4.0.0-unsupported)
DEPRECATION: pyodbc 4.0.0-unsupported has a non-standard version number. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of pyodbc or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at #12063

I just want to open Jupyter Notebook in Linux. After downloading and installing Conda, I upgraded pip to version 24.0 using 'pip install -i https://pypi.mirrors.ustc.edu.cn/simple --upgrade pip'. But then, deprecation warnings started appearing everywhere. Why is that?

sbidoul commented

pyodbc 4.0.0-unsupported is not a standard-compliant version format (specifically, the -unsupported part). You should look where this version is coming from and contact whoever is in capacity of fixing that.

davidlantai commented

DEPRECATION: torchsde 0.2.5 has a non-standard dependency specifier numpy>=1.19.*; python_version >= "3.7". pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of torchsde or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at #12063 ๅ‡บ็Žฐ่ฟ™ไธช้—ฎ้ข˜ๅฟฝ่ง†๏ผŒ่ฟ˜ๆ˜ฏ่ฆๅ‡็บง

VedantSharma16042002 commented

I am having issues while installing any libraries , showing this deprecation at the end of every command execution
DEPRECATION: textract 1.6.5 has a non-standard dependency specifier extract-msg<=0.29.*. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of textract or contact the author to suggest that they release a version with a conforming dependency specifiers.

sbidoul commented

@VedantSharma16042002 you'll need to contact the textract project so they release a fix.

notatallshaw commented

FYI textract looks like an unmaintained project and textract 1.6.5 is the latest version, likely you will not be ble to install it once pip remove legacy versions and specifiers and you will need to pin pip to the last version that supports legacy versions and specifiers (probably pip 24.0).

ichard26 commented

@ShuOreki you'll need to use a newer version of omegaconf if you wish to install it with the upcoming pip release. Cross-referencing from omry/omegaconf#775 which was merged on Aug 12 2021, I believe you'll need to use omegaconf >= 2.1.1 as version 2.1.1 was published a few days afterwards.

tianmingxuan commented

DEPRECATION: vtk -PKG-VERSION has a non-standard version number. pip 24.0 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of vtk or contact the author to suggest that they release a version with a conforming version number. Discussion can be found at #12063
May I ask how to solve this problem๏ผŸ

ichard26 commented

@tianmingxuan as the warning suggests, you should either check whether you can use a newer version of vtk that has standards-compliant metadata and/or contact the project's author to fix their metadata. The problem lies with the package itself, so either way, you'll need to do something to avoid installing packages with deprecated metadata.

InquisitiveAS commented

DEPRECATION: vtk -PKG-VERSION has a non-standard version number. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of vtk or contact the author to suggest that they release a versio
n with a conforming version number. Discussion can be found at #12063

pradyunsg commented

Please stop posting the error message here folks. The deprecation message clearly indicates what you can do -- use a newer version of the library or contact the author of the library.

tfpf commented

Might be worth considering locking this conversation? It has received enough off-topic comments. Locking may further signal that this isn't a support thread.

It may be a while before all Linux distributions update the Python distribution packages, so people may keep visiting here. When they do (and see itโ€™s locked), a glance at the original post will again clarify that this thread isnโ€™t for support.

pradyunsg commented

Yea, I considered that. If we see more of that after telling people not to in the final post (which it is no longer, oops), then I'll lock this. :)

Repeating the earlier message:

Please stop posting the error message here folks. The deprecation message indicates what you can do -- use a newer version of the library or contact the author of the library.

M-Pine commented

I have already installed huggingface_hub and it is the latest version, but when running eval.sh, I get the error ModuleNotFoundError: No module named 'huggingface_hub.snapshot_download'.

Gladys91 commented

"Hello! I installed in my terminal pip install opencv-python, and I'm getting the following error:"
Requirement already satisfied: opencv-python in c:\programdata\anaconda3\envs\jobs\lib\site-packages (4.6.0)
DEPRECATION: textract 1.6.5 has a non-standard dependency specifier extract-msg<=0.29.*. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of textract or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at #12063

I have also tried the following pip install pillow opencv-python , but I get the same error.

bluebrad commented

The solution i found for Easy Diffusion not booting is discord needed to be shutdown first.

qzhyjd commented

DEPRECATION: pandas 0.23.4 has a non-standard dependency specifier pytz>=2011k. pip 24.1 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of pandas or contact the author to suggest that they release a version with a conforming dependency specifiers.