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 and new
releases of requirementslib, pythonfinder, pip-shims, and
vistir, and merging https://github.com/pypa/pipenv/tree/feature/vendor-update
to address missing dependencies/imports. I've
been
working on these
and
should wrap up this week.[0]
You
can help in a few ways:
2.
If you see me in #pypa-dev on Freenode IRC, feel free to ask me
what I'm working on. Sumana's been keeping me focused this month
(and helped me write up the tracking issue, and this email) and
it's been helpful, as I am juggling a lot of obligations and can
get distracted.[1]
3. I
could use help replying to new users' questions in pipenv GitHub
issues, so I can concentrate on the new release. If
you'd like triage permissions on the project please reach out,
I'd be happy to give them.
4.
Documentation! Pipenv documentation,
now at https://pipenv.pypa.io/
, needs
some serious rework.
So if you
have any skills in this area, the
project would really benefit from a critical review here.
5. Make
sure to say 'thanks' to Sumana if you see her on IRC, she is
responsible for moving this release forward and is pretty great!
I'd
appreciate the help.
Thanks,
-Dan
Ryan (techalchemy)
[1]
:
I
acknowledge 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 only
now
settling 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