Closed Bug 1383914 Opened 7 years ago Closed 6 years ago

pip version 9+ required to prevent libraries migrated to py3-only to force breaking upgrade w/py2 packages

Categories

(Data Platform and Tools Graveyard :: Operations, enhancement)

Product:
Data Platform and Tools Graveyard
Component:
Operations
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: spenrose, Unassigned)

Details

(Whiteboard: [DataOps]) 

I am told [1][2] that given the following situation:

1) You are packaging a repository that requires Python2.
2) You include an external library whose latest version is Python3-only.

pre-9.0 versions of pip are not smart enough to use the latest Python2-compatible version of the library. (Can someone find a better reference?)

Solution is to make sure that we are on pip 9.0+ when building our packages.

[1] http://blog.jupyter.org/2017/04/19/release-of-ipython-6-0/
[2] https://us.pycon.org/2017/schedule/presentation/319/
Component: General → Operations
QA Contact: jthomas
I am not familiar with the scope of this. Is this related to packages being installed on ATMO or something else?
Whiteboard: [DataOps]
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
Product: Data Platform and Tools → Data Platform and Tools Graveyard
You need to log in before you can comment on or make changes to this bug.