Re: [Python-Dev] status of development documentation

2005-12-24 Thread Brett Cannon
On 12/24/05, Tim Peters <[EMAIL PROTECTED]> wrote: > [Tim] > >> FWIW, test_builtin and test_pep263 both passed on WinXP in rev 39757. > >> That's the last revision before the AST branch was merged. > >> > >> I can't build rev 39758 on WinXP (VC complains that pythoncore.vcproj > >> can't be loaded

Re: [Python-Dev] status of development documentation

2005-12-24 Thread Tim Peters
[Tim] >> FWIW, test_builtin and test_pep263 both passed on WinXP in rev 39757. >> That's the last revision before the AST branch was merged. >> >> I can't build rev 39758 on WinXP (VC complains that pythoncore.vcproj >> can't be loaded -- looks like it got checked in with unresolved SVN >> conflict

Re: [Python-Dev] status of development documentation

2005-12-24 Thread Brett Cannon
On 12/24/05, Tim Peters <[EMAIL PROTECTED]> wrote: > FWIW, test_builtin and test_pep263 both passed on WinXP in rev 39757. > That's the last revision before the AST branch was merged. > > I can't build rev 39758 on WinXP (VC complains that pythoncore.vcproj > can't be loaded -- looks like it got ch

Re: [Python-Dev] status of development documentation

2005-12-24 Thread Tim Peters
FWIW, test_builtin and test_pep263 both passed on WinXP in rev 39757. That's the last revision before the AST branch was merged. I can't build rev 39758 on WinXP (VC complains that pythoncore.vcproj can't be loaded -- looks like it got checked in with unresolved SVN conflict markers -- which isn'

Re: [Python-Dev] status of development documentation

2005-12-24 Thread Tim Peters
[Neal Norwitz] > This gives me an idea (ie, wild ass guess). r39680 checked in on > 2005-10-06 to speed up unicode charmap decoding. Dunno if it's likely > or not. Gotta run, I'm headed east. Good luck. Nope, it's not calling any decoding functions at all on Windows, let alone optimized ones ;

[Python-Dev] NotImplemented reaching top-level

2005-12-24 Thread Facundo Batista
Folks, There's a bug about number coercion about Decimal (http://www.python.org/sf/1355842). The bug appeared after some changes Raymond and I did a few months ago, solving something else (started to return NotImplemented instead of raising TypeError, to better work with custom objects that imple

Re: [Python-Dev] status of development documentation

2005-12-24 Thread Walter Dörwald
Neal Norwitz wrote: > On 12/24/05, Tim Peters <[EMAIL PROTECTED]> wrote: > > [...] >> >> The code up to the first failure is short: >> >> >> >> bom = '\xef\xbb\xbf' >> >> compile(bom + 'print 1\n', '', 'exec') > >> That sets `a` to point at the start of the string, `b` to point at

Re: [Python-Dev] status of development documentation

2005-12-24 Thread Neal Norwitz
On 12/24/05, Tim Peters <[EMAIL PROTECTED]> wrote: > You're asking a Windows guy about make: bad career move ;-) :-) > -uall is helpful in finding bugs. One thing in particular here is > that test_compiler runs only a tiny subset of its full test unless an > appropriate -u flag is given. Not

Re: [Python-Dev] status of development documentation

2005-12-24 Thread Tim Peters
[Samuele Pedroni] > PEP263: > > """ > To aid with platforms such as Windows, which add Unicode BOM marks > to the beginning of Unicode files, the UTF-8 signature > '\xef\xbb\xbf' will be interpreted as 'utf-8' encoding as well > (even if no magic encoding comment is given). > ""

Re: [Python-Dev] documentation comments

2005-12-24 Thread Facundo Batista
2005/12/22, Fred L. Drake, Jr. <[EMAIL PROTECTED]>: > In general, my worry is less with dealing with spam than with ensuring > integration of content enhancements before release candidates go out. Well, I think that the most important part of annotable documentation is just cuantitative feedback,

Re: [Python-Dev] status of development documentation

2005-12-24 Thread Samuele Pedroni
Tim Peters wrote: > [Neal] > >>Hmmm, I thought others were running the tests on Windows too. There >>was one report on Nov 22 about running Purify on Windows 2k (subject: >>ast status, memory leaks, etc). He had problems with a stack overflow >>in test_compile. He was going to disable the test

Re: [Python-Dev] status of development documentation

2005-12-24 Thread Tim Peters
[Neal] > Hmmm, I thought others were running the tests on Windows too. There > was one report on Nov 22 about running Purify on Windows 2k (subject: > ast status, memory leaks, etc). He had problems with a stack overflow > in test_compile. He was going to disable the test and re-run. I > never

Re: [Python-Dev] status of development documentation

2005-12-24 Thread Steve Holden
[EMAIL PROTECTED] wrote: > Steve> Alternatively, is there any mileage in trying to either get > Steve> Sourceforge to provide Windows machines in the compile farm, or > Steve> get Microsoft to provide more software fee to Windows testers? > > How about seeing if Microsoft has or will c

Re: [Python-Dev] status of development documentation

2005-12-24 Thread skip
Steve> Alternatively, is there any mileage in trying to either get Steve> Sourceforge to provide Windows machines in the compile farm, or Steve> get Microsoft to provide more software fee to Windows testers? How about seeing if Microsoft has or will create a compile farm? Skip __

Re: [Python-Dev] status of development documentation

2005-12-24 Thread skip
Neal> I guess you might have to binary search by date to try and find Neal> the problem. Probably needs to be a binary search by revision. I believe Martin indicated a side effect of the conversion to subversion was that date-based updates don't work. Skip __

Re: [Python-Dev] status of development documentation

2005-12-24 Thread Steve Holden
Steve Holden wrote: [...] > Alternatively, is there any mileage in trying to either get Sourceforge > to provide Windows machines in the compile farm, or get Microsoft to > provide more software fee to Windows testers? ^fee^free^ -- Steve Holden +44 150 684 7255 +1 800 494 3119 Holden Web

Re: [Python-Dev] status of development documentation

2005-12-24 Thread Steve Holden
Neal Norwitz wrote: > On 12/23/05, Tim Peters <[EMAIL PROTECTED]> wrote: > >>>http://docs.python.org/dev/results/ >> >>Wow! You get no test failures! I guess nobody tests on Windows >>anymore. I've been getting test failures for months, and just > > > Hmmm, I thought others were running t