[issue8365] 'readline' module fails to build on OS X - some recent change broke it

Ned Deily added the comment: Issue6877 (and subsequent fixes in Issue8066) allows the Python readline module to be built and linked with the OS X editline (libedit) library rather than with the GNU readline library (which is not included with OS X). However, the libedit included in versions

[issue8366] OS X universal builds fail on 2.7b1 and py3k with "Don't know machine value for archs"

Shashwat Anand added the comment: I tried to reproduce it on trunk by trying, ./configure --enable-universalsdk --with-universal-archs=32-bit ; make However It did managed to build successfully. The relevant bits during installation: gcc -c -arch ppc -arch i386 -isysroot / -DNDEBUG -g -fwrap

[issue8366] OS X universal builds fail on 2.7b1 and py3k with "Don't know machine value for archs"

Ned Deily added the comment: Fails for me with py3k, trunk, and with the 2.7.b1 tarball on 10.6.3 (Intel) and 10.5.8 (ppc). Your test output looks suspect; with the given configure values, the use of gcc-4.0 should be forced. Perhaps you used an existing build directory but did not do a mak

[issue8241] py2_test_grammar.py contains invalid syntax for 2.6

Martin v. Löwis added the comment: Benjamin, ISTM that the tests in lib2to3/tests/data/py2_test_grammar aren't run at all, as part of regrtest. If so, the entire file could be removed. -- components: +Installation -2to3 (2.x to 3.0 conversion tool)

[issue8366] OS X universal builds fail on 2.7b1 and py3k with "Don't know machine value for archs"

Shashwat Anand added the comment: I reinstalled with : make distclean; ./configure --enable-universalsdk --with-universal-archs=32-bit; make on 10.6.2 (Intel) Which I guess is correct. -- ___ Python tracker __

[issue8365] 'readline' module fails to build on OS X - some recent change broke it

Shashwat Anand added the comment: ./configure MACOSX_DEPLOYMENT_TARGET=10.6 ; make does the trick. However it should be done by default rather than being defined explicitly. Closing the issue. -- ___ Python tracker

[issue8365] 'readline' module fails to build on OS X - some recent change broke it

Changes by Shashwat Anand : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue8093] IDLE processes don't close

Stefan Krah added the comment: For the record: In 2.7-alpha you do not even get to press [Restart Shell], since IDLE is not responding during the calculation. -- nosy: +skrah ___ Python tracker ___

[issue8366] OS X universal builds fail on 2.7b1 and py3k with "Don't know machine value for archs"

Ned Deily added the comment: Chances are you do not have the 10.4u SDK installed; it is not installed by default by the Snow Leopard Xcode mpkg installer. If it is not installed, configure falls back to using / as the sysroot (see configure.in at around line 95). If you are going to build a

[issue8366] OS X universal builds fail on 2.7b1 and py3k with "Don't know machine value for archs"

Shashwat Anand added the comment: The error was finally reproduced with : $make distclean; ./configure --enable-universalsdk=/Developer/SDKs/MacOSX10.6.sdk --with-universal-archs=32-bit MACOSX_DEPLOYMENT_TARGET=10.6; make gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.6.sdk -u

[issue8367] test_winsound: failure on systems without soundcard

New submission from Stefan Krah : Got this test failure on Windows/qemu: == FAIL: test_stopasync (__main__.PlaySoundTest) -- Traceback (most recent call last):

[issue8367] test_winsound: failure on systems without soundcard

Stefan Krah added the comment: Searching for the failure reveals that sporadically this has appeared on the buildbots, so I plan to apply the patch soon if there aren't any protests. -- assignee: -> skrah components: +Tests keywords: +patch priority: -> normal stage: -> patch review

[issue8299] Improve GIL in 2.7

Kristján Valur Jónsson added the comment: I looked at ccbench. It's a great tool. I've added two features to it (see the attached patch) -y option to turn off the "do_yield" option in throughput, and so measure thread scheduling without assistance, and the throughput option now also compute

[issue6860] Inconsistent naming of custom command in setup.py help output

Éric Araujo added the comment: Hello Distutils being frozen, I’m reassigning to Distutils2. Not sure if I should make versions blank, 3.3 or third-party, so leaving it alone. Regards -- components: +Distutils2 -Distutils ___ Python tracker

[issue6650] sre_parse contains a confusing generic error message

Éric Araujo added the comment: In the absence of better propositions, the message in the patch seems more helpful to me than the previous, especially because “lookbehind” is a search term that matches <0.1 wink> on docs.python.org. So I’d apply this patch. -- nosy: +merwok __

[issue6555] distutils config file should have the same name on both platforms and all scopes

Éric Araujo added the comment: Let me add that os.path.expanduser is the Right Way™ to get a user’s home directory on POSIX too, since not every setup has a $HOME envvar or a /etc/passwd file. The only interface one should use is the pwd module (or getent in shell scripts), and so does os.pa

[issue8299] Improve GIL in 2.7

Kristján Valur Jónsson added the comment: Fyi, here is the output using the unmodified Windows GIL, i.e. without my patch being active: C:\pydev\python\trunk\PCbuild>python.exe ..\Tools\ccbench\ccbench.py -t -y == CPython 2.7a4+.0 (trunk) == == AMD64 Windows on 'Intel64 Family 6 Model 23 Steppi

[issue8299] Improve GIL in 2.7

David Beazley added the comment: I must be missing something, but why, exactly would you want multiple CPU-bound threads to yield every 100 ticks? Frankly, that sounds like a horrible idea that is going to hammer your system with excessive context switching overhead and cache performance pr

[issue5315] signal handler never gets called

Charles-Francois Natali added the comment: I think two things can trigger this problem, both have to do with how signals are handled by the interpreter. Contrarily to what you may think, when a signal is received, its handler is _not_ called. Instead, it's Modules/signalmodule.c signal_handler

[issue8299] Improve GIL in 2.7

David Beazley added the comment: Sorry, but I don't see how you can say that the round-robin GIL and the legacy GIL have the same behavior based solely on the result of a performance benchmark. Do you have any kind of thread scheduling trace that proves they are scheduling threads in exactl

[issue8299] Improve GIL in 2.7

Antoine Pitrou added the comment: > SHA1 hashing (C) > > threads= 1: 1275 iterations/s. balance > threads= 2: 1267 ( 99%)0.7238 > threads= 3: 1271 ( 99%)0.2405 > threads= 4: 1270 ( 99%)0.1508 > > Using the forced "do_yield" helps balance things, but not much. We >

[issue8368] Memory leak on multi-threaded PyObject_CallObject

New submission from Krauzi : Hi guys, i think this is a bug and Matt from h...@python.org suggested me to report it here: I attached a sample project where the memory leak occurs.I created a sample project where the memory leak occurs. It's a visual studio 2008 project and uses windows threads

[issue7443] test.support.unlink issue on Windows platform

Tim Golden added the comment: I put together a trivial patch against the 2.7 trunk (basically: I added a os.rename before the os.remove in test_support.unlink) and reran my test harness with test_zipfile... and it still failed because, of course, test_zipfile calls shutil.rmtree which bypasses t

[issue8369] Add a lint command to distutils

New submission from Éric Araujo : Add a command to run lint tools such as Python -3, pep8, pyflakes, pychecker, pylint. I think this should not be a subcommand of test. The idea comes from buildutils (http://pypi.python.org/pypi/buildutils/). -- assignee: tarek components: Distutils2

[issue8369] Add a lint command to distutils

Éric Araujo added the comment: Also, think about running reindent.py and lib2to3 fixers such as idioms or ws_comma. -- ___ Python tracker ___ ___

[issue8241] py2_test_grammar.py contains invalid syntax for 2.6

Benjamin Peterson added the comment: 2010/4/11 Martin v. Löwis : > > Martin v. Löwis added the comment: > > Benjamin, ISTM that the tests in lib2to3/tests/data/py2_test_grammar aren't > run at all, as part of regrtest. If so, the entire file could be removed. True, but then it would become ou

[issue7443] test.support.unlink issue on Windows platform

Jason R. Coombs added the comment: When I was working on a routine to checkout/patch/build/test/cleanup Python (see https://svn.jaraco.com/jaraco/python/jaraco.develop, and particularly scripts/test-windows-symlink-patch.py), I ran into a similar problem during the cleanup step. I tried using

[issue8299] Improve GIL in 2.7

Kristján Valur Jónsson added the comment: David, I don't necessarily think it is reasonable to yield every 100 opcodes, but that is the _intent_ of the current code base. Checkinterval is set to 100. If you don't want that, then set it higher. Your statement is like saying: "Why would you w

[issue8368] Memory leak on multi-threaded PyObject_CallObject

Antoine Pitrou added the comment: Why do you think PyObject_CallObject() is the culprit? There could be any number of reasons for a memory leak: - cyclic references needing to be cleared (have you tried calling PyGC_Collect()?) - reference leak(s) in your own internal logic - inefficiencies in

[issue8366] OS X universal builds fail on 2.7b1 and py3k with "Don't know machine value for archs"

Changes by R. David Murray : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue8299] Improve GIL in 2.7

Antoine Pitrou added the comment: > Antoine (2): The need to have do_yield is a symptom of the brokenness > of the GIL. Of course it is. But the point of the benchmark is to give valid results even with the old broken GIL. I could remove do_yield and still have it give valid results, but that

[issue8370] change module "builtins" to "__builtin__" in __import__ documentation

New submission from Chris Jerdonek : The "builtins" module referenced in the Python 2.6 __import__ documentation does not seem to exist in Python 2.6: http://docs.python.org/library/functions.html#__import__ These should probably be changed to __builtin__: http://docs.python.org/library/__bui

[issue8370] change module "builtins" to "__builtin__" in __import__ documentation

Changes by Chris Jerdonek : -- assignee: -> georg.brandl components: +Documentation nosy: +georg.brandl ___ Python tracker ___ ___ Pyt

[issue8370] change module "builtins" to "__builtin__" in __import__ documentation

Éric Araujo added the comment: You’re right. This module name has been fixed in the 3.x branch (it used a magic name without reason); when importlib was backported from 3.1 to 2.6, this change must have been overlooked. Are you willing to produce a patch? Regards -- nosy: +merwok _

[issue8370] change module "builtins" to "__builtin__" in __import__ documentation

Chris Jerdonek added the comment: Replaced "builtins" with "__builtin__". Also inserted a missing "the". -- keywords: +patch Added file: http://bugs.python.org/file16870/_issue-8370-1.diff ___ Python tracker _

[issue8370] change module "builtins" to "__builtin__" in __import__ documentation

Chris Jerdonek added the comment: Thanks for the info and quick response. Then this should probably also be applied to trunk (Python 2.7). -- versions: +Python 2.7 ___ Python tracker _

[issue8299] Improve GIL in 2.7

David Beazley added the comment: I'm sorry, I still don't get the supposed benefits of this round-robin patch over the legacy GIL. Given that using interpreter ticks as a basis for thread scheduling is problematic to begin with (mostly due to the fact that ticks have totally unpredictable e

[issue8368] Memory leak on multi-threaded PyObject_CallObject

Krauzi added the comment: i think the PyObject_Call* is the problem because when i comment it out, i do not longer get leaks. The arguments are also correctly decremented because i also can use NULL as argument and i get the same mem leaks like before. --

[issue8370] change module "builtins" to "__builtin__" in __import__ documentation

Chris Jerdonek added the comment: Would it make sense to put a "New in version 3.1" at the top of this page: http://docs.python.org/py3k/library/builtins.html (perhaps also with a note explaining that the module replaces __builtin__). I actually wasn't able to confirm when "builtins" was int

[issue8370] change module "builtins" to "__builtin__" in __import__ documentation

Éric Araujo added the comment: > (perhaps also with a note explaining that the module replaces __builtin__) People used to 2.x will know about the name change; people new to Python with 3.x (the happy ones!) will not this this information, except perhaps to understand outdated docs or snippets

[issue8370] change module "builtins" to "__builtin__" in __import__ documentation

Éric Araujo added the comment: Your first patch seems good to me; wait for a core developer’s answer before taking time to add notes about renamed modules everywhere. Cheers -- ___ Python tracker

[issue5315] signal handler never gets called

Antoine Pitrou added the comment: Thanks for the detailed analysis, Charles-François. > Finally, I think that the documentation should be rephrased: Yes, I think so. > Furthermore, under Linux 2.6 and NPTL, getpid() returns the main thread > PID even from another thread. Yes, those threads b

[issue6507] Enhance dis.dis to autocompile codestrings

Daniel Urban added the comment: I've made a patch, which adds a disassemble_str function to the dis module. The dis.dis function calls this function if x is a string. Added the following sentence to the documentation: "Strings are first compiled to code objects with the :func:`compile` built-

[issue8108] test_ftplib fails with OpenSSL 0.9.8m

Darryl Miles added the comment: I am unable to get "make test" to run from an unpatched version in SVN (details below of make output). Please find attached an updated patch for your consideration (and testing, as I can't test it due to 'make test' SIGSEGV on CentOS 5.4 i386). Patch Notes:

[issue8371] Add a command to download distributions

New submission from Éric Araujo : Distutils2 should have a command responsible for downloading distributions. This would factor it out of other code in one clear location and allow users to download for later installation. If setup.cfg files grow options for extras, test-requires, build-requir

[issue8366] OS X universal builds fail on 2.7b1 and py3k with "Don't know machine value for archs"

Roumen Petrov added the comment: It seems to that improvement for CFLAGS show bug in python build system - quote for configure: BASECFLAGS="${UNIVERSAL_ARCH_FLAGS} -isysroot ${UNIVERSALSDK} ${BASECFLAGS}" tgt=`sw_vers -productVersion | sed 's/\(10\.[[0-9]]

[issue8368] Memory leak on multi-threaded PyObject_CallObject

Krauzi added the comment: kay updated the code. Please use this: http://paste.pocoo.org/show/200484/ smaller code but problem still the same. -- ___ Python tracker ___ __

[issue8368] Memory leak on multi-threaded PyObject_CallObject

Changes by Krauzi : Removed file: http://bugs.python.org/file16868/Python Bug.zip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue8368] Memory leak on multi-threaded PyObject_CallObject

Martin v. Löwis added the comment: I've ported the program to Linux (see attached tar file). I cannot observe any memory leak here - even if I let the program run for a long time (linking with Python 2.6). Memory usage in top goes up and down, but never over some upper limit. The only change

[issue8108] test_ftplib fails with OpenSSL 0.9.8m

Antoine Pitrou added the comment: To just run the test_ftplib tests, you can use: $ ./python -m test.regrtest -v -uall test_ftplib (Other tests involving SSL sockets are test_ssl, test_smtpnet, test_imaplib and test_poplib) > 1) Some thing that concern me, the "unwrap()" philosophy looks to b

[issue8366] OS X universal builds fail on 2.7b1 and py3k with "Don't know machine value for archs"

Ned Deily added the comment: Setting CPPFLAGS to include the SDK is needed to make sure some of the autoconf tests work correctly by using the SDK's header files rather than those from /. But, you're right, it shouldn't throw away other CPPFLAGS settings. Plus that whole test there is suspe

[issue6507] Enhance dis.dis to autocompile codestrings

Raymond Hettinger added the comment: +1 -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue7443] test.support.unlink issue on Windows platform

Martin v. Löwis added the comment: 1. I agree that we should fix the unlinking problem on Windows. I also think that such a fix should be independent of the test suite - many people run into failed unlink problems. 2. Tim already said it, but I repeat: the common theory is that the culprit fo

[issue8372] socket: Buffer overrun while reading unterminated AF_UNIX addresses

New submission from David Watson : The makesockaddr() function in the socket module assumes that AF_UNIX addresses have a null-terminated sun_path, but Linux actually allows unterminated addresses using all 108 bytes of sun_path (for normal filesystem sockets, that is, not just abstract addresses

[issue8211] configure: ignore AC_PROG_CC hardcoded CFLAGS

Marc-Andre Lemburg added the comment: Victor, could you please fix the patch or revert it ? Thanks. -- ___ Python tracker ___ ___ Pyt

[issue8372] socket: Buffer overrun while reading unterminated AF_UNIX addresses

Changes by David Watson : Added file: http://bugs.python.org/file16875/return-unterminated-2.x.diff ___ Python tracker ___ ___ Python-bugs-list

[issue8372] socket: Buffer overrun while reading unterminated AF_UNIX addresses

Changes by David Watson : Added file: http://bugs.python.org/file16876/return-unterminated-3.x.diff ___ Python tracker ___ ___ Python-bugs-list

[issue7443] test.support.unlink issue on Windows platform

Tim Golden added the comment: I'm afraid that the problem doesn't lie in the unlink: DeleteFile succeeds. The problem is that the file is only marked for delete until such time as the last SHARE_DELETE handle on it is closed. Until that time, an attempt to (re)create the file for anything other

[issue7433] MemoryView memory_getbuf causes segfaults, double call to tp_releasebuffer

Changes by Meador Inge : -- nosy: +minge ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/

[issue8372] socket: Buffer overrun while reading unterminated AF_UNIX addresses

Changes by David Watson : Added file: http://bugs.python.org/file16877/addrlen-2.x.diff ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue8372] socket: Buffer overrun while reading unterminated AF_UNIX addresses

Changes by David Watson : Added file: http://bugs.python.org/file16878/addrlen-3.x.diff ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue8211] configure: ignore AC_PROG_CC hardcoded CFLAGS

Marc-Andre Lemburg added the comment: Reopening the ticket: it shouldn't have been closed. I'm also making this a release blocker, since this needs to be fixed before the next release - the CC variable has to be initialized by the build system and breaking this in general for all default buil

[issue8211] configure: ignore AC_PROG_CC hardcoded CFLAGS

Changes by Marc-Andre Lemburg : -- resolution: fixed -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue8372] socket: Buffer overrun while reading unterminated AF_UNIX addresses

Changes by David Watson : Added file: http://bugs.python.org/file16879/test-2.x.diff ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue8372] socket: Buffer overrun while reading unterminated AF_UNIX addresses

Changes by David Watson : Added file: http://bugs.python.org/file16880/test-3.x.diff ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue8373] socket: AF_UNIX socket paths not handled according to PEP 383

New submission from David Watson : In 3.x, the socket module assumes that AF_UNIX addresses use UTF-8 encoding - this means, for example, that accept() will raise UnicodeDecodeError if the peer socket path is not valid UTF-8, which could crash an unwary server. Python 3.1.2 (r312:79147, Mar 23 2

[issue8373] socket: AF_UNIX socket paths not handled according to PEP 383

David Watson added the comment: This patch does the same thing without fixing issue #8372 (not that I'd recommend that, but it may be easier to review). -- Added file: http://bugs.python.org/file16882/af_unix-pep383-no-8372-fix.diff ___ Python tracke

[issue8373] socket: AF_UNIX socket paths not handled according to PEP 383

Changes by David Watson : Added file: http://bugs.python.org/file16883/test-existing.diff ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue8373] socket: AF_UNIX socket paths not handled according to PEP 383

Changes by David Watson : Added file: http://bugs.python.org/file16884/test-new.diff ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue8373] socket: AF_UNIX socket paths not handled according to PEP 383

Changes by David Watson : Added file: http://bugs.python.org/file16885/af_unix-pep383-doc.diff ___ Python tracker ___ ___ Python-bugs-list mail

[issue8108] test_ftplib fails with OpenSSL 0.9.8m

Darryl Miles added the comment: To explain why you need 2 modes, a client/server would expect to do the following pseudo actions for maximum efficiency: set_socket_timeout(600_SECONDS) # or useful default send_data_over_ssl("QUIT\r\n") shutdown(SSL_SHUTDOWN_MODE_SENT) flush_data_down_to_socke

[issue8211] configure: ignore AC_PROG_CC hardcoded CFLAGS

Ned Deily added the comment: To be totally fair, it is likely that part of the OS X breakage was caused by the original code inadvertently working around the original CFLAGS misbehavior. From an OS X perspective, it may be best to just fix the new issue and move on. -- __

[issue8372] socket: Buffer overrun while reading unterminated AF_UNIX addresses

Changes by Antoine Pitrou : -- nosy: +haypo, loewis priority: -> high stage: -> patch review versions: -Python 2.5, Python 3.3 ___ Python tracker ___ __

[issue8373] socket: AF_UNIX socket paths not handled according to PEP 383

Changes by Antoine Pitrou : -- nosy: +haypo, loewis priority: -> normal stage: -> patch review versions: -Python 3.3 ___ Python tracker ___

[issue7443] test.support.unlink issue on Windows platform

Martin v. Löwis added the comment: > I'm afraid that the problem doesn't lie in the unlink: DeleteFile > succeeds. The problem is that the file is only marked for delete > until such time as the last SHARE_DELETE handle on it is closed. Then we shouldn't use DeleteFile in the first place to del

[issue8368] Memory leak on multi-threaded PyObject_CallObject

Antoine Pitrou added the comment: Thanks Martin. I see no leak here either (Linux with Python 2.6 and 2.7). -- ___ Python tracker ___

[issue8368] Memory leak on multi-threaded PyObject_CallObject

Krauzi added the comment: oh no then it's a windows bug. Now i understand why many devs use linux instead of windows.. -- ___ Python tracker ___

[issue8253] add a resource+files section in setup.cfg

Éric Araujo added the comment: I’ve read some distutils-sig threads about this. Do you still want to write a PEP for it before implementation? -- ___ Python tracker ___

[issue7443] test.support.unlink issue on Windows platform

Tim Golden added the comment: > Then we shouldn't use DeleteFile in the first place to delete the file, > but instead CreateFile, with DELETE access (and FILE_SHARE_DELETE > sharing). If that fails, we need to move the file to the bin > (see unlink_nt for details). I see what you're getting at.

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

Tony Locke added the comment: I've created a patch for parse.py against the py3k branch, and I've also included ndim's test cases in that patch file. When returning the host name of an IPv6 literal, I don't include the surrounding '[' and ']'. For example, parsing http://[::1]:5432/foo/ gives

[issue2054] add ftp-tls support to ftplib - RFC 4217

Giampaolo Rodola' added the comment: Thinking back about this, I wonder whether "FTPS" could be a better name to use instead of "FTP_TLS". It's shorter, easier to remember, and also makes more sense since also SSL can be used, not only TLS. -- ___

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

Éric Araujo added the comment: Seems sensible: Delimiters are not part of components. -- nosy: +merwok ___ Python tracker ___ ___ Pyth

[issue2054] add ftp-tls support to ftplib - RFC 4217

Éric Araujo added the comment: It doesn’t look like a constant, too. httplib.Client, ftplib.Client, ftplib.SecureClient would be much more descriptive than httplib.HTTP and ftplib.FTP. Any interest about adding aliases? Regards -- nosy: +merwok __

[issue2054] add ftp-tls support to ftplib - RFC 4217

Antoine Pitrou added the comment: > Thinking back about this, I wonder whether "FTPS" could be a better name to > use instead of "FTP_TLS". > It's shorter, easier to remember, and also makes more sense since also SSL > can be used, not only TLS. What do you mean by "also SSL can be used"? Wik

[issue8368] Memory leak on multi-threaded PyObject_CallObject

Martin v. Löwis added the comment: I can't reproduce the problem on Windows, either. The attached project runs the thread creation in a loop (leaving the 3s sleep in the code). I see (in process viewer) that the Commit Size varies between 13MB and 14MB; there is no indication of a leak.

[issue7443] test.support.unlink issue on Windows platform

Martin v. Löwis added the comment: > Would you agree that py3k is the only target branch worth aiming for? Most certainly, yes. -- ___ Python tracker ___ ___

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

Antoine Pitrou added the comment: I think parsing should be a bit more careful. For example, what happens when you give 'http://dead:beef::]/foo/' as input (note the missing opening bracket)? -- nosy: +pitrou ___ Python tracker

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

Antoine Pitrou added the comment: By the way, updating the RFC list as done in python-urlparse-rfc2732-rfc-list.patch is also a good idea. -- ___ Python tracker ___

[issue8368] Memory leak on multi-threaded PyObject_CallObject

Krauzi added the comment: ah no you misunderstood me. Please add a system("pause") and a system("pause") at the beginning of the while(1)-loop and one at the end. Then compare the memory usage of the program at the beginning (lets say it's 2,6 MB) with the usage at the second pause. In may ca

[issue2987] RFC2732 support for urlparse (e.g. http://

Éric Araujo added the comment: Isn’t “http://dead:beef::]/foo/“ and invalid URI? Regarding doc, see also #5650. -- title: RFC2732 support for urlparse (e.g. http://[::1]:80/) -> RFC2732 support for urlparse (e.g. http:// ___ Python tracker

[issue5650] Obsolete RFCs should be removed from doc of urllib.urlparse

Éric Araujo added the comment: See also #2987 -- title: Obsolete RFC's should be removed from doc of urllib.urlparse -> Obsolete RFCs should be removed from doc of urllib.urlparse ___ Python tracker __

[issue2987] RFC2732 support for urlparse (IPv6 addresses)

Antoine Pitrou added the comment: > Isn’t “http://dead:beef::]/foo/“ and invalid URI? That's the point, it shouldn't parse as a valid one IMO. -- title: RFC2732 support for urlparse (e.g. http:// -> RFC2732 support for urlparse (IPv6 addresses) ___

[issue7301] Add environment variable $PYTHONWARNINGS

Stefan Krah added the comment: The changes in main.c in r79881 don't look right: strtok() is used on the string returned by getenv(), which must not be modified. Also (and this admittedly cosmetic), perhaps use a static buffer like wchar_t warning[128] or use a single allocation before the for

[issue7301] Add environment variable $PYTHONWARNINGS

Philip Jenvey added the comment: The pending patch for py3k fixes the modification of the env value (trunk already has a fix for that). That patch is also doing the conversion to wchar_t via the char2wchar function now, with that reusing a single buffer seems out of the question --

[issue8070] Infinite loop in PyRun_InteractiveLoopFlags() if PyRun_InteractiveOneFlags() raises an error

STINNER Victor added the comment: I don't have time to write a better patch, please improve mine :-) -- ___ Python tracker ___ ___ Pyt

[issue7946] Convoy effect with I/O bound threads and New GIL

Charles-Francois Natali added the comment: A couple remarks on BFS-based patch: - nothing guarantees that you'll get a msec resolution - gettimeofday returns you wall clock time: if a process that modifies time is running, e.g. ntpd, you'll likely to run into trouble. the value returned is _no

[issue8374] Some locales are unsupported

New submission from Luke Jennings : In the locale module there are some locales that are not supported these the ones that I am aware of are nl_AW, sr_RS sr_ME. This information was due to a project that captures screenshots in different languages and we have to retrieve the language code. Rel

[issue8374] Some locales are unsupported

Éric Araujo added the comment: Hello Not a local expert here, but since this module relies on the underlying libc locale support. Do other programs work correctly with this locale? Apart from that, your program needs to catch and handle exceptions anyway. Martin, I’m making you nosy, since y

[issue8374] Some locales are unsupported

Éric Araujo added the comment: Sorry for sending this too fast. The beginning should read: Not a locale expert here, but since this module relies on the underlying libc locale support, the bug is not Python-specific. -- ___ Python tracker

[issue8374] Some locales are unsupported

Luke Jennings added the comment: Other programs do work with the local. I am working on dealing with exceptions, I am rather new to programing and thought it would also be good to try and get this fixed in the original module. -- ___ Python tracke

  1   2   >