jezdez / caniusepython3.com Goto Github PK

In the HTML there is the following image line

 <img height="16" src="https://caniusepython3.com/project/blackhole" alt="blackhole port status" />

As you can see from that img tag's source attribute, that's not an image and it fails to load in latest Chrome Canary build.

Currently you can search for any project and caniusepython3 will report it's Python3 compatible... If you press on "Check again" in the result page will 404 you.
Is it covered?

When I use the Web interface django-tables2 shows as not Python 3 compatible. Using the latest PyPi version of the cli shows it as compatible. Also the PyPi site does as well:
https://pypi.python.org/pypi/django-tables2/0.16.0

File uploads on http://caniusepython3.com currently don't work in Firefox, Safari, or Chrome. It displays as a drop target, there are no JavaScript errors in the console but nothing happens when you drop files on the widget.

I have (ERR_INVALID_REDIRECT) in all browsers ? How I fix this ? when I I manually enter "https://" it works.

I tried by URL and got an error:

https://raw.githubusercontent.com/freelawproject/courtlistener/605945436ca5de0690a6ef943f48e0a19306607e/requirements.txt

Then I tried by uploading the file by hand, and got an error.

Then I clicked the About Us link and got a 404. :)

If I click the link on Github to visit the site, Chrome (64.0.3282.186 Linux) shows an invalid redirect error.

If I manually enter "https://" at the start of the url it works fine.

It was working great, but since few days I am noticing site has been slow. Sometimes it keeps waiting forever.

I guess I started this check more than 10 minutes ago, it is still waiting https://caniusepython3.com/check/cc226657-8e23-499b-b9d2-1d965fec92aa

STR:

1. Create a requirements file containing:

requests
https://github.com/jeads/datasource/archive/v0.10.0.tar.gz#egg=datasource==0.10.0

2. Drag onto the text area on https://caniusepython3.com/ and press check

Expected:
Ideally both requirements checked, or failing that at least the check run against the non-URL requirement (requests).

Actual:

Couldn't check ['https://github.com/jeads/datasource/archive/v0.10.0.tar.gz#egg=datasource==0.10.0'].

Adding -e prior to the URL prevents the error. However bare URLs are allowed according to:
https://pip.readthedocs.org/en/stable/reference/pip_install/#requirements-file-format

STR:

1. Create a requirements file containing:

requests==2.9.1 --hash=sha256:113fbba5531a9e34945b7d36b33a084e8ba5d0664b703c81a7c572d91919a5b8

2. Drag onto https://caniusepython3.com/ and press check

Expected:
Requirements file can be checked successfully, the same as if it just contained requests==2.9.1.

Actual:

Project --hash=sha256:113fbba5531a9e34945b7d36b33a084e8ba5d0664b703c81a7c572d91919a5b8 invalid

The hash syntax was added in pip 8, as part of the new hash-checking mode:
http://pip.readthedocs.org/en/stable/user_guide/#hash-checking-mode
http://pip.readthedocs.org/en/stable/reference/pip_install/#hash-checking-mode

caniusepython3.com doesn't work if requirements.txt contains things like

 git+git://github.com/mpasternak/django-interval-field.git

Something like http://img.shields.io/badge/Python3%20port%20blocked%20by-3%20projects-red.svg and http://img.shields.io/badge/Python3%20port%20blocked%20by-no%20one-brightgreen.svg

https://requires.io/github/jezdez/caniusepython3.com/requirements/

=> leads to a 404. I guess the URL changed.

https://caniusepython3.com/

Usually the service is slow but gets the job done, but this time, it wouldn't load after a few minutes.
My requirements.txt file

bcrypt==2.0.0
cffi==1.1.2
click==4.0
dj-database-url==0.3.0
Django==1.8.2
django-postgrespool==0.3.0
gunicorn==19.3.0
msgpack-python==0.4.6
opencage==1.1.3
psycopg2==2.6
pycparser==2.14
redis==2.10.3
requests==2.7.0
rq==0.5.3
six==1.9.0
SQLAlchemy==1.0.4
wheel==0.24.0
whitenoise==1.0.6
scipy==0.15.1

Hello, I'm running into this warning from Chrome when I try to visit the site.

Think the security certificate needs to be updated.

Thanks!

@jezdez sent me a link on Twitter:

https://caniusepython3.com/check/8bad0535-bfa3-4c98-b2d2-532e848237d2

On my iPhone I cannot see the package names (on the desktop this appears in a blue column on the right; this doesn't seen to be visible in Safari on the iOS 7). See screenshot:

Can the package names be placed somewhere so that they're always visible?

Hi! I get different results using the package locally and the site. Here's the result running the site:
https://caniusepython3.com/check/7f785350-ceff-426f-8ae1-8d7edbcde2a4

And here's running against the file locally:

$ caniusepython3 -r requirements/production.txt
[WARNING] problem fetching svamp, assuming ported (404)
[WARNING] problem fetching django-features, assuming ported (404)
[WARNING] problem fetching json-api-mapper, assuming ported (404)
[WARNING] problem fetching puri, assuming ported (404)

You need 3 projects to transition to Python 3.
Of those 3 projects, 3 have no direct dependencies blocking their transition:

  django-piston
  embedly
  pyes

Any idea why the results are different?

I think it would be valuable to have URLs like http://caniusepython3.com/requirements/django,requests to provide quick links to checks for a project.

I'm willing to have a go at implementing it when I have time this weekend.

Not looking for it to look like a hyperlink per-se, but it would be handy to be able to jump to the project page.

https://github.com/mozilla/elmo/blob/master/requirements/compiled.txt doesn't work, https://github.com/mozilla/elmo/raw/master/requirements/compiled.txt does. maybe auto-sanitize the blob urls?

Site https://caniusepython3.com/ returns 502 Bad Gateway at this time.

https://pypi.python.org/pypi/testresources contains "Programming Language :: Python :: 3"

But https://caniusepython3.com/project/testresources says that it's not ready for Python 3.

Hi there,

Just in case you haven't noticed: your Let's Encrypt certificate for https://caniusepython3.com has expired. Thanks for providing this great service!

STR:

1. Enter https://raw.githubusercontent.com/mozilla/treeherder/b2ecb99390185ed7883b2334c1b11855ddd0811b/requirements/common.txt in the text field on https://caniusepython3.com/
2. Press submit

Expected:
If there were errors (eg due to #47) then they are displayed as part of the error message, eg:

Couldn't check ['https://raw.githubusercontent.com/mozilla/treeherder/b2ecb99390185ed7883b2334c1b11855ddd0811b/requirements/common.txt']: invalid requirement 'https://github.com/jeads/datasource/archive/v0.10.0.tar.gz#egg=datasource==0.10.0'.

Actual:

Couldn't check ['https://raw.githubusercontent.com/mozilla/treeherder/b2ecb99390185ed7883b2334c1b11855ddd0811b/requirements/common.txt'].

I'm not getting a final result for:

https://caniusepython3.com/check/b3b6ec4c-0367-42fa-92b1-6625059cee21 (checking django)

https://caniusepython3.com/check/ae4b3f81-a132-40ff-856f-74c5b6250cc5 (checking django, ecdsa)

https://pypi.python.org/pypi/Twiggy

has the Python 3 classifier

and the caniusepython3 CLI tool says that it's Python 3 compatible:

$ caniusepython3 --projects Twiggy
Finding and checking dependencies ...
[WARNING] Stale overrides: set([u'python-neutronclient'])

You have 0 projects blocking you from using Python 3!

but https://caniusepython3.com/project/Twiggy says that there's 1 blocker, although I can't tell what it is:

Maybe a cache needs to be cleared? Twiggy only gained the Python 3 classifier yesterday, so I'm wondering if caching is the cause and it might even sort itself out in a day or two.

This is it, the link is pointing to: https://caniusepython3.com/about/ e raise a 404 error

I'm finding lots of packages that have python3 support (as seen by .travis/tox.ini), but don't have any "Language :: Python" classifiers in setup.py.

The cert for https://caniusepython3.com/ expired on 28 August 2018, 13:03:27 GMT+2. The current time is August 29, 2018, 2:06 PM.

Likely the same issue as #62?

(Either directly or indirectly via requirements)

Then we can make a list of which packages are the most dependened on which don't have py3k support yet.

When providing e.g. Django==1.6 as input, it reports:

Project Django==1.6 invalid

I could imagine that the pinning / version information would just get ignored for the lookup.

(I have thrown my pip freeze output in there. This resulted in another error:

Couldn't check ['file:///home/jezdez/tmp/tmpxaslvn']

I have not bi-sected it to find the culprit, only tried a single entry then.)

django-storages shows as not compatible when using the web interface.
The project was abandoned for a couple of year without Python 3 support, but is now supporting Python 3.

Looks like this was reported before (#63, #62) but now the website uses HSTS so Firefox won't even allow me to add a temporary exception:

If you try to check python 3 compatibility of anything right now, you get a 500 internal server error.

Hi @tricoder42 & @jezdez! Thank you for maintaining caniusepython3.com.

I'd love to be able to point to the site as part of the work I'm doing spreading the word about the EOL for Python 2.x -- along the way it would be good to fix a few bugs in this site. Would you be interested in me co-maintaining it for the next few months?

Thanks!

cc @brettcannon in case you want to weigh in.

Gives 500 https://caniusepython3.com

Currently, trying to connect to https://caniusepython3.com leads to a security notice saying that the SSL certificate expired 18 days ago.

FYI trying to connect to http://caniusepython3.com instead (ie not secure), leads to an Nginx thank-you page.

Because the site isn't working for me (see #48), is there a command-line version of this that I can use?

If you check something made up like asdfdfsadfdfffffff it says that it's blocking, when in fact it's just invalid. Might help to grab the complete list of Python 3 projects and then do a check if a project is even listed in there to at least suggest it could be a typo from manual input.

Not responding at all...

Using Chrome 46.0.2490.86 (64-bit) on Mac OsX 10.11.1

a requirements.txt file with the below content results in "Couldn't check (file:///path/to/tempfile)

django
--allow-external djcelery

e.g.: Couldn't check ['file:///home/jezdez/tmp/tmpghod8t']. (in case that file is still available on the server)

Seems some packages are not correctly recognized even though they have the required classifiers on PyPI.

For example pyramid_mako.

One thing I noticed is that on the website entering pyramid_mako turns out as pyramid-mako (underscore converted to dash). Maybe it does not find that on PyPI...?

BR

Not sure how you want to handle updates specifically for overrides.json. Is it easiest for me to just push micro version updates (in which case the pegging in the requirements.txt file might get annoying to update)? Do you want to just grab the raw JSON from GitHub? Let me know what's easiest for you so you can get them quickly.

And if you want, feel free to have a link pointing at brettcannon/caniusepython3 for people to file bugs when a project's status is outdated.