Version 3.0 is marked as Python 2 compatible but throws syntax errors

[adifelice-godaddy]

Issue

Installing pyramid==1.9.1 on a Python 2.7 environment also installs PasteDeploy-3.0 which doesn't seem to be compatible with Python 2.7.

Error

Traceback (most recent call last):
  File "/Users/user/.virtualenvs/myproject/bin/pserve", line 8, in <module>
    sys.exit(main())
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/pyramid/scripts/pserve.py", line 32, in main
    return command.run()
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/pyramid/scripts/pserve.py", line 167, in run
    loader = self._get_config_loader(config_uri)
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/pyramid/scripts/common.py", line 23, in get_config_loader
    return plaster.get_loader(config_uri, protocols=['wsgi'])
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/plaster/loaders.py", line 116, in get_loader
    loader = loader_info.load(config_uri)
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/plaster/loaders.py", line 204, in load
    return self.factory(config_uri)
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/plaster/loaders.py", line 199, in factory
    self._factory = self.entry_point.load()
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2443, in load
    return self.resolve()
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2449, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/plaster_pastedeploy/__init__.py", line 7, in <module>
    from paste.deploy import loadapp, loadserver, loadfilter, appconfig
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/paste/deploy/__init__.py", line 3, in <module>
    from paste.deploy.loadwsgi import *  # noqa F401,F403
  File "/Users/user/.virtualenvs/myproject/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 82
    args[0] = f'Error in file {parser.filename}: {e}'

Observation

The setup.cfg definition is missing the python_requires instruction.

[mmerickel]

Ok I forgot to release the package with python_requires metadata...

1. I will release a bugfix with the correct metadata.
2. I would like to pull 3.0 and release a new version with the correct metadata but I cannot atm.

@ianb maybe you could add me as an owner so I can manage the PyPI releases? Right now I cannot as only a maintainer role.

[mmerickel]

In the short term I have released 3.0.1 with the correct metadata. That's all I can do unless I get owner on PyPI.

[arxitim]

It would be really helpful to change exactly version 3.0, because now Python versions that do not support f-string try to install an incompatible version of this package with them(

Most of our CI builds started crashing because they try to install that exact version, because it doesn't specify the minimum Python version

We have already fixed the builds, but maybe other projects have encountered this problem too

[UncleGoogle]

Similar situation here. But importing package on Python 3.6 seems work (or at least do not raise exceptions), despite in 3.0.0 release notes there is a dropped support for Python 3.6.

[jvanasco]

@mmerickel maintainers are allowed to "yank" a release on PyPi. Doing that should fix all the CI issues people are having (unless someone hardcoded 3.0 to their package).

[mmerickel]

How can I yank a release? Is there an API I have to hit? The PyPI website does not give maintainers access to any UI features.

[jvanasco]

Ugh. Let me check. Maintainers were supposed to have this ability since last year.

[jvanasco]

FFS. It seems like PyPi has been using "maintainers" and "owners" interchangeably on this feature and it is owners only. I'm filing a ticket with them.

[mmerickel]

Hey folks, a little late in the game but I did get ownership rights and I have yanked version 3.0 from PyPI.

[mmerickel]

To be clear, 3.0.1 is fine and still available.

[jvanasco]

Thank you so much, @mmerickel ! This has been holding back some CI systems for me!

FWIW, I did start a ticket with PyPi over the inability of maintainers to yank releases. See pypi/warehouse#12643