search

pypa / pip

The Python package installer
https://pip.pypa.io/
MIT License
9.55k stars 3.04k forks source link

Deprecate legacy versions and version specifiers #12063

Closed sbidoul closed 7 months ago

sbidoul commented 1 year ago

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 https://github.com/pypa/packaging/issues/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 (https://github.com/pypa/packaging/issues/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 1 year ago

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 1 year ago

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 https://github.com/google-research/torchsde/issues/131

uranusjr commented 1 year ago

Sorry, working on the wrong tab

asanka550-HACKER commented 1 year ago

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 https://github.com/pypa/pip/issues/12063

asanka550-HACKER commented 1 year ago

Help me..😥

sbidoul commented 1 year ago

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

eslerm commented 1 year ago

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
FrostyNick commented 1 year ago

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.

tfpf commented 1 year ago

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
evizcaino123 commented 1 year ago

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 https://github.com/pypa/pip/issues/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 https://github.com/pypa/pip/issues/12063

This is being built within a conda enviroment.

pradyunsg commented 1 year ago

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

pradyunsg commented 1 year ago

@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.

eslerm commented 1 year ago

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 https://github.com/pypa/setuptools/issues/3772#issuecomment-1384342813

pradyunsg commented 1 year ago

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.

ghost commented 1 year ago

gettting pep 517 on mac

Amazon90 commented 1 year ago 
`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 https://github.com/pypa/pip/issues/12063

sbidoul commented 1 year ago

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

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

zhenhuashao commented 1 year ago

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 https://github.com/pypa/pip/issues/12063

moseti1 commented 1 year ago

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 https://github.com/pypa/pip/issues/12063

pradyunsg commented 1 year ago

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.

marshalleq commented 1 year ago

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 1 year ago

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).

Jaxsii commented 1 year ago

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 https://github.com/google-research/torchsde/issues/131

anupamjamatia commented 1 year ago

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 1 year ago

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 1 year ago

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 1 year ago

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

Sabyaro commented 1 year ago

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 https://github.com/pypa/pip/issues/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 https://github.com/pypa/pip/issues/12063"

marshalleq commented 1 year ago

@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.

Louis-LLY commented 1 year ago

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 https://github.com/pypa/pip/issues/12063

pradyunsg commented 1 year ago

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

https://github.com/pypa/pip/issues/12063#issuecomment-1659568128

STEMBytes commented 1 year ago

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 1 year ago

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

sbidoul commented 1 year ago

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 1 year ago

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 1 year ago

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 1 year ago

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 1 year ago

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 1 year ago

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

truongvanthong commented 1 year ago

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 https://github.com/pypa/pip/issues/12063

sbidoul commented 1 year ago

@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).

truongvanthong commented 1 year ago

@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!

un99known99 commented 1 year ago

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 1 year ago

@un99known99 please read the first comment on this issue.

un99known99 commented 1 year ago

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

pfmoore commented 1 year ago

The original post here, https://github.com/pypa/pip/issues/12063#issue-1733513615, specifically "What you can do".

un99known99 commented 1 year ago

@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 1 year ago

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).

un99known99 commented 1 year ago

@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 1 year ago

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.