"Michael Hudson" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Anthony Baxter <[EMAIL PROTECTED]> writes: > >> So I'm currently planning for a 2.4.2 sometime around mid September. I >> figure >> we cut a release candidate either on the 7th or 14th, and a final a week >> later. > > Cool. I'm not sure how many outstanding bugs should be fixed before > 2.4.2. Some stuff to do with files with PEP 263 style declarations? > (Walter? I've lost track of these).
This is a serious issue (spurious syntax errors). One bug about files with encoding declarations is www.python.org/sf/1163244 . So far, it seems that source files having a size of f*n+x (for some small indeterminate value of x, and f is a power of 2 like 512 or 1024) occasionally fail to compile with spurious syntax errors. (I once had a file show up the line with the "syntax error", and the reported line was comprised half from the failing line and half from the line above --unfortunately I kept the file for examination in a USB key that some colleague formatted). The syntax errors disappear if the coding declaration is removed or if some blank lines are inserted before the failing line. I think this occurs only on Windows, so it should be something to do with line endings and buffering. At the moment I'm trying to create a minimal file that when imported fails with 2.4.1 . I'll update the case as soon as I have one, but I wanted to draw some attention in python-dev in case it rings a bell. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
