Taylor Edmiston created BEAM-4025: ------------------------------------- Summary: Non-working Python 3 versions are installable on PyPI Key: BEAM-4025 URL: https://issues.apache.org/jira/browse/BEAM-4025 Project: Beam Issue Type: Bug Components: sdk-py-core Affects Versions: 2.2.0, 2.1.0, 2.0.0, 0.6.0 Reporter: Taylor Edmiston Assignee: Ahmet Altay
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 PyPI configuration was fixed at some point after 2.2.0.) This affects the following 5 versions: {code:java} $ 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{code} 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: {code:java} 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)].{code} 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005)