Mailman 3 February 2001 - Python-Dev

urllib2 and urllib
by Moshe Zadka 28 Feb '01

28 Feb '01

(Full disclosure: I've been payed to hack on urllib2) For a long time I've been feeling that urllib is a bit hackish, and not really suited to conveniently script web sites. The classic example is the interface to passwords, whose default behaviour is to stop and ask the user(!). Jeremy had urllib2 out for about a year and a half, and now that I've finally managed to have a look at it, I'm very impressed with the architecture, and I think it's superior to urllib.

1 0

Re: Patch uploads broken
by Andrew Kuchling 28 Feb '01

28 Feb '01

The SourceForge admins couldn't replicate the patch upload problem, and managed to attach a file to the Python bug report in question, yet when I try it, it still fails for me. So, a question for this list: has uploading patches or other files been working for you recently, particularly today? Maybe with more data, we can see a pattern (browser version, SSL/non-SSL, cluefulness of user, ...). If you want to try it, feel free to try attaching a file to bug #404680: https://sourceforge.net/tracker/index.php?func=detail&aid=404680&group_id=5… ) The SF admin request for this problem is at http://sourceforge.net/tracker/?func=detail&atid=100001&aid=404688&group_id…, but it's better if I collect the results and summarize them in a single comment. --amk

6 6

test_symtable failing on Linux
by Skip Montanaro 28 Feb '01

28 Feb '01

test_symtable is failing for me: % ./python ../Lib/test/test_symtable.py Traceback (most recent call last): File "../Lib/test/test_symtable.py", line 7, in ? verify(symbols[0].name == "global") TypeError: unsubscriptable object Just cvs up'd about ten minutes ago. Skip

3 2

one more restriction for from __future__ import ...
by Jeremy Hylton 28 Feb '01

28 Feb '01

> In addition, all future_statments must appear near the top of the > module. The only lines that can appear before a future_statement are: > > + The module docstring (if any). > + Comments. > + Blank lines. > + Other future_statements. I would like to add another restriction: A future_statement must appear on a line by itself. It is not legal to combine a future_statement without any other statement using a semicolon. It would be a bear to implement error handling for cases like this: from __future__ import a; import b; from __future__ import c Jeremy

4 7

to whoever made the termios changes...
by Flying Cougar Burnette 28 Feb '01

28 Feb '01

I've already deleted the check-in mail and forgot who it was! Hopefully you're listening... (Fred, maybe?) I just did a cvs update and am no getting this when compiling on irix65: cc -O -OPT:Olimit=0 -I. -I/usr/u0/tommy/pycvs/python/dist/src/./Include -IInclude/ -I/usr/local/include -c /usr/u0/tommy/pycvs/python/dist/src/Modules/termios.c -o build/temp.irix-6.5-2.1/termios.o cc-1020 cc: ERROR File = /usr/u0/tommy/pycvs/python/dist/src/Modules/termios.c, Line = 320 The identifier "B230400" is undefined. {"B230400", B230400}, ^ cc-1020 cc: ERROR File = /usr/u0/tommy/pycvs/python/dist/src/Modules/termios.c, Line = 321 The identifier "CBAUDEX" is undefined. {"CBAUDEX", CBAUDEX}, ^ cc-1020 cc: ERROR File = /usr/u0/tommy/pycvs/python/dist/src/Modules/termios.c, Line = 399 The identifier "CRTSCTS" is undefined. {"CRTSCTS", CRTSCTS}, ^ cc-1020 cc: ERROR File = /usr/u0/tommy/pycvs/python/dist/src/Modules/termios.c, Line = 432 The identifier "VSWTC" is undefined. {"VSWTC", VSWTC}, ^ 4 errors detected in the compilation of "/usr/u0/tommy/pycvs/python/dist/src/Modules/termios.c". time for an #ifdef?

2 1

More std test breakage
by Tim Peters 28 Feb '01

28 Feb '01

test_inspect.py still failing under -O; probably all platforms. New failure in test___all__.py, *possibly* specific to Windows, but I don't see any "termios.py" anywhere so hard to believe it could be working anywhere else either: C:\Code\python\dist\src\PCbuild>python ../lib/test/test___all__.py Traceback (most recent call last): File "../lib/test/test___all__.py", line 78, in ? check_all("getpass") File "../lib/test/test___all__.py", line 10, in check_all exec "import %s" % modname in names File "<string>", line 1, in ? File "c:\code\python\dist\src\lib\getpass.py", line 106, in ? import termios NameError: Case mismatch for module name termios (filename c:\code\python\dist\src\lib\TERMIOS.py) C:\Code\python\dist\src\PCbuild>

3 3

pydoc for 2.1b1?
by Ka-Ping Yee 27 Feb '01

27 Feb '01

Hi! It's my birthday today, and i think it would be a really awesome present if pydoc.py were to be accepted into the distribution. :) (Not just because it's my birthday, though. I would hope it is worth accepting based on its own merits.) The most recent version of pydoc is just a single file, for the easiest possible setup -- zero installation effort. You only need the "inspect" module to run it. You can find it under the CVS tree at nondist/sandbox/help/pydoc.py or download it from http://www.lfw.org/python/pydoc.py http://www.lfw.org/python/inspect.py Among other things, it now handles a few corner cases better, the formatting is a bit improved, and you can now tell it to write out the documentation to files on disk if that's your fancy (it can still display the documentation interactively in your shell or your web browser). -- ?!ng

5 8

Re: [Python-Dev] one more restriction for from __future__ import ...
by Samuele Pedroni 27 Feb '01

27 Feb '01

Hi. > > In addition, all future_statments must appear near the top of the > > module. The only lines that can appear before a future_statement are: > > > > + The module docstring (if any). > > + Comments. > > + Blank lines. > > + Other future_statements. > > I would like to add another restriction: > > A future_statement must appear on a line by itself. It is not > legal to combine a future_statement without any other statement > using a semicolon. > > It would be a bear to implement error handling for cases like this: > > from __future__ import a; import b; from __future__ import c Will the error be unclear for the user or there's another problem? In jython I get from parser an abstract syntax tree, so it is difficult to distringuish the ; from true newlines ;) regards, Samuele

1 0

New test_inspect fails under -O
by Tim Peters 27 Feb '01

27 Feb '01

I assume this is a x-platform failure. Don't have time to look into it myself right now. C:\Code\python\dist\src\PCbuild>python -O ../lib/test/test_inspect.py Traceback (most recent call last): File "../lib/test/test_inspect.py", line 172, in ? 'trace() row 1') File "../lib/test/test_inspect.py", line 70, in test raise TestFailed, message % args test_support.TestFailed: trace() row 1 C:\Code\python\dist\src\PCbuild>

1 0

Patch uploads broken
by Andrew Kuchling 27 Feb '01

27 Feb '01

Uploading of patches seems to be broken on SourceForge at the moment; even if you fill in the file upload form, its contents seem to just be ignored. Reported to SF as support req #404688: http://sourceforge.net/tracker/?func=detail&aid=404688&group_id=1&atid=2000… --amk

1 0