ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
PSF conducted a series of three surveys. The requested features are listed here. Features requested more than once have been indicated with 'xnumber'.
2
Otherwise, the feature has been requested only once. Feature requests have been copied verbatim.
3
4
First Survey
5
6
Private packagesx6
7
Org. accountx5
8
Reserving a namespace for projects hosting multiple subprojectsx5
9
Unified manage page for all projects
10
pip search comes back to working, using PyPI as its' backend
11
Command for "packaging" the installed module in future versions of pip
12
Query entry points and extra-install keywords (ie something[keyword]) and being able to query it via the api for not installed packages
13
CVE scan and score displayed on the package page
14
Missing wheel files, not enough documentation
15
More statistics such as npm with their graphs also how many downloads a library has
16
Use PIP to upload onto PyPi
17
Discovery of useful packages for specific tasks is hard for new comers
18
Support for uploading MinGW Windows Python binaries
19
DNS validation for use with naming
20
devpi like functionality
21
Enforce 2FA
22
Support for mobile platforms
23
Collaborative web-of-trust security review process
24
API tokens for multiple projects/packages but not every package
25
Option to overwrite a version
26
Having JSON API Specification
27
Being able to subscribe to package publication events
28
Search result should show some kind of ranking
29
When a project or release is deleted it would be helpful to get a reason why, as with yanked releases
30
Difficulty in tracking all changes, either to one project or all of PyPI, using new endpoints
31
32
Second Survey
33
34
For feature requests in the second survey, please see minutes of the meetings
35
36
Third Survey
37
38
Namespace supportx64
39
Private packagesx54
40
Org. accountx42
41
Deal with supply-chain attacksx3
42
"pip search" featurex3
43
Exposing metadata for packages in the simple API
44
Only packages with valid metadata using current standards are served
45
Validation of basic metadata
46
Draft releases (publish all files, then trigger the release being public)
47
Better authorization, suitable for CI / CD
48
Authenticate with github CI token
49
Browsing PYPI using command line
50
Tie the test environment's authentication and packages to the production version
51
Upload third party compiled wheels
52
Useful to have a software/package you can run on your PC/network and can act like a proxy/cache with pypi so it store all past installed packages and synchronize them to avoid download when you need or also when you are off-line (or pypi is down)
53
Support the json API as the first class api for packages. Include all the metadata in json.
54
Dependency metadata
55
Being able to Auth with GitHub and/or sync permissions between the two
56
Search for packages
57
Draft packages so that the version namespace isn’t reserved
58
When uninstalling package there should be way to select which dependencies to remove with it
59
Get dependencies of package without download
60
Verified packages (in that the author is verified) over namespaces, public or private
61
Deprecate unmaintained packages by some mechanism
62
PyPi public API
63
Managing versions not easy enough
64
Framework for restricting access to packages based on user auth, with custom auth plugin support
65
Protect from misspellings being used on popular packages
66
Package download stats via API
67
Build wheels for C-extensions
68
Suport for RST admonition in the package description
69
Upload size limits whitelist configuration per namespace
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100