Announcement: Pipenv Beta Release
Greetings all! I am happy to announce that after a long hiatus, there is a pre-release of pipenv available for testing. You can read the full announcement at https://discuss.python.org/t/announcement-pipenv-beta-release/4051 I look forward to your feedback. Thanks, Dan -- Dan Ryan Software Engineer | Pipenv Maintainer Canonical, Ltd. | Python Packaging Authority dan.r...@canonical.com | d...@danryan.co -- You received this message because you are subscribed to the Google Groups "pypa-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to pypa-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pypa-dev/d36dc589-1ca1-67ae-41bf-21288920fdbe%40danryan.co.
Next Pipenv Release
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.|[0]| You can help in a few ways: 1. Look at the tracking issue for the new release https://github.com/pypa/pipenv/issues/3369and speak up there if you know of a release blocker that isn't in the list. 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) |[0]:| 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. |[1]|: 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 -- You received this message because you are subscribed to the Google Groups "pypa-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to pypa-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pypa-dev/7e77dccc-df48-4e54-1dd1-44caf21bde68%40danryan.co.
Re: upcoming work to facilitate PyPA communications/roadmaps
This is great news! Looking congrats and glad to have you back with us! Dan Ryan // pipenv maintainer gh: @techalchemy > On Dec 24, 2018, at 3:13 PM, Sumana Harihareswara wrote: > > It's been eight months since the release of Warehouse[0] and the sunsetting > of legacy PyPI[1]. Following up from our meeting at PyCon in May[2], > Changeset Consulting is back on board for another round of project management > to facilitate next steps! For the next 3-6 months this work will be > spearheaded by myself (Sumana) assisted by Jenny Ryan (https://jennyryan.net > ). > > The goal over these upcoming months is to create, steward and facilitate > internal and public-facing communications to aid the folks within PyPA. > > What this means is that we'll be focused on the following: > * Facilitating regular meetings of and for maintainers and contributors; > * Stewarding communications with various PyPA stakeholders, including funders > and users; > * Organizing, labelling, prioritizing, and responding to GitHub issues; > * Coordinating public communications, such as announcements, sprints, and > calls for participation; > * Maintaining and improving documentation, meeting notes and development > roadmaps for PyPA projects. > > Feedback from and participation by the Python packaging developer community > is obviously part and parcel of this project, so you may see some new "here's > what I think is up with this issue, is that right?" questions on old > unresolved discussions. And we'll be asking questions on this & other lists > and on GitHub and in IRC to collect ideas, concerns, and other productive > input regarding the tools roadmaps. > > You'll be seeing more details in mid-January to properly kick off this next > chapter of levelling up PyPI and the PyPA -- just wanted to give y'all a > heads-up. > > But of course, if you were already planning on using the next few weeks to do > issue triage and roadmap-writing and PyCon planning, please don't wait for us > -- that'll make this work all the easier. > > Thanks, > Sumana Harihareswara > > > [0] > https://blog.python.org/2018/04/new-pypi-launched-legacy-pypi-shutting.html > [1] > https://mail.python.org/archives/list/distutils-...@python.org/thread/YREMU56QKRMTTFBFVFJ2B4EHOEKOJZFJ/ > [2] > https://mail.python.org/archives/list/distutils-...@python.org/thread/CCOV6PITEWELONZHP4ZHXALBFQA3K3MY/ > > -- > Sumana Harihareswara > Changeset Consulting > https://changeset.nyc
Re: [Distutils] Announcement: Pip 10 is coming, and will move all internal APIs
FWIW we are using quite a bit of the internal api. My plan was to go over this once we cut over to the new warehouse uris. Of note might be the fact that pip-tools is a core dependency we bundle in pipenv and the current maintainer is a pipenv maintainer as well. For our specific case we have made sizeable changes to the dependency resolution stack and bundling allows us to patch freely. I don’t know that we are a good example though, we are doing significantly more with pip internals than the average project -dan Dan Ryan // pipenv maintainer gh: @techalchemy > On Apr 14, 2018, at 11:24 PM, Nick Coghlan <ncogh...@gmail.com> wrote: > >> On 15 April 2018 at 07:31, Donald Stufft <don...@stufft.io> wrote: >> >> On Apr 14, 2018, at 4:57 PM, Matthew Brett <matthew.br...@gmail.com> wrote: >> >> Is the suggestion to use the `_internal` import, or carry a copy of >> the pep425tags code myself, that I have to keep up to date with the >> internal pip copy? That would also involve me copying the `glibc` >> part of the code. I see that the `wheel` package has an old copy of >> that code too, which doesn't deal with manylinux wheels.You >> probably saw that `pip-tools` ended up vendoring the whole of pip9 >> [1]. >> >> The best solution is to figure out what APIs people need, and either add >> them to packaging and have pip consume that as well as anyone else, or make >> a new library for the same. >> >> If that’s unacceptable, vendoring or version pinning is probably the best >> option. > > I think there are going to be at least two steps involved for most > projects affected by the API change: > > 1. The quick fix to add pip 10 compatibility (which is likely a matter > of "copy the code you need into the project that needs it") > 2. The technical debt reduction to reduce code duplication (which is > likely a matter of "add the required APIs to the 'packaging' project") > > Step 2 is the step that the pip internals refactoring is designed to > encourage, as we believe a lot of tool developers were just using > pip's internal APIs rather than filing RFEs and submitting PRs to help > guide the evolution of the stable APIs in packaging in a use-case > driven manner. > > FWIW, `pipenv`'s currently still on "Step 1" at the moment (and has a > lot of internal refactoring of its own ahead of it before it will > really move on to step 2). > > Cheers, > Nick. > > -- > Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
