[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7

Brett Cannon added the comment: Didn't work when I turned on --enable-framework, but I have no clue how the framework build works so I am of no help with that. -- ___ Python tracker

[issue6185] 2to3 misses buffer slicing

Joe Amenta added the comment: Patch that will fix the problem (and make the test pass) -- Added file: http://bugs.python.org/file14165/bufferfix.patch ___ Python tracker ___

[issue6185] 2to3 misses buffer slicing

New submission from Joe Amenta : Found this bug while writing the backwards version of this fix for 3to2... there is no test for it, so it went undetected. The PATTERN does not match a buffer() invocation if there is a token after the rparen, i.e. slicing. -- components: 2to3 (2.x to 3.

[issue6183] test_time fails on VC6

Hirokazu Yamamoto added the comment: Thanks, committed in r73162. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue6183] test_time fails on VC6

Martin v. Löwis added the comment: > Can I apply attached patch? Thank you. Looks fine to me, go ahead. -- nosy: +loewis ___ Python tracker ___ _

[issue6184] py3k build gets spurious errors from libinstall target compile of lib2to3 files

Ned Deily added the comment: er, spurious "|"'s -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue6184] py3k build gets spurious errors from libinstall target compile of lib2to3 files

Ned Deily added the comment: r73160 does make the spurious errors go away - along with the compiles of all the other modules! Suggest removing the spurious "!"'s: 926c926 < -x 'bad_coding|badsyntax|site- packages|py2_test_grammar|crlf|different_encoding|' \ --- > -

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7

Evan Behar added the comment: It works fine for my framework build on 10.4.11 -- ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue6179] Documentation of for statement in Reference says that range() returns a list

Benjamin Peterson added the comment: Fixed in r73161. -- nosy: +benjamin.peterson resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue6184] py3k build gets spurious errors from libinstall target compile of lib2to3 files

Benjamin Peterson added the comment: Thanks! Fixed in r73160. -- nosy: +benjamin.peterson resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue6184] py3k build gets spurious errors from libinstall target compile of lib2to3 files

New submission from Ned Deily : [...] Compiling /tmp/image/Library/Frameworks/Python.framework/Versions/3.1/lib/python3. 1/lib2to3/tests/__init__.py ... Listing /tmp/image/Library/Frameworks/Python.framework/Versions/3.1/lib/python3. 1/lib2to3/tests/data ... Compiling /tmp/image/Library/Framew

[issue6183] test_time fails on VC6

New submission from Hirokazu Yamamoto : test_time fails on VC6 with following message. == FAIL: test_strptime (__main__.TimeTestCase) -- Traceback (most recent

[issue6182] Remove ipaddr library from py3k before 3.1rc2

New submission from Gregory P. Smith : Do not use this bug for discussion of the topic. Use the python-dev mailing list. This bug is here to track its removal (or not) of the ipaddr library pending the outcome of the mailing list discussion. Resolving this is a release blocker either way.

[issue6170] Mac 'make frameworkinstall' error: [...]/Python.framework/Versions/3.1/bin/2to3: Too many levels of symbolic links

Ned Deily added the comment: That seems to work. However, while testing that, I found another, minor problem in that same area. In Makefile.pre.in bininstall target just before the lines you cite, there is also this added in r71935: -rm -f $(DESTDIR)$(BINDIR)/python3-config (cd $(DESTDIR)$(

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7

Benjamin Peterson added the comment: Does that fix framework builds, too? -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7

Brett Cannon added the comment: I meant locale_fix2.patch causes the infinite output. Regardless, I now have my own patch that solves the problem. I simply make sure that if the check for intl passes it also added "-lintl" to $LIBS. You will need to run autoconf/autoheader yourself as when I ra

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7

Benjamin Peterson added the comment: What about the third? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7

Brett Cannon added the comment: @Evan -- You need to edit configure.in and use autoconf to regenerate configure. @Benjamin -- your second patch leads to an infinite recursion or something with 'y\n' being printed out constantly. -- ___ Python tracke

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7

Changes by Benjamin Peterson : Added file: http://bugs.python.org/file14161/locale_fix2.patch ___ Python tracker ___ ___ Python-bugs-list maili

[issue1943] improved allocation of PyUnicode objects

Guido van Rossum added the comment: That's unfortunate; it would clearly have been easier to change this in 3.1. That said, I'm not sure anyone *should* be subclassing PyUnicode. Maybe Marc-Andre can explain why he is doing this (or point to the message in this thread where he explained this b

[issue6178] Core error in Py_EvalFrameEx 2.6.2

Antoine Pitrou added the comment: > And no, there is still segfaults without optimizations, I've tried at > -O2 -O and -O0 ( -O0 being no optimization). Then you can try rebuilding Python after "./configure --with-pydebug". It will add some runtime checks, perhaps it will find the cause of the

[issue1943] improved allocation of PyUnicode objects

Changes by Raymond Hettinger : -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman

[issue1943] improved allocation of PyUnicode objects

Raymond Hettinger added the comment: Correction: It is a proposal for 3.2 that changes the struct used in 3.0 and 3.1. -- ___ Python tracker ___

[issue1943] improved allocation of PyUnicode objects

Raymond Hettinger added the comment: It's not in 3.1. It is a proposal for 3.2 that changes the struct from what it is in 3.0 and 3.o. -- ___ Python tracker ___

[issue1943] improved allocation of PyUnicode objects

Guido van Rossum added the comment: If this is not yet in 3.1, it's clearly too late to add it (now that RC1 was already released). If was in already (hard to tell from the long bug), I think it should be kept in (removing it would destabilize more than keeping it). -- ___

[issue1943] improved allocation of PyUnicode objects

Raymond Hettinger added the comment: Mark, I'm inclined to agree that this would be a destabilizing change. Guido, do you care to pronounce on whether it is okay to change the struct? -- assignee: -> gvanrossum nosy: +gvanrossum, rhettinger ___ Pyt

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7

Evan Behar added the comment: I applied Benjamin's new patch to the original files, but I receive the same error, and the LIBS in the Makefile still only has -ldl and not -lintl. -- ___ Python tracker _

[issue6136] Make logging configuration files easier to use

Vinay Sajip added the comment: a) Loggers don't have a one-to-one correspondence to files that are opened, so I don't quite understand your point. Perhaps you are conflating loggers with handlers. The common way of using logging is to have a small number of file-based handlers and perhaps a sock

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7

Evan Behar added the comment: I think I've found the problem. In configure: 13830 if test "${ac_cv_lib_intl_textdomain+set}" = set; then 13831 echo $ECHO_N "(cached) $ECHO_C" >&6 13832 else 13833 ac_check_lib_save_LIBS=$LIBS 13834 LIBS="-lintl $LIBS" but then 13883 rm -f co

[issue4806] Function calls taking a generator as star argument can mask TypeErrors in the generator

Kenneth Arnold added the comment: I can confirm that (a) this exact behavior is happening and (b) it quite confused me (most of the time it works!). What would be a "good" TypeError? I'd vote for generators to be explicitly supported even if it required a special case. Thanks! -- nosy:

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7

Benjamin Peterson added the comment: Here's another patch. -- Added file: http://bugs.python.org/file14159/locale_fix.patch ___ Python tracker ___ ___

[issue1943] improved allocation of PyUnicode objects

Marc-Andre Lemburg added the comment: Antoine Pitrou wrote: > Antoine Pitrou added the comment: > >> You cannot simply recompile your code and have it working. > > Who is "you"? > People doing mundane things with PyUnicodeObjects certainly can, > assuming they use the macros for any member ac

[issue1943] improved allocation of PyUnicode objects

Marc-Andre Lemburg added the comment: Here's an example implementation of a Unicode sub-type that allows referencing other Unicode objects: http://downloads.egenix.com/python/unicoderef-0.0.1.tar.gz As you can see, it's pretty straight-forward to write and I want to keep it that way.

[issue6181] Tkinter.Listbox several minor issues

New submission from Guilherme Polo : Hi there, I've found several minor issues in Tkinter.Listbox which are all fixed by the attached patch. I'm considering the bbox method should be clear in relation to the amount of accepted arguments, which is always one. So I dropped the *args usage there.

[issue6180] Tkinter.Entry: fix for xview and some doc clarifications

New submission from Guilherme Polo : The xview method in Tkinter.Entry doesn't indicate that index may be None, which is used to query the Entry xview. I also considered that the docstrings in the selection_range and selection_present methods needed some clarifications, so the attached patch als

[issue6154] Python 3.1 rc1 will not build on OS X 10.5.7

Changes by Brett Cannon : -- stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue6179] Documentation of for statement in Reference says that range() returns a list

New submission from Mitchell Model : The documentation of the for statement in Section 7 of the Python 3 Reference states "range(3) returns the list [0, 1, 2]". Since range() no longer returns a list, shouldn't this statement be made more precise? (since this is the reference it should be technic

[issue6178] Core error in Py_EvalFrameEx 2.6.2

Changes by Marshall Roach : -- nosy: +mroach ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue6136] Make logging configuration files easier to use

Geoffrey Bache added the comment: a) What is the point of opening files that will never be written to and sockets that will never be used? A large application might have a great many loggers for debugging which are off by default, and this means you have to either put up with lots of empty fil

[issue2919] Merge profile/cProfile in 3.0

Jean Brouwers added the comment: Fixed a couple of typos in the README and _profile_hires.c files of the attached profile_module2.tgz tar ball. -- Added file: http://bugs.python.org/file14156/profile_module2.tgz ___ Python tracker

[issue2919] Merge profile/cProfile in 3.0

Changes by Jean Brouwers : Removed file: http://bugs.python.org/file14131/profile_module.tgz ___ Python tracker ___ ___ Python-bugs-list mailin

[issue1207] Load tests from path (patch included)

Michael Foord added the comment: Similar functionality is now in TestLoader.discover. -- resolution: -> rejected status: open -> closed ___ Python tracker ___ __

[issue6177] unittest.main testRunner default argument changed from None

Michael Foord added the comment: Committed to trunk in revision 73151 and revision 73152. -- status: open -> closed ___ Python tracker ___ ___

[issue6177] unittest.main testRunner default argument changed from None

Barry A. Warsaw added the comment: Feel free to apply this to 2.6. -- nosy: +barry resolution: -> accepted ___ Python tracker ___ ___

[issue1244929] hide tests from TestProgram

Michael Foord added the comment: A module can now define load_tests (used by loadTestsFromModule) and exclude certain classes itself. -- resolution: -> wont fix status: open -> closed ___ Python tracker ___

[issue6177] unittest.main testRunner default argument changed from None

Michael Foord added the comment: Patch attached. -- keywords: +patch Added file: http://bugs.python.org/file14155/fix_unittest_main.patch ___ Python tracker ___ _

[issue6126] Python 3 pdb: shows internal code, breakpoints don't work

Eric Promislow added the comment: Similar problem with 3.1rc1: C:\...>c:\Python31rc1\python.exe -m pdb hello01.py --Return-- > c:\python31rc1\lib\encodings\cp437.py(19)encode()->b'Hello' -> return codecs.charmap_encode(input,self.errors,encoding_map)[0] (Pdb) b 2 *** Blank or comment (Pdb) b h

[issue6178] Core error in Py_EvalFrameEx 2.6.2

Tim Savannah added the comment: All site-packages were compiled against python 2.6.1, and python was upgraded later to 2.6.2 (but upon running a make install with python 2.6.2, it seemed to recompile site-packages on a byte-code level). And no, there is still segfaults without optimizations, I'

[issue6156] Error compiling valid regex

Changes by Ezio Melotti : -- nosy: +ezio.melotti versions: +Python 3.0 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue6178] Core error in Py_EvalFrameEx 2.6.2

Antoine Pitrou added the comment: If the third-party packages include some C extensions, have they been recompiled with the new Python build? Also, does the segfault disappear if you disable optimizations? Have you tried with another compiler version? (I'm asking all this because to my knowled

[issue1943] improved allocation of PyUnicode objects

Antoine Pitrou added the comment: > You cannot simply recompile your code and have it working. Who is "you"? People doing mundane things with PyUnicodeObjects certainly can, assuming they use the macros for any member access. > Please note that all type objects documented in the header files >

[issue3959] Add Google's ipaddr.py to the stdlib

Changes by Alexander Belopolsky : -- nosy: +belopolsky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue3959] Add Google's ipaddr.py to the stdlib

Gregory P. Smith added the comment: This issue is closed. Please take discussion up on a mailing list. -- ___ Python tracker ___ ___

[issue1943] improved allocation of PyUnicode objects

Marc-Andre Lemburg added the comment: Antoine Pitrou wrote: > Antoine Pitrou added the comment: > >> The patch breaks C API + binary compatibility for an essential Python >> type - that's not something you can easily undo. > > I don't see how it breaks C API compatibility. No officially docum

[issue6178] Core error in Py_EvalFrameEx 2.6.2

Tim Savannah added the comment: Yes I compiled python myself, using ./configure --prefix=/usr/local/python2.6/ --with-pth --enable-shared It is a 64-bit compile. I've done this with both standard config and a config that I modded which produces optimizations options as -ggdb3 -O0. Both contain

[issue6178] Core error in Py_EvalFrameEx 2.6.2

Antoine Pitrou added the comment: Have you compiled Python yourself? Are you using any third-party C extensions? -- nosy: +pitrou ___ Python tracker ___ _

[issue6178] Core error in Py_EvalFrameEx 2.6.2

New submission from Tim Savannah : I'm getting many segmentation faults (about 1 per half hour) from within the core of python 2.6.2 on 64-bit machines. (examples from dmesg: pythonLaunch.py[13307]: segfault at 0058 rip 2b845cfb3550 rsp 41809930 error 4 pythonLaunch.py[27

[issue6177] unittest.main testRunner default argument changed from None

Changes by Tarek Ziadé : -- nosy: +tarek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/

[issue6177] unittest.main testRunner default argument changed from None

New submission from Michael Foord : In Python 2.6 the testRunner keyword argument to unittest.main (TestProgram) changed from None to TextTestRunner. This breaks test suites (like the setuptools tests) which pass in None when not wanting to override the default. This is easy to fix without brea

[issue1943] improved allocation of PyUnicode objects

Changes by Eric Smith : -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue1943] improved allocation of PyUnicode objects

Antoine Pitrou added the comment: > The patch breaks C API + binary compatibility for an essential Python > type - that's not something you can easily undo. I don't see how it breaks C API compatibility. No officially documented function has changed, and the accessor macros still work. Am I mis

[issue1943] improved allocation of PyUnicode objects

Marc-Andre Lemburg added the comment: Antoine Pitrou wrote: > Antoine Pitrou added the comment: > >> There were a number of patches to support sharing of data between >> unicode objects. (By Larry Hastings?) They were rejected because (a) >> they were complicated, and (b) it was possible

[issue1943] improved allocation of PyUnicode objects

Marc-Andre Lemburg added the comment: Jim Jewett wrote: > Jim Jewett added the comment: > > There were a number of patches to support sharing of data between > unicode objects. (By Larry Hastings?) They were rejected because (a) > they were complicated, and (b) it was possible to provoke

[issue6142] Distutils doesn't remove .pyc files

James added the comment: Currently, I have (had) a make file with a clean target that would remove these files. Would you recommend keeping this file and it's associated functionality, or is the idea to be able to integrate this into distutils and be able to do away with makefiles for python pro

[issue3959] Add Google's ipaddr.py to the stdlib

Clay McClure added the comment: On Tue, Jun 2, 2009 at 2:52 AM, pmoody wrote: >> As far as I can >> tell, every developer in that category, outside of Google, that has >> commented on this issue here or in python-dev has advocated a >> different API. > > Is there some sort of conspiracy theory

[issue6117] Fix O(n**2) performance problem in socket._fileobject

Changes by Kristján Valur Jónsson : -- stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue6117] Fix O(n**2) performance problem in socket._fileobject

Kristján Valur Jónsson added the comment: Checked into trunk as r73145 -- assignee: -> georg.brandl components: +Documentation nosy: +georg.brandl resolution: -> accepted ___ Python tracker __

[issue5230] pydoc reports misleading failure if target module raises an ImportError

R. David Murray added the comment: I'm sorry, I mistyped. That is the error message I was expecting (it's derived from the one 'import' gives in that case). If the test were like this: elif exc is ImportError and str(value).endswith(path.split('.')[-1]): then I think the tests would pas

[issue5230] pydoc reports misleading failure if target module raises an ImportError

Lucas Prado Melo added the comment: Take a look at the output: $ python pydoc.py test.pydoc_badimport2 problem in test.pydoc_badimport2 - : No module named i_dont_exist.neither_do_i This is different from what you expected. How do we change this output? (I was talking about this issue in the la

[issue6136] Make logging configuration files easier to use

Vinay Sajip added the comment: Re. point (a): The configuration logic assumes that if you put things in the configuration file, you want them included - that means instantiating handlers, which will generally open their output files (uness the delay parameter is set) and sockets. If you use appe

[issue6170] Mac 'make frameworkinstall' error: [...]/Python.framework/Versions/3.1/bin/2to3: Too many levels of symbolic links

Ronald Oussoren added the comment: This should be fixed in r73142, please test. -- resolution: -> fixed status: open -> pending ___ Python tracker ___ __

[issue6170] Mac 'make frameworkinstall' error: [...]/Python.framework/Versions/3.1/bin/2to3: Too many levels of symbolic links

Ronald Oussoren added the comment: I found the issue. In r72899 antoine.pitrou checked in a change that adds these two lines to the bininstall target in Makefile.pre.in: -rm -f $(DESTDIR)$(LIBPC)/python3.pc (cd $(DESTDIR)$(LIBPC); $(LN) -s python-$(VERSION).pc python3.pc) This exposes

[issue6176] Reference to a wrong version of flock's documentation

New submission from Pascal Chambon : It seems that the "flock" wrapped by the fcntl module is the one descriebd in "flock(2)", not "flock(3)" (just in case this might confuse people...) Quote : """ fcntl.flock(fd, op) Perform the lock operation op on file descriptor fd (file objects providing a

[issue4829] confusing error for file("foo", "w++")

Ulrich Eckhardt added the comment: Good catch, it just took me a while to actually figure out myself where the bug is. Try the following instead: import io io.FileIO('foo.text', 'w++') This will yield "ValueError: Must have exactly one of read/write/append mode" with 2.6 on win32. I haven'

[issue6170] Mac 'make frameworkinstall' error: [...]/Python.framework/Versions/3.1/bin/2to3: Too many levels of symbolic links

Ronald Oussoren added the comment: Manually running "make frameworkinstallframework" (and the other ones) is not supported, those are internal makefile targets that are are used to implement "make install". "make framworkinstall" is supported as an alias for "make install" because the forme

[issue6172] 'make framework...' fails on Mac ([...]/bin/pythonw3.1: No such file or directory)

Ronald Oussoren added the comment: The build was quicker than expected. I also cannot reproduce using r31rc1. Or rather, I can reproduce this using "make frameworkinstallframework", but not using "make install". The latter is the correct way to install the framework, the former is an inter

[issue6170] Mac 'make frameworkinstall' error: [...]/Python.framework/Versions/3.1/bin/2to3: Too many levels of symbolic links

Tarek Ziadé added the comment: Ronald, did you try Sridar precise sequence after Pyhon was built ? make frameworkinstallframework DESTDIR=image make frameworkinstallapps DESTDIR=image make frameworkinstall frameworkinstallextras DESTDIR=image -- __

[issue6170] Mac 'make frameworkinstall' error: [...]/Python.framework/Versions/3.1/bin/2to3: Too many levels of symbolic links

Ronald Oussoren added the comment: Now I'm really confused, I tried to install a second time and this time I do get an error. Time to start hunting down an issue... -- ___ Python tracker ___

[issue6153] email parsing - Rare Failure

Amaury Forgeot d'Arc added the comment: This is a duplicate of issue170. -- nosy: +amaury.forgeotdarc resolution: -> duplicate status: open -> closed superseder: -> email parser incorrectly breaks headers with a CRLF at 8192 ___ Python tracker

[issue6170] Mac 'make frameworkinstall' error: [...]/Python.framework/Versions/3.1/bin/2to3: Too many levels of symbolic links

Ronald Oussoren added the comment: I also cannot reproduce this, using both the py3k branch and the r31rc1 tag. My build procedure: * cd r31rc1 * mkdir build * cd build * ../configure --enable-framework --enable-universalsdk * make * make install DESTDIR=$PWD/image The resulting framework i

[issue6172] 'make framework...' fails on Mac ([...]/bin/pythonw3.1: No such file or directory)

Ronald Oussoren added the comment: I cannot reproduce this with the py3k branch, I'm currently building r31rc1 to check if I can reproduce the issue with that. -- ___ Python tracker ___

[issue6170] Mac 'make frameworkinstall' error: [...]/Python.framework/Versions/3.1/bin/2to3: Too many levels of symbolic links

Tarek Ziadé added the comment: Sorry I can't reproduce it, can you tell me how you run configure precisely ? eg the whole set of commands after a fresh checkout -- ___ Python tracker __

[issue6175] inet_aton documentation kind of lies

New submission from Daniel Svensson : The documentation for inet_aton specifically says that it's used to "Convert an IPv4 address from dotted-quad string format". This however is not really true, it does accept dotted-quad, but not dotted-quad alone, but also these forms from inet(3) man page:

[issue6173] Minor typo in socket.py

Mark Dickinson added the comment: Sorry. Those revision numbers should be: r73138, r73139, r73140, r73141. -- ___ Python tracker ___ ___

[issue6173] Minor typo in socket.py

Mark Dickinson added the comment: Thanks! Fixed in r73138, r71739, r71740, r71741. -- nosy: +marketdickinson resolution: -> fixed stage: -> committed/rejected status: open -> closed type: -> behavior versions: +Python 3.0, Python 3.1 ___ Python t

[issue6172] 'make framework...' fails on Mac ([...]/bin/pythonw3.1: No such file or directory)

Ned Deily added the comment: See also Issue6170. -- nosy: +nad, ronaldoussoren ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue6170] Mac 'make frameworkinstall' error: [...]/Python.framework/Versions/3.1/bin/2to3: Too many levels of symbolic links

Ned Deily added the comment: The URL you provide for the log doesn't seem to be accessible externally so it is difficult to guess exactly what was being done. However, there were changes between 3.1b2 and 3.1rc1 to the top-level Makefile (Makefile.pre.in) and to the Mac/Makefile.in affecting