On Thu, Jun 6, 2013 at 6:00 AM, Jussi Pakkanen wrote:
>
> On Wed, Jun 5, 2013 at 10:37 PM, Chris Angelico wrote:
>
>>
>> Since you're talking about a bootstrap requirement here, the obvious
>> question is: What version of Python 3 does it require? Will it be a
>> lot of hassle to get hold of (say
What's the advantage in writing a new build tool? I'm asking this because I'm
doing the same using scons:
https://bitbucket.org/cavallo71/fatpython
At the moment I'm very interested into this problem: the main advantages I see
so far are (in scons) are node dependencies and the fact it is pla
Hi. My 2 cents about this: (well I'm only a noob)
I had this problem; I don't know about other people's environment, but
my environment's problem was that it was actually not POSIX-compliant:
it didn't have other file functions as well, but anyway the `fstat`
error is the FIRST error you get w
On Wed, Jun 5, 2013 at 10:37 PM, Chris Angelico wrote:
> Since you're talking about a bootstrap requirement here, the obvious
> question is: What version of Python 3 does it require? Will it be a
> lot of hassle to get hold of (say) Python 3.2, only to uninstall it
> when you have your 3.4 built
On Thu, Jun 6, 2013 at 5:21 AM, Jussi Pakkanen wrote:
> - implementation of Meson is 100% Python 3, it does not have a dependency on
> the shell and in fact already works on Windows
Since you're talking about a bootstrap requirement here, the obvious
question is: What version of Python 3 does it
Hello all
I'd like to start this email by saying this is not a proposal to change
Python's build system. This is just the results of some experimentation you
might be interested it.
I have been working on a cross-platform build system called Meson, which is
implemented in Python 3. For symmetry I
Le 05/06/2013 18:10, Benjamin Peterson a écrit :
I (and Guido) are accepting PEP 442 (Safe object finalization) on the
condition that finalizers are only ever called once globally.
Congratulations to Antoine on writing yet another PEP that deeply
touches the core language in a way that everyone
I (and Guido) are accepting PEP 442 (Safe object finalization) on the
condition that finalizers are only ever called once globally.
Congratulations to Antoine on writing yet another PEP that deeply
touches the core language in a way that everyone can agree is an
improvement.. I look forward to rev
Dnia 5 cze 2013 o godz. 16:31 Brett Cannon napisał(a):
> Any chance you could move your definitions for "generic function" and "single
> dispatch" to the glossary and just link to them here?
Sure thing.
--
Ł
___
Python-Dev mailing list
Python-Dev@py
On 2/06/2013 3:12 PM, Kubilay Kocak wrote:
> Afternoon (UTC+10),
>
> I'd like to request a new user/pass for a FreeBSD 10.0-CURRENT VM guest
> I've just setup as a dedicated buildbot slave to complement my other
> koobs-freebsd slaves.
>
> Also, with this and future additions to the FreeBSD build
On 5 cze 2013, at 09:29, Markus Unterwaditzer wrote:
> As somebody who missed the discussion about it and right now took a quick
> look at the PEP, i ask myself how subclasses are handled, as i don't see
> anything about it in the PEP, just support for ABCs.
>
> E.g if
>
>issubclass(Apple
On Wed, Jun 5, 2013 at 5:29 PM, Markus Unterwaditzer
wrote:
> As somebody who missed the discussion about it and right now took a quick
> look at the PEP, i ask myself how subclasses are handled, as i don't see
> anything about it in the PEP, just support for ABCs.
>
> E.g if
>
> issubclass(
As somebody who missed the discussion about it and right now took a quick look
at the PEP, i ask myself how subclasses are handled, as i don't see anything
about it in the PEP, just support for ABCs.
E.g if
issubclass(Apple, Fruit)
And i call a function which has registered an implementati
On 5 June 2013 02:32, Guido van Rossum wrote:
> Łukasz,
>
> Congratulations! I've accepted PEP 443. I've already marked it as
> Accepted in the repo. I've also applied some very minor edits in order
> to make the text flow a little better in a few places. I think this is
> a great PEP -- it's sim
14 matches
Mail list logo