Re: [Python-Dev] [Python-checkins] cpython (3.2): Fixes issue #8052: The posix subprocess module's close_fds behavior was

2012-01-22 Thread Gregory P. Smith
On Sat, Jan 21, 2012 at 4:21 PM, Benjamin Peterson wrote: > 2012/1/21 gregory.p.smith : > ... >> +/* Convert ASCII to a positive int, no libc call. no overflow. -1 on error. >> */ > > Is no libc call important? Yes. strtol() is not on the async signal safe C library function list. > >> +static

Re: [Python-Dev] Counting collisions for the win

2012-01-22 Thread Victor Stinner
> This seed is chosen randomly at runtime, but cannot > change once chosen. The hash is used to compare objects: if hash(obj1) != hash(obj2), objects are considered different. So two strings must have the same hash if their value is the same. > Salt could also be an appropriate term here, but sin

Re: [Python-Dev] python build failed on mac

2012-01-22 Thread Michael Foord
On 21 Jan 2012, at 20:24, Vijay Majagaonkar wrote: > > On 2012-01-21, at 1:57 PM, Hynek Schlawack wrote: > >> Am Freitag, 20. Januar 2012 um 23:40 schrieb Vijay Majagaonkar: > I am trying to build python 3 on mac and build failing with following > error can somebody help me with this >

Re: [Python-Dev] python build failed on mac

2012-01-22 Thread Łukasz Langa
Wiadomość napisana przez Michael Foord w dniu 22 sty 2012, o godz. 14:14: > ./configure CC=gcc-4.2 --prefix=/dev/null --with-pydebug Why the phony prefix? -- Best regards, Łukasz Langa Senior Systems Architecture Engineer IT Infrastructure Department Grupa Allegro Sp. z o.o. Pomyśl o śr

Re: [Python-Dev] python build failed on mac

2012-01-22 Thread Michael Foord
On 22 Jan 2012, at 17:43, Łukasz Langa wrote: > Wiadomość napisana przez Michael Foord w dniu 22 sty 2012, o godz. 14:14: > >> ./configure CC=gcc-4.2 --prefix=/dev/null --with-pydebug > > Why the phony prefix? Heh, it's what I've always done - I think copied from other developers. The

Re: [Python-Dev] Counting collisions for the win

2012-01-22 Thread Lennart Regebro
On Sun, Jan 22, 2012 at 11:11, Victor Stinner wrote: >> This seed is chosen randomly at runtime, but cannot >> change once chosen. > > The hash is used to compare objects: if hash(obj1) != hash(obj2), > objects are considered different. So two strings must have the same > hash if their value is th

Re: [Python-Dev] Counting collisions for the win

2012-01-22 Thread Antoine Pitrou
I think this thread is approaching the recursion limit. Be careful not to blow the stack :) Regards Antoine. On Sun, 22 Jan 2012 20:53:41 +0100 Lennart Regebro wrote: > On Sun, Jan 22, 2012 at 11:11, Victor Stinner > wrote: > >> This seed is chosen randomly at runtime, but cannot > >> change

Re: [Python-Dev] Counting collisions for the win

2012-01-22 Thread Paul McMillan
> We may use a different salt per dictionary. If we're willing to re-hash everything on a per-dictionary basis. That doesn't seem reasonable given our existing usage. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listin

Re: [Python-Dev] Counting collisions for the win

2012-01-22 Thread Lennart Regebro
On Mon, Jan 23, 2012 at 06:02, Paul McMillan wrote: >> We may use a different salt per dictionary. > > If we're willing to re-hash everything on a per-dictionary basis. That > doesn't seem reasonable given our existing usage. Well, if we get crazy amounts of collisions, re-hashing with a new salt

Re: [Python-Dev] Counting collisions for the win

2012-01-22 Thread Stephen J. Turnbull
Lennart Regebro writes: > On Mon, Jan 23, 2012 at 06:02, Paul McMillan wrote: > >> We may use a different salt per dictionary. > > > > If we're willing to re-hash everything on a per-dictionary basis. That > > doesn't seem reasonable given our existing usage. > > Well, if we get crazy amou

Re: [Python-Dev] Counting collisions for the win

2012-01-22 Thread Tim Delaney
On 23 January 2012 16:49, Lennart Regebro wrote: > On Mon, Jan 23, 2012 at 06:02, Paul McMillan wrote: > >> We may use a different salt per dictionary. > > > > If we're willing to re-hash everything on a per-dictionary basis. That > > doesn't seem reasonable given our existing usage. > > Well, i