Hey all --
With Sumana's help, I've been working to get the next pipenv release out by the end of the month. As some of you may already know, I recently changed jobs and am now working for Canonical where I have part of my time allocated to open source work in general (and pipenv in particular).
The main pipenv release blockers have been fixes in andnew releases of requirementslib, pythonfinder, pip-shims, and vistir, and merging https://github.com/pypa/pipenv/tree/feature/vendor-updateto address missing dependencies/imports.I've beenworking on these and should wrap up this week.||
You can help in a few ways:
I'd appreciate the help.
Thanks, -Dan Ryan (techalchemy)
|:| You can look at https://github.com/pypa/pipenv/issues/3742#issuecomment-492100711and https://github.com/pypa/pipenv/issues/4058#issuecomment-565550646for more context on why we've been delayed on a new release since November 2018. ||: Iacknowledge that I've been super behind on this release,but I also have moved, had a fire in my new house, changed jobs, etc., and am onlynowsettling into my new role where I finally am paid to spend some time on pipenv.So, after this release is out, I hope to get back to helping new contributors more so we can promote some more co-maintainers, so this doesn't block releases again.
-- Dan Ryan @techalchemy | Pipenv Maintainer
Thanks Dan! Some further comments inline.
On 3/25/20 4:33 PM, Dan Ryan wrote:
A few specific documentation bugs that people could help with:
And, because error logs and autogenerated lockfiles include documentation, some "give people info so they can troubleshoot better" issues they could use help with:
As you probably guessed, I did not write this line. :-) Thanks, Dan.
-- Sumana Harihareswara Changeset Consulting https://changeset.nyc