On 5 July 2017 at 15:49, Donald Stufft wrote:
> I’ve had a niggling feeling about this hook from the beginning, but I
> couldn’t quite put my finger on it until Nathaniel’s email made me realize
> it. I feel like this hook is really *only* useful for flit, and for other
> projects it is largely ei
> On Jul 4, 2017, at 11:53 PM, Nick Coghlan wrote:
>
> While it would definitely be useful to have a "check build
> consistency" tool that built wheel files via all defined paths and
> then used diffoscope to compare them, having such a tool available
> wouldn't be a prerequisite for PEP accepta
While the topic of shutting down pythonhosted.org has come up, on and off, for
a few years, there is one certain thing: The recommended documentation hosting
platform of the python community is readthedocs.org.
> -Original Message-
> From: Distutils-SIG [mailto:distutils-sig-bounces+trit
On 5 July 2017 at 10:45, Nathaniel Smith wrote:
> I already responded to several of the overall points elsewhere in the
> thread, but a few specific points:
>
> On Mon, Jul 3, 2017 at 7:03 AM, Nick Coghlan wrote:
>> I want prepare_wheel_metadata there as a straightforward way for
>> backends to e
On 5 July 2017 at 03:24, Donald Stufft wrote:
> It occurs to me that your case here is actually a reason *not* to implement
> this hook. The goal of the hook is that the wheel built from the tree
> created by copying this file is the same as the wheel built from a sdist
> created from that same VC
I already responded to several of the overall points elsewhere in the
thread, but a few specific points:
On Mon, Jul 3, 2017 at 7:03 AM, Nick Coghlan wrote:
> I want prepare_wheel_metadata there as a straightforward way for
> backends to expose the equivalent of "setup.py egg_info". Losing that
>
On Tue, Jul 4, 2017 at 11:03 AM, Donald Stufft wrote:
>
> I don’t think it’s (entirely) rehashing. The discussion has made me realize
> that the purported cases covered by the hook aren’t actually going to be
> covered except in a narrow set of circumstances, which suggests that it’s
> not actuall
> On Jul 4, 2017, at 1:35 PM, Thomas Kluyver wrote:
>
> On Tue, Jul 4, 2017, at 06:24 PM, Donald Stufft wrote:
>> It occurs to me that your case here is actually a reason *not* to implement
>> this hook. The goal of the hook is that the wheel built from the tree
>> created by copying this file
On Tue, Jul 4, 2017, at 06:24 PM, Donald Stufft wrote:
> It occurs to me that your case here is actually a reason *not* to
> implement this hook. The goal of the hook is that the wheel built from
> the tree created by copying this file is the same as the wheel built
> from a sdist created from that
> On Jul 4, 2017, at 3:22 AM, Thomas Kluyver wrote:
>
> On Tue, Jul 4, 2017, at 01:06 AM, Donald Stufft wrote:
>> 2) We have a VCS directory or “original development source” or whatever you
>> want to call the thing you have before a sdist that typically gets into a
>> sdist.
>> - Works on
On 4 July 2017 at 18:58, Thomas Kluyver wrote:
> On Tue, Jul 4, 2017, at 09:45 AM, Nick Coghlan wrote:
>> +1, but we should explicitly note in the rationale section of the PEP
>> that it's to cover both of the following cases:
>>
>> * build from an already unpacked and potentially edited sdist"
>>
Howdy all,
Is ‘pythonhosted.org’ still a recommended service for hosting
documentation for Python distributions? It certainly seems so, from the
page at https://pythonhosted.org/>:
This site hosts documentation uploaded by authors of packages in
the Python Package Index.
To upload
On Tue, Jul 4, 2017, at 09:45 AM, Nick Coghlan wrote:
> +1, but we should explicitly note in the rationale section of the PEP
> that it's to cover both of the following cases:
>
> * build from an already unpacked and potentially edited sdist"
> * cleanly support explicitly out-of-tree builds even
On 4 July 2017 at 17:22, Thomas Kluyver wrote:
> On Tue, Jul 4, 2017, at 01:06 AM, Donald Stufft wrote:
>
> 2) We have a VCS directory or “original development source” or whatever you
> want to call the thing you have before a sdist that typically gets into a
> sdist.
> - Works on both proposa
On 4 July 2017 at 08:22, Thomas Kluyver wrote:
> Practical objection: besides it being a VCS checkout, you need the VCS tools
> available (e.g. git on $PATH). It's not hard to imagine cases where this
> doesn't hold, e.g. installing from a directory bind-mounted into a docker
> container. Between
On Tue, Jul 4, 2017, at 01:06 AM, Donald Stufft wrote:
> 2) We have a VCS directory or “original development source” or
>whatever you want to call the thing you have before a sdist that
>typically gets into a sdist.> - Works on both proposals for setuptools
> and flit (since both can
>
16 matches
Mail list logo
