Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Outreach re: ipython 6.0.0rc1 breaking builds of related projects on Python 2.7

See original GitHub issue

After the ipython 6.0.0rc1 release, the python-fire project ran in to Travis CI failures for internal builds, as noted in https://github.com/google/python-fire/issues/57

It would be helpful to have more readily visible or even proactive advice on how to configure setup.py, pip, and other dependency-management systems for a wide variety of use cases. E.g. how to configure a project to depend on ipython 6 for supported python versions, but version 5 otherwise.

Issue Analytics

State:
Created 6 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

1reaction

takluyvercommented, Mar 10, 2018

Closing this - we’ve made some efforts to promote the Requires-Python metadata, and things largely seem to have shaken out.

1reaction

takluyvercommented, Apr 11, 2017

Many packages are only uploaded as source packages, and the setup script can ask for different dependencies depending on the environment (e.g. require x only on Windows, or only on Python 2). So you can’t have a static list of all a packages dependencies in general.

There are better ways to handle conditional dependencies now - you can make a static list with ‘environment markers’ to filter which ones are used. If packages provide the information, PyPI can record dependencies (e.g. astsearch shows the dependency on astcheck). But many packages don’t.