chhantyal / py3readiness Goto Github PK

http://www.isup.me/py3readiness.org

These 2 libraries already support Python 3 but are shown in white on http://py3readiness.org:

1. https://pypi.python.org/pypi/testresources
2. https://pypi.python.org/pypi/filechunkio

They both have the trove classifier:
"Programming Language :: Python :: 3"

I noticed that the website https://caniusepython3.com is getting their Python 3 status wrong. But if you install the caniusepython3 library itself and check them, it returns True for their Python 3 status. So it's only the https://caniusepython3.com website that's wrong.

http://www.fabfile.org/index.html

Fabric is a high level Python (2.7, 3.4+) library designed to execute shell commands remotely over SSH, yielding useful Python objects in return:

https://news.ycombinator.com/item?id=11248652

http://docs.aws.amazon.com/lambda/latest/dg/lambda-python-how-to-create-deployment-package.html

• Fix same origin policy on S3
• Fix Cache Control and Content Type headers on S3
• Remove wheel.svg and results.json file from source

Looks like Fabric is supported now:
https://pypi.org/project/Fabric/2.2.2/

#38

i wonder if 360 list includes some packages that have not been updated for a long time.
these packages can be out-of-date and replaced by new packages.
it might just because their long existance in the past made them top the list.

would it be a good idea to exclude packages that has not been updated in the last 1 or 2 years for this py3 readiness list?

also would it be nice to put a different color for those py2 only but has py3 alternative packages? might also list the alternative packages next to it as a reference.

I believe that will make the list much more useful as a reference to new py3 developers

caniusepython3 uses tags in setup.py to check for Python 3 support, but some packages simply don't list supported versions at all. A good example would be uwsgi, which (in addition to being an application rather than a library) has a nearly empty PyPI page and, contrary to what is stated, supports Python 3. Maybe it'd be better to detect packages like this and remove them from the list completely?

Hey numpy is python 3 ready

M2Crypto and diamond support python3 but on website it doesn't show it. Please update. I am new to git don't know how to do edits.

as per subject

Currently when clicking a package name, one will reach the respective pypi project page.
However, when using py3readyness, I felt like I want to know more - for example how much downloads the other packages have, just to see how much is needed to rise up the charts.

Some research later I found the PyPI Ranking site which seems to have all the (even historical information) I wanted.

Personally I feel that py3readyness is just right in terms of simplicity, and if an additional link is added per package, it should be done so without adding clutter.

Maybe it would already help to just link the main PyPI Ranking page to the text saying "Python 3 support graph for 360 most popular Python packages!" right at the pages top.

Thanks for sharing your opinion about this.

futures is a backport of a Python 3 standard library module, so it's a bit of a special case, but its latest version says "It should not be installed on Python 3, although there should be no harm in doing so, as the standard library takes precedence over third party libraries.". Doesn't that text suggest that it shouldn't appear white in the compatibility list?

Somewhat separately: given that futures is useful on 2.7 only, should it particularly matter whether or not it is compatible with Python 3? Should it even appear in the list at all, whether in green or in white?

Does the text "Green packages support Python 3 (or has drop in replacement package which supports Python 3)" play any role for futures, given that its drop-in replacement not only exists, but is part of Python 3 itself?

Unless i am mistaken, nvidia-ml-py3 and py-filelock support Python 3, according to their READMEs and xgboost according to its installation guide. This leaves oauth, the later of which is archived, and thus might be considered dead anyway.

Just a thought before going ahead:
Would be nice to provide an alternative package if

1. Package is abandoned and has drop-in replacement
2. Package is not going to be supporting Python 3 because there already alternative package doing so.

etc.

Color would be yellow?

Packages like https://pypi.python.org/pypi/rackspace-novaclient only have setup.py but not really Python code.

Thus, they don't really relate to version support and should be removed from the graph/table.

I notice the website hasn't been updated since the 29th of October. A new version of caniusepython3 has been released and we should have at least 275 packages by now. Can you do an update, and is there any way I can help?

Both django-templatetag-sugar and nosexcover are reported as supporting Python3 by caniusepython3 (and have been for several hours), but aren't green on the website.

Cross-posting from meshy/pythonwheels#94:

Download counts are being removed from PyPI and instead BigQuery needs to be used.

See pypi/warehouse#2480 which removes the top_packages from the API.

Right now, PyPI is running from https://github.com/pypa/pypi-legacy but will be switching to https://github.com/pypa/warehouse soon. (Their milestones show they're 95% complete to launch, and 38% complete to shut down legacy PyPI.)

See badges/shields#716 and zhmcclient/python-zhmcclient#73 for some more info on BigQuery.

Perhaps in the short term Python 3 readiness could use a hardcoded list of the top 360 packages.

google-apputils is obsolete and replaced by absl-py, the latter one supports Python 3.

(Curious on how frequently do you update the list of packages?)

Even though they are put in FLAGS, they still show up in graph.

Plone seems to have many packages which make up core Plone. Check if duplication can be avoided.

https://travis-ci.org/chhantyal/py3readiness

The mysql-python package is manually overridden: https://github.com/brettcannon/caniusepython3/blob/master/caniusepython3/overrides.json#L18.

On the site however the link is not to https://pypi.python.org/pypi/mysqlclient, but to the old https://pypi.python.org/pypi/MySQL-python.

Generated data in json file results.json is saved to S3 to be using in http://py3readiness.org

Since 20 January, this feature is broken and results is not saved anymore.

I tried this approach, but it has some other issue 6cacd5b#diff-919718660b5ee2d0715752f611a3b7f6

This seems important (?)/relevant, as it's package number 9 on the list!

I've verified this by:

1. installing certifi on Python 3.4 (successfully), and
2. checking the PyPI package metadata (it's listed under Classifier: Programming Language :: Python :: 3.0, all the way up to 3.4).

1. The link to Werkzeug on http://py3readiness.org/ is https://pypi.python.org/pypi/Werkzeug which currently gives a 404 not found error.
   Here is a link that works: https://pypi.python.org/pypi/Werkzeug/0.10.1
   It is listed in white on py3readiness, but on the working link it lists "Programming Language :: Python :: 3"
2. The link on py3readiness for https://pypi.python.org/pypi/marionette-transport is a dead link. A working link is https://pypi.python.org/pypi/marionette-transport/0.1

Hi, texttable author here.

A user informed me that texttable is reported as python3 incompatible on your site. Please mark it as compatible. Even the caniusepython3 library is ok:

$ python -c "import caniusepython3; print(caniusepython3.check(projects=['texttable']))"
True

https://caniusepython3.com/project/texttable

Best regards,

Is it possible for you to use the development version of caniusepython3 instead of the stable version? The development version has the most up-to-date overrides and is a better indicator of Python 3 readiness.

Last updated on Sunday, 23 September 2018, 09:47:38 Would fix #60, #62, #63

As of v2.11.0 (released 10 days ago), Beam supports Python 3: https://pypi.org/project/apache-beam/

This will complete the list of the top 360 packages!

I'd like to see a visualization of which latest releases only support Python 3 (and do not support Python 2). i.e., NumPy will not support Python 2 after Jan. 1, 2019 (source). I'd like to see a representation of that.

The custom domain for your GitHub Pages site is pointed at an outdated IP address. You must update your site's DNS records if you'd like it to be available via your custom domain. For more information, see https://help.github.com/en/articles/using-a-custom-domain-with-github-pages.

Just a thought for now, but it might be useful.

As of today, there are 12 mozilla related packages in the graph http://py3readiness.org/ as these packages have large number of downloads on PyPi.

I am not sure if anyone outside Mozilla uses these packages. If people outside Mozilla don't use these, there is no point in showing them here. There is already a mechanism to override a package, and we could just put them there.

It looks like all those packages with moz prefix are related to Mozilla test infrastructure and they might be downloading/installing frequently while running tests.

I am opening this issue hoping to get some input from Mozilla Devs or someone who knows about it.

Ping Python devs at @mozilla/gecko-dev

there is pika python 3 version,

Use BigQuery to get data as suggested at https://packaging.python.org/guides/analyzing-pypi-package-downloads/

Alternatively, pypinfo can be used as well.

http://py3readiness.org/ show that it doesn't support it

From E-mail sent to me:

Current progress is 343/360 = 95% looks good but it is not correct because of there are much more than 360 active packages...

So I have suggestion to increase 360 to 3*360 = 1080. Why 1080? Because of it will be possible to save same style for graph (you can select green or white colour for each sector based on small group of 3 items)..

More packages - more fun to track progress. :-)

Now that makes sense :D

Update: Can't, cause AWS Lambda only supports 2 :(

futures package https://pypi.python.org/pypi/futures is gray, but it is actually a backport from Python 3. IMO it either should be shown green or removed from the list.