Inconsistent supported python version with one specified by dependecy modules

[artingithug]

Pypi of pylxd ver 2.2.10 build shows at classifier field that it supports upto python version 3.6. However, requests-toolbelt module and ws4py module, what pylxd depends on, appear to constrain python version upto 3.5.

Expected:

• classifiers field of pylxd's pypi meta shows supporting upto python ver 3.5 as requests-toolbelt module and ws4py module supports upto python ver 3.5.

Actual:

• classifiers field of pylxd's pypi meta shows supporting upto python ver 3.6 (as defined in setup.cfg)

Supplement info:

• Pypi meta excerpt of pylxd shows that it supports upto python 3.6

  $ curl -s -L https://pypi.python.org/pypi/pylxd/json | jq '.info | {"name":.name ,"version":.version, "classifiers":.classifiers}'
  {  
    "name": "pylxd",
    "version": "2.2.10",
    "classifiers": [
      ...
      "Programming Language :: Python :: 3.6"
    ]
  }

• Supported python version by dependency modules appears upto 3.5

  pylxd dependency tree in excerpt of pipenv's graph command output for my project using pylxd:

  • pylxd [required: Any, installed: 2.2.10]
    • cryptography [required: >=1.0,!=1.3.0, installed: 2.9.2]
      • cffi [required: >=1.8,!=1.11.3, installed: 1.14.0]
      • pycparser [required: Any, installed: 2.20]
      • six [required: >=1.4.1, installed: 1.14.0]
    • pbr [required: >=1.6, installed: 5.4.5]
    • python-dateutil [required: >=2.4.2, installed: 2.8.1]
      • six [required: >=1.5, installed: 1.14.0]
    • requests [required: >=2.20.0, installed: 2.23.0]
    • requests-toolbelt [required: >=0.8.0, installed: 0.9.1]
      • requests [required: >=2.0.1,<3.0.0, installed: 2.23.0]
    • requests-unixsocket [required: >=0.1.5, installed: 0.2.0]
      • requests [required: >=1.1, installed: 2.23.0]
      • urllib3 [required: >=1.8, installed: 1.25.9]
    • six [required: >=1.9.0, installed: 1.14.0]
    • ws4py [required: >=0.3.4,!=0.3.5, installed: 0.5.1]

  Among them, requests-toolbelt ver 2.8.1 and ws4py ver 0.5.1 support only upto python 3.5:

  • requests-toolbelt

    $_pymdl="requests-toolbelt"; \
    yolk -M "${_pymdl}" | grep -E '^name:|^version:'; \
    yolk -M "${_pymdl}" -f classifiers | tr ',' '\n' | awk '{gsub(/'"'"'|[ ]+|]/,"",$0); print $0}' | grep -E '[0-9]$' | awk -F':' '{print $(NF-2) "::" $NF}' | sort -r -u -V
    name: requests-toolbelt
    version: 0.9.1
    Python::3.5
    Python::3.4
    Python::3.3
    Python::3
    Python::2.7
    Python::2

  • ws4py

    $_pymdl="ws4py"; \
    yolk -M "${_pymdl}" | grep -E '^name:|^version:'; \
    yolk -M "${_pymdl}" -f classifiers | tr ',' '\n' | awk '{gsub(/'"'"'|[ ]+|]/,"",$0); print $0}' | grep -E '[0-9]$' | awk -F':' '{print $(NF-2) "::" $NF}' | sort -r -u -V
    name: ws4py
    version: 0.5.1
    Python::3.5
    Python::3.4
    Python::3.3
    Python::3
    Python::2.7
    Python::2

[xnox]

Note that whilst ws4py in pypi shop do not support 3.7 and up, in Debian and Ubuntu ws4py are patched for 3.7+ support.

I don't know if requests-toolbelt works or not.

[jhenstridge]

Note that trove classifiers are not a great way of determining the version compatibility of a packages. Many packages will just work with new versions of Python, and developers might not update the classifiers when publishing new releases.

The main concern is the ws4py dependency, right?

[xnox]

Correct ws4py is dead upstream, last known maintainer said they don't have time to do things. Distros have ws4py patched, but the version from pypi is broken.

Maybe you can switch requirements.txt syntax to pull ws4py from Ubuntu or Debian tarball and/or patch it, when building a part for it? As the stock one from pypi is borked.

[xnox]

Or for example please drop ws4py from the requirements.txt it is optional, and code works without it. And if someone has a working copy of ws4py => great, otherwise a broken one is not automatically installed for those that follow requirements.txt from pypi.