Sadly the current version of pipenv available in homebrew has broken support for pyenv. While it's possible to install pipenv from master, it would still be a good idea to release a new version as soon as possible. Otherwise you risk that people who try pipenv for the first time might get a misleading first impression. Additionally even seasoned pipenv users suffer from having to do a web search to find a workaround to fix their work environment.
adonig
All 9 comments
It also seems it's time to have a proper regular Next Release according to the _Project Board_:
https://github.com/pypa/pipenv/projects/8
The only issue in the project board not in the _Done_ column has already been closed: https://github.com/pypa/pipenv/issues/2359
We've not had a release since _Nov 26, 2018_ and it's end of March 2019 (4 months). I suspect enough things have been improved/fixed since then that many people are still running into trouble they could be avoiding with just the latest release 🤔
Thank you for your work 🙇
whyboris
on 25 Mar 2019
To be fair, I have no idea what that project is -- apologies for the delay on this but we had significant delays getting CI builds passing with updates to pip, piptools, and other resolver issues. Each delay has added up to over a week at a time and this is a project that happens in our free time -- and it is super complicated to push a release with so many moving parts coming together. I _will_ get one out this week, which is about a week or two behind when I _actually_ planned to cut a release.
techalchemy
on 26 Mar 2019
Thanks for the hard work @techalchemy. Also looking forward to restoring pyenv support. ❤️
AlJohri
on 9 Apr 2019
Hi wonderful contributors! Is there any chance this is in the works, or could use some help getting things ready for release?
miketheman
on 2 May 2019
AlJohri
on 22 May 2019
why you no?
(Thank you for your hard work!)
amir-barkal
on 29 May 2019
@amir-barkal -- it's very likely you meant the image in a jovial fashion (it's a funny meme, I like it too), but it's easy to misread people on the internet, and the maintainers of the repository might feel as if you're _demanding_ they do something (which isn't pleasant).
In the future, a comment like this accompanying with a comment below saying something like "thank you for your hard work 🙇♂️" would remove the ambiguity 😉
whyboris
on 30 May 2019
Apologies to anyone if I have offended them, that was never my intention.
@whyboris I’ve edited the comment as per your kind advice. Thank you.
amir-barkal
on 31 May 2019
Redirect #3742
frostming
on 20 Jun 2019
Related issues
konstin
·
3Comments
johnjiang
·
3Comments
bgjelstrup
·
3Comments
ipmb
·
3Comments
fbender
·
3Comments
Most helpful comment
To be fair, I have no idea what that project is -- apologies for the delay on this but we had significant delays getting CI builds passing with updates to pip, piptools, and other resolver issues. Each delay has added up to over a week at a time and this is a project that happens in our free time -- and it is super complicated to push a release with so many moving parts coming together. I _will_ get one out this week, which is about a week or two behind when I _actually_ planned to cut a release.