Mailman 3 October 2007 - Python-Dev

Re: [Python-Dev] Windows builds for backported SSL module, please?
by Paul Moore 05 Oct '07

05 Oct '07

On 05/10/2007, Bill Janssen <janssen(a)parc.com> wrote: > For some reason, it was set to be 'hidden'. > > Try > > http://pypi.python.org/pypi/ssl/1.5 > > Bill Tiny typo in setup.py (see below). I've fixed it in my copy - it won't affect the Windows builds, unless you want to release a new version, when the version number will change :-) Paul. --- setup.py.orig 2007-10-05 00:19:04.000000000 +0100 +++ setup.py 2007-10-05 19:01:27.359375000 +0100 @@ -160,7 +160,7 @@ ssl_incs = [os.environ.get("C_INCLUDE_DIR") or os.path.join(gnuwin32_dir, "include")] ssl_libs = [os.environ.get("C_LIB_DIR") or os.path.join(gnuwin32_dir, "lib")] libs = ['ssl', 'crypto', 'wsock32'] - if static: + if not dynamic: libs = libs + ['gdi32', 'gw32c', 'ole32', 'uuid'] link_args = ['-static'] else:

2 2

Summary of Tracker Issues
by Tracker 05 Oct '07

05 Oct '07

ACTIVITY SUMMARY (09/28/07 - 10/05/07) Tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. 1291 open (+18) / 11432 closed ( +3) / 12723 total (+21) Open issues with patches: 413 Average duration of open issues: 680 days. Median duration of open issues: 705 days. Open Issues Breakdown open 1286 (+18) pending 5 ( +0) Issues Created Or Reopened (21) _______________________________ popen3 website documentation inconsistency 09/30/07 http://bugs.python.org/issue1220 created jbronn email.Utils.parseaddr("a(WRONG)@b") 09/30/07 http://bugs.python.org/issue1221 created helmut locale.format bug if thousand separator is space (french separat 09/30/07 http://bugs.python.org/issue1222 created edlm10 httplib does not handle ssl end of file properly 10/01/07 http://bugs.python.org/issue1223 created Richie patch SimpleHTTPServer doesn't understand // at beginning of path anym 10/01/07 http://bugs.python.org/issue1224 created philfr IDLE - Fix: pressing Ctrl+C while printing exception -> stuck 10/01/07 http://bugs.python.org/issue1225 created taleinat lib/sched.py superfluous code for removal 10/01/07 http://bugs.python.org/issue1226 created lorph csv docs say 'excel_tab'; code says 'excel-tab' 10/02/07 CLOSED http://bugs.python.org/issue1227 created dcelzinga 3.0 tutorial/datastructures.rst patch 10/02/07 http://bugs.python.org/issue1228 created scav patch 3.0 library/stdtypes.rst 10/02/07 http://bugs.python.org/issue1229 created scav Tix HList class missing method implementation for info_bbox 10/03/07 http://bugs.python.org/issue1230 created ron.longo PEPs 344 and 3134 contain incorrect hyperlinks. 10/03/07 CLOSED http://bugs.python.org/issue1231 created draghuram %f prints the wrong 6 decimal places 10/03/07 CLOSED http://bugs.python.org/issue1232 created kmckiou bsddb.dbshelve.DbShelf.append doesn't work 10/03/07 http://bugs.python.org/issue1233 created polaar semaphore errors on AIX 5.2 10/04/07 http://bugs.python.org/issue1234 created sable CGIHTTPRequestHandler.run_cgi() does not run on Windows if sys.e 10/04/07 http://bugs.python.org/issue1235 created schu subprocess is not thread-safe 10/04/07 http://bugs.python.org/issue1236 created kjd(a)duda.org type_new doesn't allocate space for sentinal slot 10/05/07 http://bugs.python.org/issue1237 created rhamphoryncus dictobject and dictentry not used consistently in dictobject.c 10/05/07 http://bugs.python.org/issue1238 created anthon openpty does not give bidirectional pipe 10/05/07 http://bugs.python.org/issue1239 created mudyc str.split bug when using sep = None and maxsplit 10/05/07 http://bugs.python.org/issue1240 created QuantumTim Issues Now Closed (10) ______________________ Backport ABC to 2.6 40 days http://bugs.python.org/issue1026 baranguren patch bogus attributes reported in asyncore doc 37 days http://bugs.python.org/issue1053 fdrake csv docs say 'excel_tab'; code says 'excel-tab' 1 days http://bugs.python.org/issue1227 dcelzinga PEPs 344 and 3134 contain incorrect hyperlinks. 1 days http://bugs.python.org/issue1231 georg.brandl %f prints the wrong 6 decimal places 0 days http://bugs.python.org/issue1232 kmckiou SimpleHTTPServer doesn't understand query arguments 639 days http://bugs.python.org/issue1394565 philfr Move firewall warning to "about" menu 435 days http://bugs.python.org/issue1529018 georg.brandl patch Python SEGFAULT on tuple.__repr__ and str() 192 days http://bugs.python.org/issue1686386 brett.cannon patch textView code cleanup 144 days http://bugs.python.org/issue1718043 kbk patch IDLE - configDialog layout cleanup 123 days http://bugs.python.org/issue1730217 kbk patch

1 0

Re: [Python-Dev] Windows builds for backported SSL module, please?
by Paul Moore 05 Oct '07

05 Oct '07

On 05/10/2007, Bill Janssen <janssen(a)parc.com> wrote: > I found a bug -- setup.py wasn't detecting the difference between > 2.5.0 and 2.5.1 properly. I've updated the release to 1.5. > > > http://pypi.python.org/pypi?name=ssl&version=1.5& I'll do Windows binaries for you. The URL you gave is broken, though, and I can't find the package on PyPI... :-( Paul.

2 1

Removing hotshot profiler?
by Fred Drake 05 Oct '07

05 Oct '07

I vaguely recall some discussion about removing hotshot in favor of a better maintained profiler that has better thread support as well. Does anyone remember the decision? I don't see anything about it in PEP 4 or the Python 3000 PEPs I checked. -Fred -- Fred Drake <fdrake at acm.org>

3 2

Windows builds for backported SSL module, please?
by Bill Janssen 04 Oct '07

04 Oct '07

I've uploaded the source version of the backported SSL module to the Cheeseshop. It would be nice to include Windows builds for it for Python 2.3, 2.4, and 2.5, as well, and I'd be happy to upload them if someone could create them. http://pypi.python.org/pypi?name=ssl&version=1.4&:action=display Now, for the Python 3K version... Bill

1 1

Returning exception stack trace in SimpleXMLRPCServer response
by Raghuram Devarakonda 04 Oct '07

04 Oct '07

Hi, When an exception occurs in a function, SimpleXMLRPCServer currently sends exception type and value back to the client (in <faultString>) . So the client sees some thing like: "'<type \'exceptions.ValueError\'>:invalid literal for int() with base 10" This string is constructed in _marshaled_dispatch() as ""%s:%s" % (exc_type, exc_value)". How about adding the stack traceback to this string? I found it very useful to have the server side traceback in case of failures. I will come up with a patch if there is any interest. Some thing similar has been done in case of internal server errors (in r57158). Thanks, Raghu

1 0

Backporting Decimal
by Facundo Batista 02 Oct '07

02 Oct '07

People: I don't decide myself what to do in this case. The Decimal module appeared in 2.4, and received just slight modifications for 2.5. Since it appeared, a "just download and use it" version was available for Python 2.3 users. But for 2.6, it was fully renewed. Not only was updated to the last spec from Cawlishaw, but also a lot of (very slightly, arithmetic corner cases) bugs were fixed. Also, it received a lot of code simplifications and speedups. All this is, in most part, because Mark Dickinson was involved here, and he did (and is doing) a great work. When 2.6 is out, I'll update that downloadable for Py2.3. But what to do with Py2.5? Decimal is a pretty stand alone module, and I'm absolutely sure that just backporting the whole module and its testcases will fix a lot of problems, and Py2.5 users will have new functionality, but is this ok? (of course, I can not be 100% sure that any bugs were introduced in these modifications). Recommendations? Thank you very much! -- . Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/

4 6

Re: [Python-Dev] [python] Re: New lines, carriage returns, and Windows
by Nick Maclaren 02 Oct '07

02 Oct '07

"Guido van Rossum" <guido(a)python.org> wrote: > > Does anyone else have the feeling that discussions with Mr. MacLaren > don't usually bear any fruit? Yes. I do. My ability to predict the (technical) future is good; my ability to persuade people of it is almost non-existent. However, when an almost identical thread to this one occurs in a decade's time, I shall be safely retired. And, assuming no changes to the basic models, when one occurs in twenty years' time, I shall be forgotten. Such is life. Regards, Nick Maclaren, University of Cambridge Computing Service, New Museums Site, Pembroke Street, Cambridge CB2 3QH, England. Email: nmm1(a)cam.ac.uk Tel.: +44 1223 334761 Fax: +44 1223 334679

1 0

Re: [Python-Dev] [python] Re: New lines, carriage returns, and Windows
by Nick Maclaren 02 Oct '07

02 Oct '07

Greg Ewing <greg.ewing(a)canterbury.ac.nz> wrote: > > > I don't know PRECISELY what you mean by "universal newlines mode" > > I mean precisely what Python means by the term: any of > "\r", "\n" or "\r\n" represent a newline, and no distinction > is made between them. Excellent. While this over-simplifies the issue, let's stick to the over-simplified form, as we may be able to get somewhere. The question is independent of what the outside system believes a text file should look like, and is solely what Python believes a sequence of characters should mean. For example, does 'A\r\nB' mean that B is separated from A by one newline or two? The point is that, once we know that, we can design a translator to and from Python's conventions to any reasonable system (and, as I say, I have done it many times). But, if Python's own interpretation is ambiguous, it is a sure recipe for different translators being incompatible, even on the same system. Which is what has happened here. So, damn the outside system, EXACTLY what does Python mean by such characters, and EXACTLY what uses of them are discouraged as having unspecified meanings? If we could get an answer to that precisely enough to write a parse tree with all terminals explicit, this problem would go away. And that is all that I say can or should be done. The details of how to write the translators to other file systems are then a separate matter. Regards, Nick Maclaren, University of Cambridge Computing Service, New Museums Site, Pembroke Street, Cambridge CB2 3QH, England. Email: nmm1(a)cam.ac.uk Tel.: +44 1223 334761 Fax: +44 1223 334679

5 4

Re: [Python-Dev] New lines, carriage returns, and Windows
by Nick Maclaren 02 Oct '07

02 Oct '07

"Paul Moore" <p.f.moore(a)gmail.com> wrote: > > OK, so far so good - although I'm not *quite* sure there's a > self-consistent definition of "code that only uses \n". I'll assume > you mean code that has a concept of lines, that lines never contain > anything other than text (specifically, neither \r or \n can appear in > a line, I'll punt on whether other weird stuff like form feed are > legal), and that whenever your code needs to write data to a file, it > writes lines with \n alone between them. I won't. There are a few of us still left who know how this started, and here is a simplified description. Unix was a computer scientist's workbench, and made no attempt to be general. In particular, its text datastream model was appropriate for the imnportant devices of the day - teletypes and similar. So far, so good. But what was forgotten later is that the model does NOT extend to other systems and, in particular, made no sense on the record-oriented models generally used by mainframes (see Fortran for an example). When C was standardised, this was fudged. I tried to get it improved, but it is one of the many things I failed to do. The handling of ALL of the control characters in text I/O is non-portable (even \t, despite what the satndard says), and you have to follow the system's constraints if things are to work. Unfortunately, the kludging that the compiler does to map C to the operating system confuses things still further - though it is essential. Now, BCPL was an ancestor of C, but always was a more portable language (i.e. it didn't start with a specific operating system in mind), and used/uses a rather better model. In this, line separators are atomic - e.g. '\f' is newline-with-form-feed and '\r' is "newline-with-overprinting". Now, THAT model is more generic. Not fully generic, of course, but it would cater for all of Unix, CPM and its derivatives (yes, Microsoft), MacOS and most mainframes (with some reservations). So, until and unless Python chooses to define its own I/O model, these problems will continue to arise. Whether this one is a simple bug or an avoidable feature, I can't say without looking harder, but bugs are often caused by attempting to implement impossible or confusing specifications. Regards, Nick Maclaren, University of Cambridge Computing Service, New Museums Site, Pembroke Street, Cambridge CB2 3QH, England. Email: nmm1(a)cam.ac.uk Tel.: +44 1223 334761 Fax: +44 1223 334679

10 21