View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006287 | Kali Linux | Kali Package Bug | public | 2020-04-14 15:07 | 2020-04-15 07:34 |
| Reporter | jsf9k | Assigned To | rhertzog | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | kali-dev | ||||
| Summary | 0006287: python-pip package not available | ||||
| Description | I noticed starting Friday (April 10, 2020) that the python-pip package is no longer available, but python2 appears to still be the default python. This is inconsistent. | ||||
| Steps To Reproduce | $ docker pull kalilinux/kali-rolling:latest | ||||
|
This is actually breaking a lot of builds for me. It would be great if Kali-rolling could either restore the python-pip package or make python3 the default python. Right now Kali-rolling is in a sort of limbo state. |
|
|
This is also breaking our systems and ops. A quick resolution would be much appreciated. � |
|
|
There's nothing like the "default python". /usr/bin/python is python2, /usr/bin/python3 is python3. Most scripts now use python3 and python3 is the de-facto default python. Debian made the choice to not update /usr/bin/python to not break user scripts and the like. All python modules, including pip, are being updated to no longer provide the python 2 version so this is expected and normal. Please update your code/automation to use python3. |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-04-14 15:07 | jsf9k | New Issue | |
| 2020-04-14 19:25 | jsf9k | Note Added: 0012621 | |
| 2020-04-14 21:09 | felddy | Note Added: 0012622 | |
| 2020-04-15 07:34 | rhertzog | Assigned To | => rhertzog |
| 2020-04-15 07:34 | rhertzog | Status | new => closed |
| 2020-04-15 07:34 | rhertzog | Resolution | open => no change required |
| 2020-04-15 07:34 | rhertzog | Note Added: 0012623 |