I don't think there is a need to be that pessimistic. Most people will even
be able to keep setup.py as is. But when you really should be sidestepping
DistUtils instead of writing a 10k line extension there is a supported path.
On Mar 21, 2014 7:37 PM, "Vinay Sajip" wrote:
>
>
> > This strategy d
On 22 March 2014 09:37, Vinay Sajip wrote:
>> This strategy does not generally try to eliminate arbitrary code
>> execution during builds - builds are an inherently arbitrary-code
>> process. But once the build has happened most installs should work
>> without arbitrary code execution.
>
> I don't
> This strategy does not generally try to eliminate arbitrary code
> execution during builds - builds are an inherently arbitrary-code
> process. But once the build has happened most installs should work
> without arbitrary code execution.
I don't think builds should be a *completely* arbitrary
On Fri, Mar 21, 2014 at 1:46 PM, Daniel Holth wrote:
> Bento emulates setup.py:
> https://github.com/cournape/Bento/blob/master/setup.py
>
> It mostly has to implement egg_info and install to be pip compatible.
>
Yes. While some things are quite not ideal in Bento, I think that part is a
good on
Thank you sir!
On Mar 21, 2014, at 5:25 PM, Richard Jones wrote:
> Let's do it. PEP accepted.
>
>
> On 22 March 2014 07:51, Donald Stufft wrote:
> Ping on a decree/pronouncement for this? :]
>
> On Mar 11, 2014, at 3:53 PM, Christian Theune wrote:
>
> >
> > On 11. Mar2014, at 20:01, Donald
Let's do it. PEP accepted.
On 22 March 2014 07:51, Donald Stufft wrote:
> Ping on a decree/pronouncement for this? :]
>
> On Mar 11, 2014, at 3:53 PM, Christian Theune wrote:
>
> >
> > On 11. Mar2014, at 20:01, Donald Stufft wrote:
> >
> >> I think maybe we're ready for a decree on this? I di
Ping on a decree/pronouncement for this? :]
On Mar 11, 2014, at 3:53 PM, Christian Theune wrote:
>
> On 11. Mar2014, at 20:01, Donald Stufft wrote:
>
>> I think maybe we’re ready for a decree on this? I didn’t expect many people
>> to actually care about it since it’s unused :)
>
> I think I
On Fri, Mar 21, 2014 at 3:34 PM, Thomas Heller wrote:
> Am 21.03.2014 20:19, schrieb Daniel Holth:
>
>> 2. You are correct. We plan to switch the default to be py3-none-any
>> "runs on some Python 3 interpreter". cp33 means "only runs on CPython"
>> however we have decided this tag is probably les
Am 21.03.2014 20:19, schrieb Daniel Holth:
2. You are correct. We plan to switch the default to be py3-none-any
"runs on some Python 3 interpreter". cp33 means "only runs on CPython"
however we have decided this tag is probably less useful than
initially posited since there are other ways to say
1. No. Probably some day they will.
2. You are correct. We plan to switch the default to be py3-none-any
"runs on some Python 3 interpreter". cp33 means "only runs on CPython"
however we have decided this tag is probably less useful than
initially posited since there are other ways to say "has a C
1. question: Can wheels support a postinstall script?
Background: I'm in the process of setting up a build script for that
part of our company's software that is ported to Python 3.4.
I am using either wheels built by 'pip wheel' and cache them locally,
or, if this doesn't work (numpy and pywin3
On Mar 21, 2014, at 2:50 PM, Tres Seaver wrote:
> Signed PGP part
> On 03/21/2014 02:37 PM, Paul Moore wrote:
> > Again, though, that's only needed for "pip wheel" or for the
> > install-direct-from-source cases that may not even be expected to
> > work in the new metabuild system...
>
> Hmm, t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/21/2014 02:37 PM, Paul Moore wrote:
> Again, though, that's only needed for "pip wheel" or for the
> install-direct-from-source cases that may not even be expected to
> work in the new metabuild system...
Hmm, that is a clear case of baby-with-
On Fri, Mar 21, 2014 at 2:37 PM, Paul Moore wrote:
> On 21 March 2014 17:56, Daniel Holth wrote:
>> You do need to keep a mechanism to indicate & install build dependencies.
>
> Do we have that at the moment? Metadata 2.0 covers that with
> build_requires. At the moment setup_requires covers it,
On 21 March 2014 17:56, Daniel Holth wrote:
> You do need to keep a mechanism to indicate & install build dependencies.
Do we have that at the moment? Metadata 2.0 covers that with
build_requires. At the moment setup_requires covers it, but I don't
know if/how that works (AIUI, setup_requires is
On Fri, Mar 21, 2014 at 10:25 AM, Paul Moore wrote:
> On 21 March 2014 13:46, Daniel Holth wrote:
>> It mostly has to implement egg_info and install to be pip compatible.
>
> At a *very* brief scan, pip uses just the following setup.py
> invocations (this definitely needs to be properly audited b
On Fri, Mar 21, 2014 at 10:25 AM, Paul Moore wrote:
> On 21 March 2014 13:46, Daniel Holth wrote:
>> It mostly has to implement egg_info and install to be pip compatible.
>
> At a *very* brief scan, pip uses just the following setup.py
> invocations (this definitely needs to be properly audited b
On 21 March 2014 13:46, Daniel Holth wrote:
> It mostly has to implement egg_info and install to be pip compatible.
At a *very* brief scan, pip uses just the following setup.py
invocations (this definitely needs to be properly audited before
relying on it):
For installation from sdist
* setup.py
Bento emulates setup.py: https://github.com/cournape/Bento/blob/master/setup.py
It mostly has to implement egg_info and install to be pip compatible.
In the future we'd like them to implement dist_info (generate a
.dist-info directory instead of an .egg-info directory) and wheel; an
sdist would s
On 20 Mar 2014 23:16, "Brett Cannon" wrote:
>
>
>
> On Thu Mar 20 2014 at 12:51:13 AM, Nick Coghlan
wrote:
>>
>> On 20 March 2014 09:54, Vinay Sajip wrote:
>> > Daniel Holth gmail.com> writes:
>> >
>> >> extensions without using distutils. The problem of invoking the
>> >> compiler has been sol
20 matches
Mail list logo
