Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

show alternative package if it doesn't support Python 3 #9

Open
chhantyal opened this issue Dec 4, 2014 · 15 comments
Open

show alternative package if it doesn't support Python 3 #9

chhantyal opened this issue Dec 4, 2014 · 15 comments

Comments

@chhantyal
Copy link
Owner

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?

@chhantyal
Copy link
Owner Author

Or just add short notes below table to inform about existence of alternative.

@ztane
Copy link

ztane commented Mar 30, 2015

+1 for this. For example it is not immediately obvious that sqlalchemy-migrate is a third-party effort and the preferred migration tool for sqlalchemy is the package named alembic.

@robertlagrant
Copy link

Yeah it should still be green, but with a note that a drop-in replacement exists?

@nicktimko
Copy link

Point of fact, MySQLdb is basically dead, but there's now a fork (drop-in replacement, no API changes) recommended by Django in their docs:

MySQL DB API Drivers

  • MySQLdb is a native driver that has been developed and supported for over a decade by Andy Dustman.
  • mysqlclient is a fork of MySQLdb which notably supports Python 3 and can be used as a drop-in replacement for MySQLdb. At the time of this writing, this is the recommended choice for using MySQL with Django.

@robertlagrant
Copy link

PyMySQL also seems to work nicely - pure-Python replacement that doesn't have a compile step on install. Nice for us fortunate enough to have to use Windows :)

@mathiasertl
Copy link

+1 from me.

(I'd like to add that I've made a 2.7/3.4+ fork for Fabric: https://pypi.python.org/pypi/Fabric3)

@brettcannon
Copy link
Contributor

I should mention that some of the overrides in caniusepython3 are actually drop-in alternatives so some of that data is already collected for you (e.g., look at how BeautifulSoup and PIL are overridden).

@mathiasertl
Copy link

@brettcannon in that case can you add Fabric3 as drop-in alternative to Fabric?

@brettcannon
Copy link
Contributor

@mathiasertl Please file an issue or send a PR against brettcannon/caniusepython3

@nickjacobson
Copy link
Contributor

Another example is https://pypi.python.org/pypi/ipaddr which was forked and became a builtin library in Python 3: https://docs.python.org/3/library/ipaddress.html

@nicktimko
Copy link

The wheel of win shows more and more win, but it's perhaps a bit strange when the Python 3 alternatives "overrides" aren't signified in any way. Noting which have alternate packages via https://github.com/brettcannon/caniusepython3/blob/master/caniusepython3/overrides.json might be prudent so there isn't any confusion if someone tries to install a package name (e.g. mysql-python) that's green but it then fails under 3.

@nickjacobson
Copy link
Contributor

2 more that are in white, and that have a version in Python 3:
"python-openid": "https://pypi.python.org/pypi/python3-openid" (already in overrides.json)
"python-ldap": "https://github.com/pyldap/pyldap" (I requested to have this added to overrides.json)

@ConorMcGee
Copy link

Sorry if I've misunderstood what's supposed to be happening here, but why is Fabric listed as green with no mention on the site that you have to use a fork?

@chhantyal
Copy link
Owner Author

@mcgeeco Sorry if it was misleading. I clarified the text here 1aad080 will be updated in next deployment

@ConorMcGee
Copy link

Ah that makes sense. Personally I like the yellow idea. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants