Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork1.9k
Closed
Milestone
Description
This is an internal tracking issue which will tie in the related issues which will be tackled/still need to be updated for the purposes of cutting the release. It's been a long time coming (see#4058 (comment) and#3742 (comment) for some past comments on that) and there's a tentative goal of getting a pre-release out in March 2020.
(Edited by@brainwane to say: fixing some brokenness in the continuous integration setup is delaying this release 2020.04.1a1 till -- new estimate -- 21 April 2020.)
(Edited by@brainwane to say: the prerelease2020.4.1b1is now out, as of 29 April, and Dan aims to get the next release out in about a week.)
(Edited by@brainwanein conversation with Dan on 5 March 2020 and then throughout March & April)
- Other Items inthe March 2020 release milestone:
- Pipenv installs wrong packages (ignoring package lock) #3613 Pipenv installs wrong packages (ignoring package lock)
- Change docs links to pipenv.pypa.io #4137 Update
READMEandRead the Docs project to point to docs at pipenv.pypa.io
- Fix
pip-shimstest failures (mergethebugfix/56branch) requirementslibfixes:- AST parsing of setup.py fails on non-addition type binOps sarugaku/requirementslib#204
requirementslibissue AST parsing ofsetup.pyfails on non-addition typebinOps - AST parsing fails on non-utf8 setup.py files sarugaku/requirementslib#205 AST parsing fails on non-utf8
setup.pyfiles - We shouldn't install upgraded versions of test dependencies in CI sarugaku/requirementslib#214 We shouldn't install upgraded versions of test dependencies in CI
- Add requirement calculator for artifacts in pypi sarugaku/requirementslib#219 calculator Add requirement calculator for artifacts in PyPI
- Review
requirements-libissues for other pipenv release blockers
- AST parsing of setup.py fails on non-addition type binOps sarugaku/requirementslib#204
- Make new releases of related libraries:
- Finish, approve and mergeUpdate vendored dependencies, relevant API usage, and CI config #4169 to address missing dependencies/imports
- Fix news entry/entries
- Fix broken CI configuration
- Get tests to pass
- FixYour API Key is invalid #4188 by either getting pyup API key working again or choosing and implementing an alternative
- Get GitHub tests to pass on master (skipping the test mentioned inDebug test_install_markers for python 3.6 in github CI #4201)
- Improve release automation to allow generation of prereleases
- Generate changelog in draft mode
- Don't autotag & push tag to repo
- Update and run through "Test locally" and "Uploading the release" forpackaging/release checklist
- Package and upload pipenv prerelease version 2020.04.1a1to PyPI
That's what Dan aims to do by 21 April 2020. Then:
- Make another new release ofrequirementslib that incorporates a fix toparsing setup.cfg via setuptools is currently broken sarugaku/requirementslib#216
- Relock requirementslib dependencies
- Publicize pre-release and ask for a week of testing
- Especially testing on Windows against PEP 517 backends and involving virtualenvs
- After ~1 week (if no showstopper bugs), publish new release
How others can help:
- replying to new users' questions in pipenv's GitHub issues
- help developa "Pipenv workflows to test" list,along these lines
Metadata
Metadata
Assignees
Labels
No labels