[BEAM-4025] Non-working Python 3 versions are installable on PyPI

• Type: Bug
• Status: Open
• Priority: P3
• Resolution: Unresolved
• Affects Version/s: 0.6.0, 2.0.0, 2.1.0, 2.2.0
• Component/s: sdk-py-core
• Assignee: Unassigned
• Reporter: Taylor Edmiston
• Created: 05/Apr/18 22:48
• Updated: 03/Jun/22 21:05

Description

Beam does not currently support Python 3, however, it's possible to install some versions from PyPI / Warehouse under Python 3 today.  (It appears the config was fixed after 2.2.0 - https://github.com/apache/beam/commit/807b4bcefd877440c12f7fc3b401446e21899904.)

This affects the following 5 versions:

$ pip3 install apache-beam==-1
Collecting apache-beam==-1
 Could not find a version that satisfies the requirement apache-beam==-1 (from versions: 0.6.0, 2.0.0, 2.1.0, 2.1.1, 2.2.0)
No matching distribution found for apache-beam==-1

This is a confusing experience for users (customers) to discover that it's incompatible only on import after installing the package (and not reading the docs) via the error message:

RuntimeError: The Apache Beam SDK for Python is supported only on Python 2.7. It is not supported on Python [sys.version_info(major=3, minor=6, micro=4, releaselevel='final', serial=0)].

Since it's not compatible anyway, it's confusing that the non-working package versions are installable.

I don't think there's an easy way to remove just the Python 3 build from the wheels or in the PyPI GUI.  As far as I can tell, this would require rebuilding + re-uploading the Python 2 wheels for affected versions.