On 10/10/2011 4:21 PM, Giampaolo Rodolà wrote:
Thanks everybody for your feedback.
I created a gcode project here:
http://code.google.com/p/pycompat/
This project will be easier if the test suite for a particular
function/class/module is up to par. If you find any gaping holes, you
might file
On Mon, Oct 10, 2011 at 2:29 PM, Paul Moore wrote:
> Ideally bdist_wininst and bdist_msi would also integrate with pysetup
> and with virtual environments, but I imagine that could be pretty hard
> to make work cleanly, as Windows doesn't really support multiple
> installations of a software packa
On 10 October 2011 21:38, Vinay Sajip wrote:
>> I'm not sure what you mean by a "setup.cfg-based directory". Could
>
>> you
>> clarify, and maybe explain how you'd expect to create such an archive?
>> We may be talking at cross-purposes here.
>
> Here's how I see it: at present, you can install a
> I'm not sure what you mean by a "setup.cfg-based directory". Could
> you
> clarify, and maybe explain how you'd expect to create such an archive?
> We may be talking at cross-purposes here.
Here's how I see it: at present, you can install a project by specifying
pysetup3 install path-to-direc
Thanks everybody for your feedback.
I created a gcode project here:
http://code.google.com/p/pycompat/
2011/10/8 Antoine Pitrou :
> There's also some stuff there that is coded in C, or that will rely on
> some functionality of the core interpreter that is not easily
> emulated on previous versions
On 10 October 2011 17:12, Vinay Sajip wrote:
> Paul Moore gmail.com> writes:
>
>> I'd propose that the install arguments used in bdist_wininst be
>> transferred to bdist_dumb (or a new command bdist_binary created based
>> on the same), because the bdist_wininst zip format has the following
>> ad
Nick Coghlan gmail.com> writes:
> Should we create an informational PEP or other resource to point
> people towards some of these forwards compatibility options?
Or perhaps a page on www.python.org which is referenced by e.g. a footnote in
PEP 387 (Backwards Compatibility Policy)?
Regards,
Vin
Paul Moore gmail.com> writes:
> I'd propose that the install arguments used in bdist_wininst be
> transferred to bdist_dumb (or a new command bdist_binary created based
> on the same), because the bdist_wininst zip format has the following
> advantages:
>
> 1. Proven format, so it should deal wi
On Mon, Oct 10, 2011 at 11:47 PM, Vinay Sajip wrote:
> Giampaolo Rodolà gmail.com> writes:
>
>> This let us use different stdlib features which appeared in latest
>> Python versions (including 3.2) throughout all our code base.
>> Now, what I have in mind is to release this as a public module so
Giampaolo Rodolà gmail.com> writes:
> This let us use different stdlib features which appeared in latest
> Python versions (including 3.2) throughout all our code base.
> Now, what I have in mind is to release this as a public module so that
> everyone who cannot upgrade to a recent python versio
On 10/10/2011 12:58, Paul Moore wrote:
I've now installed VS Pro 2010. We'll see how that goes. I'd rather
avoid downgrading to VS2008 (or having both at once) just for personal
builds. But will if I have to.
Fairly sure VS2010 won't work, Paul.
At least it didn't when I was in the same situat
On 10 October 2011 12:47, Nick Coghlan wrote:
> IIRC, even the Express edition should still work once the 64 bit
> Platform SDK is installed. Regardless, the intent is that it should be
> possible to build Python with only the free tools from MS. If they
> broke the Express editions such that extr
On Mon, Oct 10, 2011 at 7:49 PM, Paul Moore wrote:
> I'd propose that the install arguments used in bdist_wininst be
> transferred to bdist_dumb (or a new command bdist_binary created based
> on the same)
bdist_zip, bdist_archive, bdist_simple would all work (bdist_binary is
redundant, given what
2011/10/10 PJ Eby :
> On Sun, Oct 9, 2011 at 4:14 PM, Paul Moore wrote:
>>
>> As regards the format, bdist_dumb is about the right level - but
>> having just checked it has some problems (which if I recall, have been
>> known for some time, and are why bdist_dumb doesn't get used).
>> Specifically
14 matches
Mail list logo
