>
>
> - Will allow for both static and dynamic specification of build
> dependencies
I think you need to fill in the story on dynamic dependencies, or otherwise
this PEP will be a mystery to most people.
I *think* I understand your motivation for this, based on hearing your plan
(in another thre
On Mon, Oct 26, 2015 at 8:04 AM, Nathaniel Smith wrote:
> When this sdist is built, the resulting wheel MUST have metadata
> which is identical to the metadata present in this file, except that
> any fields with value ``__SDIST_DYNAMIC__`` in the sdist may have
> arbitrary values in the wheel.
>
On Mon, Oct 26, 2015 at 8:04 AM, Nathaniel Smith wrote:
> [TBD: should builds be performed in a fully isolated environment, or
> should they get access to packages that are already installed in the
> target install environment? The former simplifies a number of things,
> but Robert was skeptical
On 28 Oct 2015 10:08, "Nathaniel Smith" wrote:
>Though it may well make sense for
> the PyPA packaging guide to add a set of best-practice guidelines for
> build system implementors.
What would be really nice is if the new specification came with a
behavioural test suite (e.g. defined with a proj
Nathaniel,
I'm not sure what the software is supposed to do with fine grained dynamic
metadata that would make very much sense to the end user. I think you could
probably get away with a single flag Dynamic: true / false. Iff true, pip
runs the dist-info command after installing bootstrap dependen
On Tue, Oct 27, 2015 at 7:00 AM, David Cournapeau wrote:
>
>
> On Tue, Oct 27, 2015 at 1:12 PM, Daniel Holth wrote:
>>
>> The drawback of .zip is file size since it compresses each file
>> individually rather than giving the compression algorithm a larger input,
>> it's a great format otherwise.
On Tue, Oct 27, 2015 at 3:43 AM, Paul Moore wrote:
>
> On 26 October 2015 at 06:04, Nathaniel Smith wrote:
> > Here's a second round of text towards making a build-system
> > independent interface between pip and source trees/sdists. My idea
> > this time is to take a divide-and-conquer approach:
On 27 October 2015 at 13:12, Daniel Holth wrote:
> We must do the hard work to support Unicode file names, and spaces and
> accent marks in home directory names (historically a problem on Windows), in
> our packaging system. It is the right thing to do. It is not the publisher's
> fault that your
On Tue, Oct 27, 2015 at 1:12 PM, Daniel Holth wrote:
> The drawback of .zip is file size since it compresses each file
> individually rather than giving the compression algorithm a larger input,
> it's a great format otherwise. Ubiquitous including Apple iOS packages,
> Java, word processor file
The drawback of .zip is file size since it compresses each file
individually rather than giving the compression algorithm a larger input,
it's a great format otherwise. Ubiquitous including Apple iOS packages,
Java, word processor file formats. And most Python packages are small.
We must do the ha
On 26 October 2015 at 06:04, Nathaniel Smith wrote:
> Here's a second round of text towards making a build-system
> independent interface between pip and source trees/sdists. My idea
> this time is to take a divide-and-conquer approach: this text tries to
> summarize all the stuff that it seemed l
Hi all,
Here's a second round of text towards making a build-system
independent interface between pip and source trees/sdists. My idea
this time is to take a divide-and-conquer approach: this text tries to
summarize all the stuff that it seemed like we had mostly reached
consensus on in the previo
12 matches
Mail list logo