Re: [Python-Dev] Proposed schedule for Python 3.4

Am 03.10.2012 13:54, schrieb Larry Hastings: > As for the rest of it, my understanding was that there is no longer any > great plan written in the stars for Python releases. Python releases > are comprised of whatever features people propose, implement, and are > willing to support, that they can

Re: [Python-Dev] Proposed schedule for Python 3.4

On Thu, Oct 4, 2012 at 12:32 PM, Christian Heimes wrote: > Two days ago NIST announced the SHA-3 contest winner. My wrapper of > keccak https://bitbucket.org/tiran/pykeccak/ is almost ready and just > needs some cleanup and more tests. Once it's done I'll remove the Python > 3.2 and 2.x compatibil

Re: [Python-Dev] Proposed schedule for Python 3.4

Am 04.10.2012 12:49, schrieb Dirkjan Ochtman: > On Thu, Oct 4, 2012 at 12:32 PM, Christian Heimes > wrote: >> Two days ago NIST announced the SHA-3 contest winner. My wrapper of >> keccak https://bitbucket.org/tiran/pykeccak/ is almost ready and just >> needs some cleanup and more tests. Once it'

[Python-Dev] Bootstrap issue: "select" is compiled "too late"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The relevant part: """ ranlib libpython2.7.a gcc -o python \ Modules/python.o \ libpython2.7.a -l

Re: [Python-Dev] Bootstrap issue: "select" is compiled "too late"

2012/10/4 Jesus Cea : > Any suggestion about how to solve this? Easy solutions include somehow removing the dependence on subprocess or moving the import of subprocess into the function that uses it. -- Regards, Benjamin ___ Python-Dev mailing list P

Re: [Python-Dev] Using environment variables problematic for embedded python.

Checked Python 3.4 (latest hg checkout) and this area of the code hasn't changed: pythonrun,c initstdio() reported the issue: http://bugs.python.org/issue16129 On Thu, Oct 4, 2012 at 2:51 PM, Guido van Rossum wrote: > This seems more fit for the tracker; can you file there? (Then post the > issu

Re: [Python-Dev] Bootstrap issue: "select" is compiled "too late"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/10/12 14:34, Benjamin Peterson wrote: > 2012/10/4 Jesus Cea : >> Any suggestion about how to solve this? > > Easy solutions include somehow removing the dependence on > subprocess or moving the import of subprocess into the function > that uses

Re: [Python-Dev] Proposed schedule for Python 3.4

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/10/12 17:27, Nick Coghlan wrote: > I received a fair number of complaints from people that wanted to > experiment with yield from, but couldn't, because the first alpha > wasn't out yet and they weren't sufficiently interested to go to > the ef

Re: [Python-Dev] Bootstrap issue: "select" is compiled "too late"

On Thu, Oct 4, 2012 at 9:17 AM, Jesus Cea wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 04/10/12 14:34, Benjamin Peterson wrote: > > 2012/10/4 Jesus Cea : > >> Any suggestion about how to solve this? > > > > Easy solutions include somehow removing the dependence on > > subproces

Re: [Python-Dev] Bootstrap issue: "select" is compiled "too late"

On Thu, Oct 4, 2012 at 7:54 PM, Brett Cannon wrote: > This used to be a no-no, though, because if someone called that function in > a thread during an import it would deadlock. Now Antoine reworked the locks > so I don't know if this is still true or not. You can still technically deadlock, but y

Re: [Python-Dev] Stdlib and timezones, again

It occurred to me this morning that Python already ships a set of timezone data with the Windows installer: Tcl/Tk's. Is there any way we could use that as the default on Windows? ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/m

Re: [Python-Dev] Stdlib and timezones, again

On Thu, Oct 4, 2012 at 12:01 PM, Zachary Ware wrote: > It occurred to me this morning that Python already ships a set of > timezone data with the Windows installer: Tcl/Tk's. Is there any way > we could use that as the default on Windows? I would say no. You could choose not to include Tcl/Tk in

Re: [Python-Dev] Proposed schedule for Python 3.4

Hello :) That PEP is indeed pining to the fjords. I may be able to contribute (and hopefully I can with the preliminary research and talking-to-people-about-what-they-want that I've already done that maybe hasn't made it into the draft PEP versions), but I can not currently spare the cycles to car

Re: [Python-Dev] Stdlib and timezones, again

On Thu, Oct 4, 2012 at 7:01 PM, Zachary Ware wrote: > It occurred to me this morning that Python already ships a set of > timezone data with the Windows installer: Tcl/Tk's. Is there any way > we could use that as the default on Windows? We could, but it wouldn't solve any of the problems that n

[Python-Dev] Split unicodeobject.c into subfiles?

Hi, I would like to split the huge unicodeobject.c file into smaller files. It's just the longest C file of CPython: 14,849 lines. I don't know exactly how to split it, but first I would like to know if you would agree with the idea. Example: - Objects/unicode/codecs.c - Objects/unicode/mod_fo

Re: [Python-Dev] Split unicodeobject.c into subfiles?

I like the idea. From my perspective better to use subdirectory to sake of easy finding in grep style. On Thu, Oct 4, 2012 at 11:30 PM, Victor Stinner wrote: > Hi, > > I would like to split the huge unicodeobject.c file into smaller > files. It's just the longest C file of CPython: 14,849 lines.

Re: [Python-Dev] Split unicodeobject.c into subfiles?

2012/10/4 Victor Stinner : > I only see one argument against such refactoring: it will be harder to > backport/forwardport bugfixes. I imagine it could also prevent inlining of hot paths. -- Regards, Benjamin ___ Python-Dev mailing list Python-Dev@py

Re: [Python-Dev] Bootstrap issue: "select" is compiled "too late"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/10/12 18:38, Nick Coghlan wrote: > You can still technically deadlock, but you need a circular import > *and* two different threads that start at different parts of the > cycle. Is this true for 2.7 too, or only for recent 3.x? - -- Jesús Ce

Re: [Python-Dev] Split unicodeobject.c into subfiles?

Zitat von Victor Stinner : I only see one argument against such refactoring: it will be harder to backport/forwardport bugfixes. I'm opposed for a different reason: I think it will be *harder* to maintain. The amount of code will not be reduced, but now you also need to guess what file some p

Re: [Python-Dev] Split unicodeobject.c into subfiles?

2012/10/4 Benjamin Peterson : > 2012/10/4 Victor Stinner : >> I only see one argument against such refactoring: it will be harder to >> backport/forwardport bugfixes. > > I imagine it could also prevent inlining of hot paths. It depends how the code is compiled. The stringlib is splitted in many .

Re: [Python-Dev] Split unicodeobject.c into subfiles?

2012/10/4 Victor Stinner : > 2012/10/4 Benjamin Peterson : >> 2012/10/4 Victor Stinner : >>> I only see one argument against such refactoring: it will be harder to >>> backport/forwardport bugfixes. >> >> I imagine it could also prevent inlining of hot paths. > > It depends how the code is compiled

Re: [Python-Dev] Split unicodeobject.c into subfiles?

On Thu, Oct 4, 2012 at 1:30 PM, Victor Stinner wrote: > I would like to split the huge unicodeobject.c file into smaller > files. It's just the longest C file of CPython: 14,849 lines. > ... > I only see one argument against such refactoring: it will be harder to > backport/forwardport bugfixes.

Re: [Python-Dev] Tru64 support

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/09/12 00:11, mar...@v.loewis.de wrote: > We don't need to. It's perfectly fine if it breaks - we just can't > actively remove code to support the platform. > > OTOH, if Tru64 was proposed for "unsupport", we could disable > support in 3.4, and

Re: [Python-Dev] Bootstrap issue: "select" is compiled "too late"

On Thu, Oct 4, 2012 at 5:37 PM, Jesus Cea wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 04/10/12 18:38, Nick Coghlan wrote: > > You can still technically deadlock, but you need a circular import > > *and* two different threads that start at different parts of the > > cycle. > >

Re: [Python-Dev] Split unicodeobject.c into subfiles?

> I am not siding with either side of the change yet, but an additional > argument against is that history may become less convenient to > navigate and track (e.g. hg annotate may lose information depending on > how the split is done). If new files are created using "hg cp unicodeobject.c unicode/

Re: [Python-Dev] Split unicodeobject.c into subfiles?

2012/10/4 Victor Stinner : >> I am not siding with either side of the change yet, but an additional >> argument against is that history may become less convenient to >> navigate and track (e.g. hg annotate may lose information depending on >> how the split is done). > > If new files are created usi

Re: [Python-Dev] Split unicodeobject.c into subfiles?

2012/10/5 Benjamin Peterson : > 2012/10/4 Victor Stinner : >> If new files are created using "hg cp unicodeobject.c >> unicode/newfile.c", the historic is kept. > > Yes, but you can only create one file that way. You can create as many files as you want. Try: --- hg cp unicodeobject.c unicode2.c h

Re: [Python-Dev] Split unicodeobject.c into subfiles?

On Thu, Oct 4, 2012 at 4:31 PM, Benjamin Peterson wrote: > 2012/10/4 Victor Stinner : >>> I am not siding with either side of the change yet, but an additional >>> argument against is that history may become less convenient to >>> navigate and track (e.g. hg annotate may lose information depending

Re: [Python-Dev] Split unicodeobject.c into subfiles?

On 10/4/2012 4:30 PM, Victor Stinner wrote: > Hi, > > I would like to split the huge unicodeobject.c file into smaller > files. It's just the longest C file of CPython: 14,849 lines. What problem are you trying to solve? -- Eric. ___ Python-Dev mailin

Re: [Python-Dev] Proposed schedule for Python 3.4

On 03.10.12 20:10, MRAB wrote: I downloaded the alphas to test the support for PEP 393 I'd added to the regex module. Hardly alpha would be useful to you if it released before PEP 393 implementation. ___ Python-Dev mailing list Python-Dev@python.o

Re: [Python-Dev] Split unicodeobject.c into subfiles?

On Thu, 04 Oct 2012 23:46:57 +0200 mar...@v.loewis.de wrote: > > Zitat von Victor Stinner : > > > I only see one argument against such refactoring: it will be harder to > > backport/forwardport bugfixes. > > I'm opposed for a different reason: I think it will be *harder* to maintain. > The amoun

Re: [Python-Dev] Proposed schedule for Python 3.4

mar...@v.loewis.de writes: > We once had nightly builds of the Windows installers. It required a > dedicated buildbot operator, since the process tended to break. For what it's worth, I'd be willing to try to re-institute the daily Windows installer builds if they'd see usage, but I suspect I'll

Re: [Python-Dev] Proposed schedule for Python 3.4

On 10/3/2012 12:02 PM, Larry Hastings wrote: What it really comes down to: I'm a first-time RM, and I lack the courage/wisdom to overrule what appears to be a reasonable status quo. I feel I don't have to defend the decision to maintain the status quo; I feel instead you have to make a case for

Re: [Python-Dev] Bootstrap issue: "select" is compiled "too late"

On Thu, 4 Oct 2012 22:08:40 +0530 Nick Coghlan wrote: > On Thu, Oct 4, 2012 at 7:54 PM, Brett Cannon wrote: > > This used to be a no-no, though, because if someone called that function in > > a thread during an import it would deadlock. Now Antoine reworked the locks > > so I don't know if this i

Re: [Python-Dev] Proposed schedule for Python 3.4

In article <20121003203328.horde.za5_tqgzi1vqbit43mhb...@webmail.df.eu>, mar...@v.loewis.de wrote: > I wouldn't mind having alpha 1 in April 2013, and alpha 2 in October 2013. > I share Larry's skepticism, and actually fear that it may confuse users > (which find that they test something complete

Re: [Python-Dev] Split unicodeobject.c into subfiles?

Chris Jerdonek writes: > You can create multiple files this way. I just verified it. But the > problem happens with merging. You will create merge conflicts in the > deleted portions of every split file on every merge. There may be a > way to avoid this that I don't know about though (i.e.

Re: [Python-Dev] Split unicodeobject.c into subfiles?

2012/10/4 Antoine Pitrou : > On Thu, 04 Oct 2012 23:46:57 +0200 > mar...@v.loewis.de wrote: >> >> Zitat von Victor Stinner : >> >> > I only see one argument against such refactoring: it will be harder to >> > backport/forwardport bugfixes. >> >> I'm opposed for a different reason: I think it will b

Re: [Python-Dev] Should vars() return modifiable dict?

On 10/3/2012 11:34 AM, Steven D'Aprano wrote: On 03/10/12 18:54, Serhiy Storchaka wrote: Should behavior of vars() be corrected for locals? I believe you are misinterpreting what you are seeing. In this case, vars() simply returns locals(), which is an ordinary dict, but changes to that dict

Re: [Python-Dev] what´s new 3.3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30/09/12 12:55, Kristján Valur Jónsson wrote: > Hi there. > > Not having kept up, I realized I failed to contribute to the What's > new thingie. > > Here's stuff I remember working on and putting in: > > 1. pickling support for built in iterators

Re: [Python-Dev] Proposed schedule for Python 3.4

Executive summary: Larry admits that doing an early alpha is a plausible experiment, he just has reasons not to do it himself. OTOH, Nick has a reason for wanting to do it in *this* release cycle. It's Larry's call; we should restrict ourselves to giving him the information he requests to make a

[Python-Dev] Thread/garbage collection race in Popen

Hi all, I have a Python program where I have many threads each calling Popen, and I was hitting some trouble. I've been seeing this on 3.2.3, however I believe the same issue is still potentially a problem on head. The error manifests itself when a call to os.close(errpipe_read) fails with EBADF