State of PyPI Organizations
|
|
11
|
2151
|
April 11, 2024
|
Announcing a PyPI Support Specialist!
|
|
0
|
309
|
March 20, 2024
|
PyPI Malware Observation Report Outcomes - Private Preview
|
|
0
|
610
|
March 20, 2024
|
Troubleshooting Modbus Connection Issue: "Failed to connect" Error
|
|
7
|
234
|
March 8, 2024
|
Restricting "open ended" releases on PyPI?
|
|
32
|
1516
|
February 11, 2024
|
Is PEP 541 still the correct solution?
|
|
19
|
2380
|
January 22, 2024
|
Pip3 version after multiple installations of python3
|
|
7
|
977
|
January 5, 2024
|
Getting error No module named 'pip._internal.download' and ModuleNotFoundError: No module named 'pip.download'
|
|
5
|
1357
|
December 9, 2023
|
Project names blocked on PyPI to avoid name collision for downstream free-threaded Python distributions
|
|
6
|
679
|
December 6, 2023
|
Request "python" organisation on PyPI
|
|
8
|
1783
|
December 6, 2023
|
The fate of artifacts after a PEP 541 transfer?
|
|
1
|
377
|
August 30, 2023
|
Must Pypi organization names be different than existing usernames?
|
|
3
|
496
|
August 26, 2023
|