[issue9338] argparse optionals with nargs='?', '*' or '+' can't be followed by positionals

paul j3 added the comment: I need to make one correction to my last post: '-x 1 2 -w 3 4 5 6', # w:3, x:[1,2], y:4, z:[5,6] + # w:3, x:[1], y:2, z:[4,5,6] - The second solution is only possible if 'z' is not consumed when 'y' is being processed. In current ver

[issue17973] '+=' on a list inside tuple both succeeds and raises an exception

New submission from Andy Chugunov: At the same time append() succeeds silently, while simple '+' fails. Here's an example: >>> a = ([1],) >>> a[0].append(2) >>> a ([1, 2],) >>> a[0] += [3] Traceback (most recent call last): File "", line 1, in a[0] += [3] TypeError: 'tuple' object does no

[issue17973] '+=' on a list inside tuple both succeeds and raises an exception

Changes by Ronald Oussoren : -- assignee: -> ronaldoussoren ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue17973] '+=' on a list inside tuple both succeeds and raises an exception

Ronald Oussoren added the comment: This is a side effect to the way the in place operators work. Basically "a[0] += [3]" is evaluated as: a[0] = a[0].__iadd__([3]) The call to __iadd__ succeeds, which is why the list is updated, but you get an exception when the interpreter tries to updat

[issue17973] '+=' on a list inside tuple both succeeds and raises an exception

Ronald Oussoren added the comment: I'm closing this issue as rejected because the current behavior is intentional, although it is confusing (IMO). -- resolution: -> rejected status: open -> closed ___ Python tracker

[issue17973] '+=' on a list inside tuple both succeeds and raises an exception

Changes by Florent Xicluna : -- nosy: +flox ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue17128] OS X system openssl deprecated - installer should build local libssl

Ronald Oussoren added the comment: The RVM issue is wrong, ML still includes OpenSSL. Apple has deprecated the use of the system install of OpenSSL, but the library and include files are still there. There are two paths for avoiding the deprecated library: either ship your own build of OpenSS

[issue16531] Allow IPNetwork to take a tuple

Kiyoshi Aman added the comment: I would instead suggest a cidr or netmask kwarg, rather than accepting a tuple as first argument. -- nosy: +Kiyoshi.Aman ___ Python tracker ___ _

[issue17969] multiprocessing crash on exit

Kristján Valur Jónsson added the comment: Catching regressions is what we have the regression tests for. If it is not in caught by the regression tests, then it is not a regression, by definition. Bug fix mode is for fixing bugs, IMHO. Yes, I have patched my local version. The reason I am here

[issue17950] Dynamic classes contain non-breakable reference cycles

Kristján Valur Jónsson added the comment: Thanks Guido. The current patch provides the property you ask for. I will see if I can make the "fiddling" of the internal tuple less magical. I have one other question for you: The standard "mro" puts the class in the 0th position. But apparently, t

[issue17969] multiprocessing crash on exit

Richard Oudkerk added the comment: Kristjan, could you confirm whether joining the pool explicitly before shutdown (in the way I suggested earlier) fixes the problem. I think it should -- at shutdown you won't switch to a thread if it has already been joined. -- _

[issue17969] multiprocessing crash on exit

Antoine Pitrou added the comment: > Catching regressions is what we have the regression tests for. If it > is not in caught by the regression tests, then it is not a > regression, by definition. Call it what you want :-) The bottom line is that we'll release a 2.7.5 soon because of breakage int

[issue1772673] Replacing char* with const char*

Serhiy Storchaka added the comment: In C++ we may overload functions for backward compatibility: PyAPI_FUNC(int) PyArg_ParseTupleAndKeywords(PyObject *, PyObject *, const char *, const char * const *, ...); PyAPI_FUNC(int) PyArg_VaParseTupleAndKeywords(PyObject *, PyObjec

[issue17969] multiprocessing crash on exit

Charles-François Natali added the comment: > Catching regressions is what we have the regression tests for. If it is not > in caught by the regression tests, then it is not a regression, by definition. You do realize this sentence doesn't make sense, do you? -- __

[issue17974] Migrate unittest to argparse

New submission from Antoine Pitrou: Attached patch migrates unittest to argparse. This doesn't make discover handling much saner, given the awful way it's originally implemented. -- components: Library (Lib) files: unittest_argparse.patch keywords: patch messages: 189212 nosy: ezio.melo

[issue17974] Migrate unittest to argparse

Michael Foord added the comment: What's the benefit of this change? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue14596] struct.unpack memory leak

Antoine Pitrou added the comment: I don't think Serhiy's patch should be blocked by a larger issue. I suppose you could rebase easily over his changes. -- versions: +Python 3.4 -Python 2.7, Python 3.2, Python 3.3 ___ Python tracker

[issue17974] Migrate unittest to argparse

Antoine Pitrou added the comment: I was considering making it possible to customize command-line options, as requested by Guido, and it's better to expose the modern API rather than the more obsolete one. -- ___ Python tracker

[issue16024] Doc cleanup regarding path=fd, dir_fd, follow_symlinks, etc

A.M. Kuchling added the comment: Kaleb Robertson's changes look good. Larry, do you want to go ahead and commit this? -- ___ Python tracker ___

[issue17974] Migrate unittest to argparse

Michael Foord added the comment: Ok, feel free to reimplement discovery command line handling if it can be done in a compatible-but-less-horrible way. Anyway, the patch looks fine and a couple of minor cleanups in there. -- ___ Python tracker

[issue17974] Migrate unittest to argparse

Serhiy Storchaka added the comment: I don't see much sense in this modernization, while the code does not use the capabilities of argparse (and even optparse). Why USAGE_AS_MAIN/USAGE_FROM_MODULE/etc exist, why help is not generated automatically? Why -v/-q store boolean flags instead of chang

[issue17969] multiprocessing crash on exit

Kristján Valur Jónsson added the comment: Richard, I'll review implement your change. It is a bit tricky to test this, since I can only tell after a few days if the particular (rare) problem has been fixed. The crash is a rare one but consistently happens with some probability we use multipr

[issue17974] Migrate unittest to argparse

Michael Foord added the comment: Test discovery and new options (buffer, failfast etc) were bolted onto an old and ugly design. Yes the code could use an overhaul and rebuilding from scratch - but doing that whilst remaining fully compatible with all the existing usage patterns is "difficult".

[issue17974] Migrate unittest to argparse

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue17969] multiprocessing crash on exit

Kristján Valur Jónsson added the comment: Richard, reading the multiprocessing.py code, it appears that your suggestion of closign and joining the Pool() object should also do the trick. Doing that will certainly also fix this particular case. I'll implement that in our local application cod

[issue17955] Minor updates to Functional HOWTO

A.M. Kuchling added the comment: Updated version of the patch: * uses 'r' instead of 'N'. * removes the old outline and some notes at the end. * minor rewriting. -- Added file: http://bugs.python.org/file30257/functional.txt ___ Python tracker

[issue11245] Implementation of IMAP IDLE in imaplib?

Changes by Dmitry Shachnev : -- nosy: +mitya57 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue17975] libpython3.so conflicts between $VERSIONs

New submission from Patrick Welche: I currently have python 2.7 and 3.2 installed concurrently. I just tried to install 3.3 as well, but a file conflicts between 3.2 and 3.3. It is libpython3.so. Given that we go out of our way e.g. with $(INSTALL_DATA) Misc/python.pc $(DESTDIR)$(LIBPC)/pytho

[issue17927] Argument copied into cell still referenced by frame

Guido van Rossum added the comment: Would you mind doing the backport then? -- ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue17970] Mutlithread XML parsing cause segfault

Christian Heimes added the comment: In my opinion it's fine to document Python's XML parser as not thread-safe and leave locking to the user. Any fancy locking or tracking is going to make it slower for users. Any it takes a lot of effort to implement the feature, too. lxml offers a faster XML

[issue17976] file.write doesn't raise IOError when it should

New submission from Jaakko Moisio: file.write doesn't sometimes raise IOError when it should, e.g. writing to /dev/full in line buffered mode: jaakko@jm-laptop:~$ python Python 2.7.5+ (2.7:a32a3b79f5e8, May 14 2013, 14:20:11) [GCC 4.7.2] on linux2 Type "help", "copyright", "credits" or "licens

[issue17922] Crash in clear_weakref

Jan Safranek added the comment: On 05/09/2013 09:07 AM, Jan Safranek wrote: > > Jan Safranek added the comment: > > On 05/07/2013 05:32 PM, Antoine Pitrou wrote: >> Jan, one possibility would be for Pegasus to stop "unloading" Python, >> it seems. > > It is always possibility. Actually, Pegasu

[issue17977] urllib.request.urlopen() cadefault argument is documented with wrong default value

New submission from Barry A. Warsaw: The docs[1] say: .. function:: urlopen(url, data=None[, timeout], *, cafile=None, capath=None, cadefault=True) The code[2] says: def urlopen(url, data=None, timeout=socket._GLOBAL_DEFAULT_TIMEOUT, *, cafile=None, capath=None, cadefault=False):

[issue17977] urllib.request.urlopen() cadefault argument is documented with wrong default value

Roundup Robot added the comment: New changeset e2288953e9f1 by Barry Warsaw in branch '3.3': - Issue #17977: The documentation for the cadefault argument's default value http://hg.python.org/cpython/rev/e2288953e9f1 New changeset 85ecc4761a6c by Barry Warsaw in branch 'default': - Issue #17977:

[issue17977] urllib.request.urlopen() cadefault argument is documented with wrong default value

Changes by Barry A. Warsaw : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue17936] O(n**2) behaviour when adding/removing classes

Kristján Valur Jónsson added the comment: Yes, thanks for pointing that out, Antoine, I have made the change locally. -- ___ Python tracker ___ __

[issue17950] Dynamic classes contain non-breakable reference cycles

Armin Rigo added the comment: Well, adding weak references left and right to break cycles is going to subtly change or break people's code and hasn't been done so far, but that's only my opinion. Anyway, I want to correct what you say about tp_subclasses: yes, tp_subclasses is a list of weakr

[issue17970] Mutlithread XML parsing cause segfault

Amaury Forgeot d'Arc added the comment: In my opinion it's not fine to let Python crash. The implementation could be similar to the one in bufferedio.c, it's quite lightweight. -- ___ Python tracker __

[issue17976] file.write doesn't raise IOError when it should

Charles-François Natali added the comment: > I assume my glibc and fwrite aren't broken though Actually, it's a glibc bug when the last character is a '\n': $ python -c "f = open('/dev/full', 'w', 1); f.write('hello'); f.close()" Traceback (most recent call last): File "", line 1, in IOError

[issue14596] struct.unpack memory leak

Meador Inge added the comment: > I don't think Serhiy's patch should be blocked by a larger issue. > I suppose you could rebase easily over his changes. Where rebase=undo, sure. The changes for issue3132 are pretty extensive (the basic data structures are changed). And as mentioned in msg16589

[issue17976] file.write doesn't raise IOError when it should

Serhiy Storchaka added the comment: Indeed, fwrite() can return expected number of items and set errno. Here is a simple example on C. An output is: setvbuf 0 0 fwrite 5 0 fwrite 1 28 fwrite 1 28 On writing "\n" fwrite returns 1 and set errno to ENOSPC. -- nosy: +serhiy.storchaka Adde

[issue17974] Migrate unittest to argparse

Antoine Pitrou added the comment: > Ok, feel free to reimplement discovery command line handling if it can > be done in a compatible-but-less-horrible way. I don't think it's possible. Best way forward would be to provide a pytest utility that does discovery automatically, and leave "python -m u

[issue17976] file.write doesn't raise IOError when it should

Charles-François Natali added the comment: > Indeed, fwrite() can return expected number of items and set errno. Here is a > simple example on C. An output is: Yeah, who's volunteering to report it to the glibc? That's not a python bug, but I feel bad ignoring it. Note that ferror() isn't rel

[issue17950] Dynamic classes contain non-breakable reference cycles

Guido van Rossum added the comment: Kristjan, it seems you're in over your head. :-) The mro() function is documented here: http://docs.python.org/3/library/stdtypes.html?highlight=mro#class.mro It exists to be called instead of using __mro__ directly; a metaclass can then override what it retu

[issue14596] struct.unpack memory leak

Antoine Pitrou added the comment: Le mardi 14 mai 2013 à 16:37 +, Meador Inge a écrit : > If we feel that this optimization is really critical, then I agree > let's not hold it up and I will just work around it with my patch for > issue3132. I don't see it as that critical, but I understand

[issue17976] file.write doesn't raise IOError when it should

Antoine Pitrou added the comment: Yuck. We can of course workaround this (the glibc is commonly used :-)). Why is ferror() not reliable? -- priority: normal -> low stage: -> needs patch ___ Python tracker ___

[issue17976] file.write doesn't raise IOError when it should

Charles-François Natali added the comment: > Why is ferror() not reliable? Because the glibc doesn't check the errno return code after the write() syscall, and thus doesn't set the file's stream error flag (ferror() just checks this flag). That's what I saw from the code. I was a little surpri

[issue17807] Generator cleanup without tp_del

Roundup Robot added the comment: New changeset edefd3450834 by Antoine Pitrou in branch 'default': Backout c89febab4648 following private feedback by Guido. http://hg.python.org/cpython/rev/edefd3450834 -- ___ Python tracker

[issue17807] Generator cleanup without tp_del

Antoine Pitrou added the comment: After getting some private feedback from Guido, I'm convinced this patch isn't ready for consumption. Objects visible from the frame when it is finalized can be in a weird, incomplete state (Guido reports failing to get the __class__ of an object, for instance

[issue17128] OS X system openssl deprecated - installer should build local libssl

OpenSSL CA file: <https://svn.macports.org/repository/macports/trunk/dports/security/certsync/files/certsync.m>, and a blog message at <http://landonf.bikemonkey.org/code/macosx/certsync.20130514.html> -- ___ Python tracker <http://

[issue17922] Crash in clear_weakref

Antoine Pitrou added the comment: Le mardi 14 mai 2013 à 15:28 +, Jan Safranek a écrit : > libpython2.7.so is not unloaded because python extensions, e.g. > /usr/lib64/python2.7/lib-dynload/_heapq.so depend on it. And _heapq.so > was dlopenened by Python and it was not dlclosed -> glibc does

[issue17976] file.write doesn't raise IOError when it should

Jaakko Moisio added the comment: Thank you for your comments. > I was a little surprised when Jaako says that ferror() is enough to > detect this, so I modified Serhiy code to print ferror(), and actually > ferror() reports an error for subsequent writes, not for the first one > (probably becaus

[issue17950] Dynamic classes contain non-breakable reference cycles

Kristján Valur Jónsson added the comment: Armin: Of course you are right. This is what weak references are for, in a gc world, although their convenience to avoid cycles and enable reference counting to work always makes me forget. I have another ongoing issue regarding tp_subclasses, btw, i

[issue17950] Dynamic classes contain non-breakable reference cycles

Guido van Rossum added the comment: Good call. I think it's perfectly fine for you to do this in your custom 2.7 branch. It feels too fragile to adopt the same approach for Python 3.4 though. -- status: open -> closed ___ Python tracker

[issue14596] struct.unpack memory leak

Meador Inge added the comment: > Are you sure the PEP 3118 changes will land in 3.4? It would be a pity > to lose a simple improvement because it was deferred to a bigger > change. No, I am not sure. That is why I said that I understand if others felt this bug was critical to fix now since the

[issue17978] Python crashes if Py_Initialize/Py_Finalize are called multiple times

New submission from Romulo A. Ceccon: I have patched (see attachment) Python 2.7.4 (as available for download at python.org/download) to disable initialization of Unicode (an embeded system requirement) and now it segfaults with the following program: #include int main(int argc,

[issue17976] file.write doesn't raise IOError when it should

Charles-François Natali added the comment: > Strange. I too modified Serchiy's code and my version of glibc (2.15) set the > error flag at the same fwrite call as errno was set: > > setvbuf 0 0 0 > fwrite 5 0 0 > fwrite 1 28 1 > fwrite 1 28 1 > > (the last column being the return value of ferror

[issue16611] multiple problems with Cookie.py

Éric Araujo added the comment: I have just been bitten by a bug (haven’t checked if it’s covered by the added tests) where Cookies uses string.translate incorrectly: File "/usr/lib/python2.7/Cookie.py", line 323, in _quote if "" == translate(str, idmap, LegalChars): File "/usr/lib/pytho

[issue17976] file.write doesn't raise IOError when it should

Jaakko Moisio added the comment: > Yeah, would you like to write a patch? Yes. It's fileobject-fix3.patch attached to this issue record. -- Added file: http://bugs.python.org/file30262/fileobject-fix3.patch ___ Python tracker

[issue17974] Migrate unittest to argparse

Serhiy Storchaka added the comment: Here is a patch which reimplement discovery command line handling in a i-hope-in-compatible-but-less-horrible way (and fixes some bugs). It is horrible still, but I doubt how many changes can I do without breaking compatibility. If _do_discovery() used only

[issue17979] Cannot build 2.7 with --enable-unicode=no

New submission from Amaury Forgeot d'Arc: python2.7 can't be compiled with --enable-unicode=no Because of a crash in the re module. It's a regression from 2.7.3. $ ./python -c 'import re; re.compile("([a-zA-Z][a-zA-Z0-9_]+)\s*=\s*(.*)")' Traceback (most recent call last): File "", line 1, in

[issue17978] Python crashes if Py_Initialize/Py_Finalize are called multiple times

Amaury Forgeot d'Arc added the comment: The official way to build without unicode is ./configure --enable-unicode=no But see issue17979. -- nosy: +amaury.forgeotdarc ___ Python tracker ___

[issue17977] urllib.request.urlopen() cadefault argument is documented with wrong default value

Senthil Kumaran added the comment: OMG. That's a glaring mistake. Thanks for fixing it. -- nosy: +orsenthil ___ Python tracker ___ ___

[issue15392] Create a unittest framework for IDLE

Terry J. Reedy added the comment: Attached is a 3.3 patch that I *believe* is ready to commit and push. With my Win7 repository build, I tested running one test from a file (after "if __name__ == '__main__':") or command line ('python_d -m idlelib.PathBrowser'); all idle tests with an interacti

[issue7965] Problem with urlparse in Windows XP after a drag and drop

Christopher Bare added the comment: I see Senthil's point, but this tripped me up. -- nosy: +Christopher.Bare ___ Python tracker ___ __

[issue17978] Python crashes if Py_Initialize/Py_Finalize are called multiple times

Romulo A. Ceccon added the comment: I've made some further investigation on this issue. Here's the output and the stack trace using --with-pydebug (and the attached patch applied): run no. 0 [8766 refs] free_list[0]->ob_refcnt before XDECREF: 2 run no. 1 [8844 refs] free

[issue15392] Create a unittest framework for IDLE

Todd Rovito added the comment: Terry I think you have a typo you mean PEP434 (http://www.python.org/dev/peps/pep-0434/) where PEP343 exists. Can you please confirm? -- ___ Python tracker

[issue17974] Migrate unittest to argparse

Changes by Berker Peksag : -- nosy: +berker.peksag ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue15392] Create a unittest framework for IDLE

Terry J. Reedy added the comment: Yes, of course. Thanks for correcting. 434, 434, 434,... -- ___ Python tracker ___ ___ Python-bugs-

[issue17947] Code, test, and doc review for PEP-0435 Enum

Ethan Furman added the comment: Got the pickle issues worked out. Added super to the metaclass' __new__. Checking for illegal names of members and raising ValueError if any are found (I know, I know, safety checks! But such an enum is broken from the getgo so I see no reason to allow those

[issue15392] Create a unittest framework for IDLE

Ezio Melotti added the comment: A few comments about the patch: 1) I would prefer a more explicit idle_test instead of Itest (assuming "I" means idle); 2) having idle_test in Lib/test would be better if possible (see #10572); 3) the tests should only be in idle_test, and not in the "if __name__

[issue17955] Minor updates to Functional HOWTO

Ezio Melotti added the comment: LGTM. -- stage: patch review -> commit review ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue17927] Argument copied into cell still referenced by frame

Roundup Robot added the comment: New changeset 2b4b289c1abb by Benjamin Peterson in branch '3.3': when arguments are cells clear the locals slot (backport of #17927) http://hg.python.org/cpython/rev/2b4b289c1abb -- ___ Python tracker

[issue17927] Argument copied into cell still referenced by frame

Changes by Benjamin Peterson : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue15392] Create a unittest framework for IDLE

Todd Rovito added the comment: Terry, On my Mac with "hg revert -a" and "hg pull -u" the patch fails to apply on CallTips.py and PathBrowser.py under the latest version of Python 3.4. Here is the output when I try to apply the patch: rovitotv-pc:py34 rovitotv$ hg import --no-commit /Volum

[issue15392] Create a unittest framework for IDLE

Ezio Melotti added the comment: Have you tried applying it to 3.3? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue15392] Create a unittest framework for IDLE

Terry J. Reedy added the comment: Todd, the last two commits, both rather trivial, I merged from 3.3 to 3.4 would not apply for no reason I could see. I wonder is there is something wrong with the repository. I wrote about the problem on the committer's list a few days ago, but got no response

[issue15392] Create a unittest framework for IDLE

Ezio Melotti added the comment: > I wonder is there is something wrong with the repository. The repo looks ok to me. You could try to run "hg verify" on your machine id you want to make sure your clone is ok. > I wrote about the problem on the committer's list a few days ago, > but got no res