|
Size: 3287
Comment: pip resolver blockers
|
← Revision 39 as of 2020-06-05 22:32:24 ⇥
Size: 808
Comment: moved to GitHub
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| This page lists specific things that | The [[https://github.com/psf/fundable-packaging-improvements|Fundable Packaging Improvements repository]] lists specific things that |
| Line 7: | Line 7: |
| 3. would happen much faster if the Packaging Working Group got funding to achieve them | 3. would happen much faster if the [[PackagingWG|Packaging Working Group]] got funding to achieve them (through [[http://donate.pypi.org/|donations]] or grants/directed gifts) |
| Line 9: | Line 9: |
| That list [[https://wiki.python.org/psf/Fundable%20Packaging%20Improvements?action=info|was previously on this wiki page]] and has now been moved [[https://github.com/psf/fundable-packaging-improvements|to GitHub]]. | |
| Line 10: | Line 11: |
| == Projects == === finish dependency resolver for pip === See [[https://github.com/pypa/pip/issues/988|pip issue #988]] and [[https://github.com/pypa/pip/issues/6536|#6536]]. This includes help with user experience, communications/publicity, and testing (including developing robust testing/CI infrastructure) as well as, potentially, core feature development and review. We need to finish this because so many other improvements are blocked on it, such as: * [[https://github.com/pypa/pip/issues/4551|adding an "upgrade-all" command to pip]] * [[https://github.com/pypa/pip/issues/5497|warning when trying to download or build wheels from incompatible set of packages/requirements]] * [[https://github.com/pypa/pip/issues/4745|adding a no-implicit-upgrades strategy]] * [[https://github.com/pypa/pip/issues/4681|warning the user when uninstalling a package that other packages depend on]] and it would fix so many dependency issues for our users, such as: * [[https://github.com/pypa/pip/issues/4907|Django installation conflict]] * [[https://github.com/pradyunsg/zazo/issues/2|cherrypy/six/cheroot installation conflict]] * [[https://github.com/pypa/pip/issues/5043|Spyder downgrade requirement]] * [[https://github.com/pradyunsg/zazo/issues/4|boto3/bravado dependency failure]] * [[https://github.com/pypa/pip/issues/5313|Ansible/PyOpenSSL/cryptography failure]] And in our larger ecology, this causes installation problems -- for example: * [[https://github.com/antocuni/capnpy/issues/16|a Cap'n Proto implementation]] * [[https://github.com/DataBiosphere/toil/issues/2230|toil, awscli, and boto3]] * [[https://github.com/mozilla/bedrock/issues/5967|the Mozilla website & icalendar]] * [[https://github.com/certbot/certbot/issues/5195|certbot, in the past and possibly the future]] * [[https://github.com/TurboGears/tg2devtools/issues/13|TurboGears]] * [[https://github.com/pycontribs/jira/pull/744|a JIRA API client library]] * [[https://github.com/crossbario/autobahn-testsuite/issues/55|a WebSocket protocol test suite]] === Robust interoperability testing === We need funding to ensure core packaging tools work well with each other; currently they aren't seamlessly interoperable. See [[https://github.com/pypa/integration-test|the integration-test project]]. === System for generic statuses/flags on projects on PyPI === See [[PackagingWG/2019-03-22-Warehouse|notes from this meeting]]. To scale up our anti-abuse moderation, we need to be able to, for instance, mark a release as deprecated or a project as unsupported. We need support to do the architectural design to implement this. === Feature flag system on PyPI === It's difficult to roll out new features gradually to our test site or to selected test users; a feature flag system would help us deploy more confidently. See [[https://github.com/pypa/warehouse/issues/5869|this GitHub issue]]. == virtualenv rewrite == See [[https://github.com/pypa/virtualenv/pull/697|virtualenv issue #697]]. |
Please contact the Packaging WG to ask us to estimate how much one of these improvements would cost; we'll get back to you within a few business days. |
Packaging improvements that could be funded
The Fundable Packaging Improvements repository lists specific things that
- the Python packaging community wants
- are fairly well-scoped
would happen much faster if the Packaging Working Group got funding to achieve them (through donations or grants/directed gifts)
That list was previously on this wiki page and has now been moved to GitHub.
Please contact the Packaging WG to ask us to estimate how much one of these improvements would cost; we'll get back to you within a few business days.