Re: upcoming work to facilitate PyPA communications/roadmaps

[Dan Ryan]

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: Trying to outline the steps taken to go from "I want this package" to it being installed

[Brett Cannon]

On Sat, 22 Dec 2018 at 12:22, Brett Cannon  wrote:

>
>
> On Fri, 21 Dec 2018 at 12:08, Sumana Harihareswara 
> wrote:
>
>> Brett, did you end up making progress on this? If not, would you be open
>> to someone else picking it up?
>>
>
> The complete outline can be found in an email I sent to pypa-dev and I
> have started work by trying to add PEP 425 support to 'packaging':
> https://github.com/pypa/packaging/pull/156 .
>

I realized I should have clarified by saying, "and if anyone else wants to
take on something from that outline that needs doing then feel free!" :)

-Brett


>
> -Brett
>
>
>>
>> Thanks!
>>
>> --
>> Sumana Harihareswara
>> Changeset Consulting
>> https://changeset.nyc
>>
>> On 3/5/18 1:01 PM, Brett Cannon wrote:
>> > Thanks for the extra details, Nick! I have some documentation to read on
>> > some projects now that I have a complete list, but once that's done I'll
>> > come back here with my idea. ;)
>> >
>> > On Fri, 2 Mar 2018 at 21:50 Nick Coghlan  wrote:
>> >
>> >> On 3 March 2018 at 06:55, Brett Cannon  wrote:
>> >>
>> >>> I have a project idea, but before I start it I need to make sure that
>> I
>> >>> have the high-order steps necessary to go from `pip install
>> pip=9.0.1` to
>> >>> it actually ending up on disk. Now I'm only considered with
>> >>> modern/bleeding-edge, spec-based stuff, so PEP 517/518 and no
>> setup.py, etc.
>> >>>
>> >>> Anyway, if people can point out any steps the below outline is
>> missing I
>> >>> would appreciate it. Thanks!
>> >>>
>> >>>
>> >>>1. Specify package requirement
>> >>>   1. Translate name to PyPI-compatible name
>> >>>   2. Tease out requirement details (e.g. version, markers, etc.)
>> >>>2. Check if package is already installed
>> >>>
>> >>>
>> >> Depending on the installer design, a local download/build cache may be
>> >> checked before checking PyPI (and since you include a caching step
>> later,
>> >> you'll presumably want to cover the caching step as well).
>> >>
>> >>
>> >>>
>> >>>1. Check PyPI for package
>> >>>2. Choose appropriate file
>> >>>   1. Get list of files
>> >>>   2. Calculate best-fitting wheel
>> >>>   3. Fallback to .tar.gz sdist
>> >>>3. Download file
>> >>>4. If sdist:
>> >>>   1. Extract
>> >>>   2. Read pyproject.toml
>> >>>   3. Create venv
>> >>>   4. Install build dependencies
>> >>>
>> >>>
>> >> After installing the static build dependencies, you also need to query
>> for
>> >> any dynamic build dependencies and install them if they're requested:
>> >> https://www.python.org/dev/peps/pep-0517/#get-requires-for-build-wheel
>> >>
>> >> This build dependency installation step can get arbitrarily
>> complicated if
>> >> you allow build dependencies to be installed from source, so the
>> initial
>> >> implementation in pip requires that build dependencies already be
>> available
>> >> as wheel files (either on the index server or in the local artifact
>> cache).
>> >>
>> >> Cheers,
>> >> Nick.
>> >>
>> >> --
>> >> Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia
>> >>
>> >
>>
>