Nick Coghlan ncoghlan at gmail.com writes:
I'm not a fan of post-install hooks - that way lies setup.py. If
people want to run arbitrary code at install time, they can publish a
platform specific installer.
*Maybe* we can go down that path in the Python 3.5 timeframe, but for now, no.
I'm
On Wed, Feb 27, 2013 at 8:52 PM, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
Just to clarify: when I say hooks, what I mean is setuptools-style entry
points that the installer looks for, which are used to customise the
installation
process.
The command to create a wheel from a source archive
On Wed, Feb 27, 2013 at 6:45 AM, Nick Coghlan ncogh...@gmail.com wrote:
On Wed, Feb 27, 2013 at 8:52 PM, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
Just to clarify: when I say hooks, what I mean is setuptools-style entry
points that the installer looks for, which are used to customise the
The Packaging Summit page [1] lists Friday evening but doesn't specify a time
or location, as far as I can tell. Have those been set, yet?
Doug
[1]
https://us.pycon.org/2013/community/openspaces/packaginganddistributionminisummit/
___
Distutils-SIG
Daniel Holth dholth at gmail.com writes:
Vinay's distlib has taken the wheel spec at its word, runs an
unmodified install command with all the various paths set to
wheel-compatible distname-1.0.data/scripts etc., and converts the
.egg-info directory to .dist-info the same as bdist_wheel's
On Wed, Feb 27, 2013 at 10:08 AM, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
Daniel Holth dholth at gmail.com writes:
Vinay's distlib has taken the wheel spec at its word, runs an
unmodified install command with all the various paths set to
wheel-compatible distname-1.0.data/scripts etc., and
I have a question about the compatibility tags used by Wheel (PEP 425) and their
completeness on Windows. IIUC, it may not be enough to consider the platform and
the Python ABI (determined by the Python version). In addition, on Windows, we
may have to consider the version of compiler used to
On Wed, Feb 27, 2013 at 12:23 PM, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
I have a question about the compatibility tags used by Wheel (PEP 425) and
their
completeness on Windows. IIUC, it may not be enough to consider the platform
and
the Python ABI (determined by the Python version).
Daniel Holth dholth at gmail.com writes:
That is a concern, there seem to be a nearly unlimited number of ways
that binaries can be incompatible with your platform, I believe some
numpy stuff includes the version of a numeric library in their
(non-wheel) system.
I designed that assuming
On Feb 27, 2013, at 2:52 AM, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
Nick Coghlan ncoghlan at gmail.com writes:
I'm not a fan of post-install hooks - that way lies setup.py. If
people want to run arbitrary code at install time, they can publish a
platform specific installer.
*Maybe*
On Wed, Feb 27, 2013 at 1:01 PM, Vinay Sajip vinay_sa...@yahoo.co.ukwrote:
The trouble is, mistakes happen, and people can upload stuff built with the
wrong compiler without realising - say, corporates who build their own
Pythons, perhaps for embedding scenarios. It may be that in some
On Wednesday, February 27, 2013 at 1:47 PM, Glyph wrote:
On Feb 27, 2013, at 2:52 AM, Vinay Sajip vinay_sa...@yahoo.co.uk
(mailto:vinay_sa...@yahoo.co.uk) wrote:
Nick Coghlan ncoghlan at gmail.com (http://gmail.com/) writes:
I'm not a fan of post-install hooks - that way lies
On 27 February 2013 18:49, Chris Lambacher ch...@kateandchris.net wrote:
On Wed, Feb 27, 2013 at 1:01 PM, Vinay Sajip vinay_sa...@yahoo.co.uk
wrote:
The trouble is, mistakes happen, and people can upload stuff built with
the
wrong compiler without realising - say, corporates who build their
On Feb 27, 2013, at 11:04 AM, Daniel Holth dho...@gmail.com wrote:
What does it have to do in the hook?
This: https://twistedmatrix.com/documents/current/core/howto/plugin.html#auto3
While this is theoretically optional - Twisted will behave mostly correctly
without it - it noticeably
On Feb 27, 2013, at 10:49 AM, Donald Stufft donald.stu...@gmail.com wrote:
I'm generally +1 on hooks, the failure of setup.py isn't particularly that
it's executable, it's that you can't access the metadata without executing
it. In general hooks also allow people to easily disable them during
On Mon, Feb 25, 2013 at 9:39 AM, Nick Coghlan ncogh...@gmail.com wrote:
(This probably belongs in a successor to PEP 376, but I'll leave it
under the PEP 426 umbrella for now)
One of the points raised regarding PEP 426's integrated metadata
format is the potential for runtime issues with
On Wed, Feb 27, 2013 at 4:48 PM, PJ Eby p...@telecommunity.com wrote:
On Mon, Feb 25, 2013 at 9:39 AM, Nick Coghlan ncogh...@gmail.com wrote:
(This probably belongs in a successor to PEP 376, but I'll leave it
under the PEP 426 umbrella for now)
One of the points raised regarding PEP 426's
On 27 February 2013 19:47, Paul Moore p.f.mo...@gmail.com wrote:
The key on Windows is the version of the MS C runtime. That's what the
version of MSVC determines, in essence. Other than MSVC, only gcc
(mingw) is supported for building extensions, and gcc builds binaries
linking to the same
On Thu, Feb 28, 2013 at 12:32 AM, Doug Hellmann doug.hellm...@gmail.com wrote:
The Packaging Summit page [1] lists Friday evening but doesn't specify a
time or location, as far as I can tell. Have those been set, yet?
Doug
[1]
On Thu, Feb 28, 2013 at 7:59 AM, Daniel Holth dho...@gmail.com wrote:
My aim is to provide a hook mechanism that specifically does not say
anything about the way the cache is stored or even whether the hook
produces a cache at all. It will just run when pip is done.
How does the following idea
On Thu, Feb 28, 2013 at 5:47 AM, Paul Moore p.f.mo...@gmail.com wrote:
It's certainly true that the ABI flags are incomplete (there's also
the whole stable ABI to consider).
The stable ABI is covered in PEP 425: the stable ABI compatibility tag
is abi3, and you use the Python version tag to
21 matches
Mail list logo
