[issue15928] Open url with proxy causes TypeError
Senthil Kumaran added the comment: Have a look at the ProxyHandler example in the Examples here - http://docs.python.org/library/urllib2.html#examples Also, construct the full url properly with urlencoded data as params. Your report does not give any details of problem. -- nosy: +orsenthil resolution: - invalid stage: - committed/rejected ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15928 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15928] Open url with proxy causes TypeError
Changes by Senthil Kumaran sent...@uthcode.com: -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15928 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15928] Open url with proxy causes TypeError
zhang kai added the comment: Well, I do have encoded the params, that is not the problem. Also these code did work for most of the time, I don't know why this bug happen so I don't know any details about the problem. Sorry about that. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15928 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15926] Segmentation fault after multiple reinitializations
Stefan Krah added the comment:
The segfault occurs in a path in import.c that has a comment XXX this
this should really not happen.:
Program received signal SIGSEGV, Segmentation fault.
0x0047d733 in type_dealloc (type=0x8381e0) at Objects/typeobject.c:2694
2694_PyObject_GC_UNTRACK(type);
(gdb) bt
#0 0x0047d733 in type_dealloc (type=0x8381e0) at
Objects/typeobject.c:2694
#1 0x0045d8ef in free_keys_object (keys=0x8eb810) at
Objects/dictobject.c:374
#2 0x00463513 in dict_dealloc (mp=0x8fa9c0) at
Objects/dictobject.c:1392
#3 0x00503118 in _PyImport_FixupExtensionObject (mod=0xa0cd40,
name=0xb1fa90,
filename=0xb1fa90) at Python/import.c:498
(gdb) f 3
#3 0x00503118 in _PyImport_FixupExtensionObject (mod=0xa0cd40,
name=0xb1fa90,
filename=0xb1fa90) at Python/import.c:498
498 Py_DECREF(def-m_base.m_copy);
(gdb) l
493 if (def-m_size == -1) {
494 if (def-m_base.m_copy) {
495 /* Somebody already imported the module,
496likely under a different name.
497XXX this should really not happen. */
498 Py_DECREF(def-m_base.m_copy);
499 def-m_base.m_copy = NULL;
500 }
501 dict = PyModule_GetDict(mod);
502 if (dict == NULL)
--
nosy: +brett.cannon, eric.snow, pitrou, skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15926
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15926] Segmentation fault after multiple reinitializations
Stefan Krah added the comment: Maybe related: If you increase the number of passes in Modules/_testembed.c, pass 9 fails: --- Pass 9 --- _testembed: Objects/typeobject.c:2693: type_dealloc: Assertion `type-tp_flags (1L9)' failed. Aborted -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15926 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15926] Segmentation fault after multiple reinitializations
Changes by Stefan Krah stefan-use...@bytereef.org: -- components: +Interpreter Core stage: - needs patch type: - crash ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15926 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5766] Mac/scripts/BuildApplet.py reset of sys.executable during install can cause it to use wrong modules
Ned Deily added the comment: This problem was caused by a conflict between the expat parser included with Python and the expat parser included with the MacPorts ports of the obsolete pyxml package. The MacPorts project has subsequently deleted the py*-xml ports. A solution for this issue is to remove the obsolete port, something like: sudo port uninstall py26-xml See https://trac.macports.org/ticket/32090 for a similar case and its resolution. -- nosy: +ned.deily resolution: - out of date stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5766 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15898] OSX TTY bug
Martin v. Löwis added the comment: Am 11.09.2012 09:11, schrieb Andrew Moffat: I'm not sure I follow the problem exactly. So you're saying that the failing version uses _cancel sys calls, and that __pthread_testcancel may result in EINTR. But that this is not happening in the trace, and data is being written successfully. I guess I'm wondering where the written bytes went and if there's any way to retrieve them? That's exactly the question, and why I say that is must be an OS bug. According to the trace, the OS accepted the data, so if they got lost, it's their fault. Unfortunately, the dtruss doesn't decode the ioctl arguments, so it's not easy to tell whether they are right. You could try running it with -a to see whether this gives more information. Please don't paste the traces, though, but attach them (the editing is surely appreciated, though). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15898 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15881] multiprocessing 'NoneType' object is not callable
Changes by Mitar mmi...@gmail.com: -- nosy: +mitar ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15881 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15929] argparse non alphanum characters replacement
New submission from Julien Castets:
argparse.add_argument replaces dashes with underscores. If an argument contains
another non alphanum character, accessing to it will result to a syntax error.
#! /usr/bin/env python
import argparse
if __name__ == '__main__':
argParser = argparse.ArgumentParser()
argParser.add_argument('--foo+', action='store_true')
arguments = argParser.parse_args()
print 'getattr foo+: %s' % getattr(arguments, 'foo+') # ok
print arguments.foo+ # syntax error
The patch replaces every non alnum character with an underscore.
--
components: None
files: argparse.patch
keywords: patch
messages: 170361
nosy: brmzkw
priority: normal
severity: normal
status: open
title: argparse non alphanum characters replacement
type: behavior
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file27178/argparse.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15929
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15928] Open url with proxy causes TypeError
R. David Murray added the comment: What is proxy? Perhaps it does not implement readline correctly. -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15928 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15929] argparse non alphanum characters replacement
R. David Murray added the comment: It would probably be better to have the namespace object support subscripting in order to satisfy this use case. You can use getattr to do it now. (Note that the namespace object should probably use a real dict and a __getattr__ method, since I don't think the language guarantees that you can put non-identifiers in an attribute dict). -- nosy: +bethard, r.david.murray type: behavior - enhancement versions: -Python 2.7, Python 3.1, Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15929 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15929] argparse non alphanum characters replacement
Steven Bethard added the comment: If you need to get things that aren't valid Python identifiers, use vars() to get the dictionary: http://docs.python.org/dev/library/argparse.html#the-namespace-object Changing all non-alphanumeric characters to underscores would be a backwards incompatible change for argparse (it would break existing code). That means we'd need to have a long deprecation period before the change. I'm not sure it's really worth it for this feature when vars() already gives you what you need easily. I'm therefore closing this a won't fix, but if you feel really strongly that vars() doesn't solve your problem and you want to push through the long deprecation process, feel free to re-open. @R. David Murray: I wouldn't worry about non-identifiers in an attribute dict. This has worked for ages, and changing this would be a seriously backwards incompatible change that couldn't be possible before Python 4. -- resolution: - wont fix status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15929 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
R. David Murray added the comment: I agree with Chris here. We also need to add the various tests he's come up with. IMO the easiest way to restore the original behavior and the preserve the fixes is to make the following single line change: diff --git a/Lib/argparse.py b/Lib/argparse.py --- a/Lib/argparse.py +++ b/Lib/argparse.py @@ -1962,7 +1962,8 @@ # only if it was defined already in the namespace if (action.default is not None and hasattr(namespace, action.dest) and -action.default is getattr(namespace, action.dest)): +action.default is getattr(namespace, action.dest) and +isinstance(action.default, str)): setattr(namespace, action.dest, self._get_value(action, action.default)) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Steven Bethard added the comment: It looks like the correct fix was already applied, but just to chime in here: (1) Yes, the error is that the isinstance(action.default, str) check was lost (2) Yes, it is intended that you can use a string value as your default and the type= converter will be called on that. This feature allows DRY for people that have a complex object that can be specified by a simple string. (3) Yes, the type= converter function should be applied to the default for all action types, not just for the store action. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15929] argparse non alphanum characters replacement
R. David Murray added the comment: Oh, it wasn't CPython that that comment was directed at. But I think you are right: because CPython supports it, I think other implementations will as well, whatever the language spec says or doesn't say (I didn't double check, I'm going on a fuzzy memory of a conversation on python-dev from the pypy folks). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15929 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11385] TextTestRunner methods are not documented
Changes by Julian Berman julian+python@grayvines.com: -- nosy: +Julian ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11385 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
R. David Murray added the comment: The correct fix has not been applied yet. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9592] Limitations in objects returned by multiprocessing Pool
Ask Solem added the comment: I vote to close too as it's very hard to fix in a clean way. A big problem though is that there is a standard for defining exceptions, that also ensures that the exception is pickleable (always call Exception.__init__ with original args), that is not documented (http://docs.python.org/tutorial/errors.html#user-defined-exceptions). Celery has an elaborate mechanism to rewrite unpickleable exceptions, but it's a massive workaround just to keep the workers running, and shouldn't be part of the stdlib. It would help if the Python documentation mentioned this though. Related: http://docs.celeryproject.org/en/latest/userguide/tasks.html#creating-pickleable-exceptions -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9592 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14617] confusing docs with regard to __hash__
Raymond Hettinger added the comment: This can wait until after the release. We will have periodic point releases where further doc updates can go in. -- nosy: +rhettinger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14617 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15929] argparse non alphanum characters replacement
Steven Bethard added the comment: I haven't been following python-dev recently, but the only discussion I remember was for non-strings in __dict__, not non-identifiers. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15929 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Steven Bethard added the comment: Oh, I see, you're right - the recent changes from the Roundup Robot are exactly the wrong changes - special casing _StoreAction, not string defaults. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15930] buffer overrun in wcstombs_errorpos()
New submission from Christian Heimes: Coverity has found a buffer overrun in wcstombs_errorpos() defined at http://hg.python.org/cpython/file/25e41fdc4e60/Objects/unicodeobject.c#l3237 Message: CID 719672: Out-of-bounds access (OVERRUN)At (2): Overrunning array buf of 2 4-byte elements by passing it to a function which accesses it at element index 15 (byte offset 60) using argument 16UL. On a 64bit Linux system SIZE_OF_WCHAR_T is 4 and MB_LEN_MAX 16. In this constellation buf is 8 bytes long (wchar_t[2]) but outbuf has a size of 16 bytes. This causes a buffer overrun in wcstombs(outbuf, buf, sizeof(outbuf)). -- keywords: 3.3regression messages: 170373 nosy: christian.heimes, haypo priority: normal severity: normal status: open title: buffer overrun in wcstombs_errorpos() type: resource usage versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15930 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13990] Benchmarks: 2to3 failures on the py3 side
Brett Cannon added the comment: It's translating properly for me now as well (but on a different machine). I will give it another try when I get home to see if I can reproduce success on the machine that was failing for me previously. -- status: pending - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13990 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13990] Benchmarks: 2to3 failures on the py3 side
Changes by Brett Cannon br...@python.org: -- assignee: benjamin.peterson - brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13990 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12680] cPickle.loads is not thread safe due to non-thread-safe imports
Brett Cannon added the comment: I just checked and this is no longer an issue in Python 3.3. The sys.modules bug isn't a bug as that's how it is supposed to work to prevent partially initialized modules. As for how pickle is doing stuff, that could change if it wouldn't break backwards-compatibility. -- versions: -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12680 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15930] buffer overrun in wcstombs_errorpos()
Christian Heimes added the comment: Georg, this issue might be security relevant and should be reviewed before the next release. -- nosy: +georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15930 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15930] buffer overrun in wcstombs_errorpos()
Stefan Krah added the comment: buf[1] contains NUL if SIZE_OF_WCHAR_T is 4. The man page says: size_t wcstombs(char *dest, const wchar_t *src, size_t n) The conversion can stop for three reasons: 3. The wide-character string has been completely converted, including the terminating L'\0'. In this case the conversion ends in the initial state. The number of bytes written to dest, exclud- ing the terminating '\0' byte, is returned. To me this sounds like there cannot be an invalid write. -- nosy: +skrah ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15930 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Barry A. Warsaw added the comment: On Sep 12, 2012, at 10:57 AM, Steven Bethard wrote: (1) Yes, the error is that the isinstance(action.default, str) check was lost Except that it won't work any more in the original location. I tried it and it broke other tests. Maybe I did it wrong, so please verify by actually applying that patch, backing mine out, and running the full test suite. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Barry A. Warsaw added the comment: On Sep 12, 2012, at 10:39 AM, R. David Murray wrote: diff --git a/Lib/argparse.py b/Lib/argparse.py --- a/Lib/argparse.py +++ b/Lib/argparse.py @@ -1962,7 +1962,8 @@ # only if it was defined already in the namespace if (action.default is not None and hasattr(namespace, action.dest) and -action.default is getattr(namespace, action.dest)): +action.default is getattr(namespace, action.dest) and +isinstance(action.default, str)): setattr(namespace, action.dest, self._get_value(action, action.default)) For me, this results in the following failure. [307/371/1] test_argparse NS(foo='foo_converted') Namespace(foo=0) NS(foo='foo_converted') Namespace(foo=0) test test_argparse failed -- Traceback (most recent call last): File /home/barry/projects/python/cpython/Lib/test/test_argparse.py, line 4608, in test_type_function_call_with_non_string_default self.assertEqual(NS(foo='foo_converted'), args) File /home/barry/projects/python/cpython/Lib/test/test_argparse.py, line 29, in assertEqual super(TestCase, self).assertEqual(obj1, obj2) AssertionError: NS(foo='foo_converted') != Namespace(foo=0) This test was added for the issue #12776 and #11839 fix, and it's pretty obvious why it fails. In the test, default=0 (i.e. a non-string). Do you think test_type_function_call_with_non_string_default() is a valid test of expected semantics? If not, then the test should be removed, and the changeset for #12667 and #11839 should be re-evaluated, at least to determine whether accurate tests of those bugs were applied. If that test is removed, then the above suggested change can be made to fix #15906. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11783] email parseaddr and formataddr should be IDNA aware
Christian Heimes added the comment: 3.3 is in feature freeze mode. This new feature has to go into 3.4. -- nosy: +christian.heimes versions: +Python 3.4 -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11783 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10167] ESET Trojan Alert [python-3.1.2.amd64 ON Win7-64]
Christian Heimes added the comment: We haven't received any similar report and 3.1.2 is outdated, too. I'm closing this bug. -- nosy: +christian.heimes resolution: - out of date status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10167 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Barry A. Warsaw added the comment:
On Sep 12, 2012, at 04:22 AM, Chris Jerdonek wrote:
The argparse documentation makes it pretty clear that 'type' is meant to be
applied only to strings.
Then test_type_function_call_with_non_string_default() which was added to fix
#12776 and #11839 is a bogus test, because it converts default=0 to
'foo_converted'. This is the test that fails if you restore the
isinstance(action.default, str) test.
Also, the parse_args() documentation says, Convert argument strings to
objects and assign them as attributes of the namespace, but it doesn't say
anything about also converting non-string defaults.
Thirdly, the documentation for the default keyword argument says, The
default keyword argument of add_argument(), whose value defaults to None,
specifies what value should be used if the command-line argument is not
present. It doesn't say that the value should be converted before being
used.
In which case, doing *any* conversion of default seems wrong. Meaning, you
can't expect the following to work:
p.add_argument('--file', type=open, default='/etc/passwd')
a = p.parse_args([])
a.file.read()
because no --file argument was given, and a.file will be a string. This
implies that if the command line argument is not given, then user code must
test the type of a.file, and explicitly open it if it's a string, because it
will only be a file object if --file *was* given on the command line.
Then why use type=open at all? You're better off always expecting a.file to
be a string and do the conversion explicitly after you've parsed the
arguments. But maybe that's the right interpretation given the documentation.
However, the original fix for #12776 and #11839 does not follow those
semantics.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15906
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15930] buffer overrun in wcstombs_errorpos()
Stefan Krah added the comment: I'm convinced that this is a false positive: size_t wcstombs(char *dest, const wchar_t *src, size_t n); We have: 1) buf[0] = *wstr and buf[1] = 0. So: 2) wcstombs(NULL, buf, 0) = 4. Then the man page says: ... the programmer should make sure n is greater or equal to wcstombs(NULL,src,0)+1. In this case, wcstombs(NULL, buf, 0) + 1 = 5 and we call: wcstombs(char *dest, const wchar_t *src, 16); -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15930 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15930] buffer overrun in wcstombs_errorpos()
Christian Heimes added the comment: Stefan, I agree with your analysis. With the terminating null wide char wcstombs will never read beyond the end of buf. -- resolution: - invalid status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15930 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Steven Bethard added the comment: I see. So right now, both string defaults and non-string defaults are being converted with the type= function. That seems suspect to me since the documentation explicitly says type= can take any callable that takes a single string argument and returns the converted value, so non-string defaults don't make sense to pass to that function. I believe test_type_function_call_with_non_string_default() comes from Arnaud Fontaine. Arnaud, can you comment on the intent of that test? My thoughts: * We should not be converting non-string defaults, or the documentation's description of the type= argument doesn't make sense. * For the string defaults, I can see the argument for not converting them, and the argparse docs never show them being converted from strings. I thought there was a discussion somewhere where someone had requested the current behavior, but I can't for the life of me find that discussion, so perhaps I'm imagining it... In terms of potential for breaking code, I'm not too worried about removing type conversion for non-string defaults - this never happened before the fix for #12776 and #11839, so I doubt much code depends on it. I am more worried about removing type conversion for string defaults - this has worked for a long time, so there probably is some code that depends on it. -- nosy: +arnau ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
R. David Murray added the comment: *No* code should depend on it: this fix is very recent and is not in any released version of Python, not even the RCs. The bogus test should be removed. When I committed that patch I did not understand the correct (documented) semantics of default conversion, and so did not realize the test was bogus. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
R. David Murray added the comment: Actually, no, the test should not be removed, it should be reversed so as to test the documented behavior. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Barry A. Warsaw added the comment: On Sep 12, 2012, at 03:03 PM, R. David Murray wrote: Actually, no, the test should not be removed, it should be reversed so as to test the documented behavior. Good point. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15931] inspect.findsource fails after directory change
New submission from Gabor Kovacs:
The attached script works in 2.6(.4) but not in 2.7(.3); the script cannot
locate its own source code if invoked by relative path and work directory has
changed. If line 8 uncommented, everything is fine due to caching.
I think this is related to issue #4050 changes in inspect.py.
~ kgabor$ python ./instest.py
None ./instest.py
Traceback (most recent call last):
File ./instest.py, line 10, in module
print inspect.getsourcefile(A), inspect.getfile(A),inspect.findsource(A)
File
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/inspect.py,
line 529, in findsource
raise IOError('source code not available')
IOError: source code not available
~ kgabor$ pwd
/Users/kgabor
~ kgabor$ python /Users/kgabor/instest.py
/Users/kgabor/instest.py /Users/kgabor/instest.py (['import inspect\n', 'import
os\n', '\n', 'class A:\n', ' def __init__(self):\n', ' self.a=1\n', '\n',
'#print inspect.getsourcefile(A),inspect.getfile(A),inspect.findsource(A)\n',
os.chdir('/')\n, 'print inspect.getsourcefile(A),
inspect.getfile(A),inspect.findsource(A)\n'], 3)
--
components: Library (Lib)
files: instest.py
messages: 170389
nosy: kgabor79
priority: normal
severity: normal
status: open
title: inspect.findsource fails after directory change
type: behavior
versions: Python 2.6, Python 2.7
Added file: http://bugs.python.org/file27179/instest.py
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15931
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Steven Bethard added the comment: Ok, sounds good. Let's make the test check the documented behavior, and then add back the isinstance(action.default, str) check. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Changes by Barry A. Warsaw ba...@python.org: Added file: http://bugs.python.org/file27180/15906-3.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Barry A. Warsaw added the comment: On Sep 12, 2012, at 02:48 PM, Steven Bethard wrote: We should not be converting non-string defaults, or the documentation's description of the type= argument doesn't make sense. Agreed. If we also take RDM's suggestion of reversing the sense of test_type_function_call_only_once(), then patch 15906-3.diff would do this[*], restore the isinstance test of action.default, and retain the fix for the regression noted in this issue's description. For the string defaults, I can see the argument for not converting them, and the argparse docs never show them being converted from strings. I thought there was a discussion somewhere where someone had requested the current behavior, but I can't for the life of me find that discussion, so perhaps I'm imagining it... In terms of potential for breaking code, I'm not too worried about removing type conversion for non-string defaults - this never happened before the fix for #12776 and #11839, so I doubt much code depends on it. I am more worried about removing type conversion for string defaults - this has worked for a long time, so there probably is some code that depends on it. Agreed. Removing the conversion of non-string defaults, but retaining the conversion of string defaults is probably the safest course of action. Do we need a new test for conversion of string defaults? [*] Patch is against 2.7, but if we all agree this is the appropriate fix, I will port it to 3.2 and 3.3. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15931] inspect.findsource fails after directory change
Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15931 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Barry A. Warsaw added the comment: On Sep 12, 2012, at 03:40 PM, Steven Bethard wrote: Ok, sounds good. Let's make the test check the documented behavior, and then add back the isinstance(action.default, str) check. See patch 15906-3.diff for Python 2.7. If acceptable, I will apply and forward port it. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
R. David Murray added the comment: Looks good to me. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Barry A. Warsaw added the comment:
Oops, one small correction for 15906-3.diff: In Python 2.7, s/str/basestring/
Obviously isinstance should just check for str-y-ness in Python 3.{2,3}
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15906
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15932] files in the csv documentation's examples are not closed
New submission from berdario: I changed the examples to use the with statement -- assignee: docs@python components: Documentation files: doc.diff keywords: patch messages: 170394 nosy: berdario, docs@python, ezio.melotti priority: normal severity: normal status: open title: files in the csv documentation's examples are not closed Added file: http://bugs.python.org/file27181/doc.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15932 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15923] Building from a fresh clone breaks on Parser/asdl_c.py
Amaury Forgeot d'Arc added the comment: It's most probably related to issue15801: if 'name' is an instance of Python-defined class, then it was considered as a mapping... -- nosy: +amaury.forgeotdarc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15923 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15926] Segmentation fault after multiple reinitializations
Roundup Robot added the comment: New changeset 8d22d9528164 by Antoine Pitrou in branch 'default': Issue #15926: Fix crash after multiple reinitializations of the interpreter. http://hg.python.org/cpython/rev/8d22d9528164 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15926 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Steven Bethard added the comment: Patch, with the basestring amendment, looks good. Do we need a new test for conversion of string defaults? Yeah, I guess go ahead and add one. That will at least document our intentions here, and if we decide to change that later, then it will force us to deprecate the conversion of string defaults first (which we probably should if we're going to.) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15926] Segmentation fault after multiple reinitializations
Antoine Pitrou added the comment: This should be fixed now. Georg, this is up to you whether this deserves being ported to 3.3.0 or not. -- assignee: - georg.brandl nosy: +georg.brandl resolution: - fixed stage: needs patch - committed/rejected ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15926 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15599] test_circular_imports() of test_threaded_import fails on FreeBSD 9.0
Antoine Pitrou added the comment: Stefan, do you plan to commit this patch (or a similar one)? The FreeBSD buildbot is crashing again. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15599 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15933] flaky test in test_datetime
New submission from Antoine Pitrou: Seen on a buildbot: == FAIL: test_today (test.datetimetester.TestSubclassDateTime_Fast) -- Traceback (most recent call last): File /export/home/buildbot/32bits/3.2.cea-indiana-x86/build/Lib/test/datetimetester.py, line 1009, in test_today abs(todayagain - today) timedelta(seconds=0.5)) AssertionError: False is not true http://buildbot.python.org/all/builders/x86%20OpenIndiana%203.2/builds/1341/steps/test/logs/stdio -- components: Tests keywords: easy messages: 170401 nosy: belopolsky, pitrou priority: normal severity: normal stage: needs patch status: open title: flaky test in test_datetime type: behavior versions: Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15933 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15934] flaky test in test_ftplib
New submission from Antoine Pitrou:
Seen on a buildbot:
==
ERROR: test_storlines (test.test_ftplib.TestTLS_FTPClassMixin)
--
Traceback (most recent call last):
File
/export/home/buildbot/64bits/3.x.cea-indiana-amd64/build/Lib/test/test_ftplib.py,
line 583, in test_storlines
self.client.storlines('stor', f)
File
/export/home/buildbot/64bits/3.x.cea-indiana-amd64/build/Lib/ftplib.py, line
811, in storlines
conn.unwrap()
File /export/home/buildbot/64bits/3.x.cea-indiana-amd64/build/Lib/ssl.py,
line 495, in unwrap
s = self._sslobj.shutdown()
socket.timeout: The read operation timed out
http://buildbot.python.org/all/builders/AMD64%20OpenIndiana%203.x/builds/4429/steps/test/logs/stdio
--
components: Tests
messages: 170402
nosy: giampaolo.rodola, pitrou
priority: normal
severity: normal
status: open
title: flaky test in test_ftplib
type: behavior
versions: Python 3.2, Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15934
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15934] flaky test in test_ftplib
Giampaolo Rodola' added the comment: Assigning to me but I won't be able to look into it for a while. -- assignee: - giampaolo.rodola ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15934 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Chris Jerdonek added the comment: Do we need a new test for conversion of string defaults? I think we should also update the documentation of the default keyword argument (and/or the type argument) to remove any ambiguity and make the behavior more clear. Maybe one way to view what is happening (and maybe one way to describe it in the documentation) is that if a default value is a string, the parser treats it as a default for the command-line *argument*, otherwise it treats it as a default for the final *attribute*. Lastly, can we also add the test from one of my first comments above to check that double conversion of strings doesn't take place? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
R. David Murray added the comment: All three of those sound like good ideas (testing string conversion, clarifying docs, adding the no-double conversion test). Do you want to prepare the patch, Chris? Barry can apply his any time and yours can be a followup. We should also make a doc update equivalent to that we made for optparse in issue 5088, but that should probably be a different issue, where we discuss how/whether to change that behavior. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15599] test_circular_imports() of test_threaded_import fails on FreeBSD 9.0
Stefan Krah added the comment: I was hesitating because the other FreeBSD bots don't have that problem. The other option would be to kick out the FreeBSD/kvm bot in favor of FreeBSD/Virtualbox. http://buildbot.python.org/all/buildslaves/koobs-freebsd-clang seems to be very stable. I could take down FreeBSD/kvm altogether. Is Python supposed to work with gil_interval = 1 or is some potential flakiness expected? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15599 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Chris Jerdonek added the comment: Do you want to prepare the patch, Chris? Sure, I should be able to get to this today or tomorrow. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15932] files in the csv documentation's examples are not closed
Brett Cannon added the comment: Quick glance at the patch LGTM. I don't have commit access handy so I can't do it myself ATM. -- nosy: +brett.cannon stage: - commit review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15932 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15599] test_circular_imports() of test_threaded_import fails on FreeBSD 9.0
Antoine Pitrou added the comment: I was hesitating because the other FreeBSD bots don't have that problem. The other option would be to kick out the FreeBSD/kvm bot in favor of FreeBSD/Virtualbox. Well, if the test is just running too slow, changing the switch interval sounds easier to me than deploying a whole new setup. Is Python supposed to work with gil_interval = 1 or is some potential flakiness expected? I don't know. It's not supposed to be widely tunable, though. Most legitimate uses would be to lower or raise the interval a bit, not choose insane values. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15599 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15926] Segmentation fault after multiple reinitializations
Arfrever Frehtes Taifersar Arahesis added the comment: +1 for including the fix in 3.3.0. This segmentation fault was reproducible in test suite of dbus-python: http://cgit.freedesktop.org/dbus/dbus-python/tree/test/import-repeatedly.c -- priority: high - release blocker ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15926 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15933] flaky test in test_datetime
Brett Cannon added the comment: First off, that assertEquals should have a custom error message stating what values the date objects had to better tell how off things were. Second, this can probably be solved by upping the timedelta to something like a minute or something for when it's run on a really slow machine (I mean the test itself is wonky based on the the definition of date.today() and not being able to freeze time, so being upwards of a minute off should be acceptable to verify it's still today). -- nosy: +brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15933 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15599] test_circular_imports() of test_threaded_import fails on FreeBSD 9.0
Stefan Krah added the comment: OK, I'll commit the patch soon. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15599 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Barry A. Warsaw added the comment: On Sep 12, 2012, at 05:19 PM, R. David Murray wrote: All three of those sound like good ideas (testing string conversion, clarifying docs, adding the no-double conversion test). Do you want to prepare the patch, Chris? Barry can apply his any time and yours can be a followup. I will add the no-double-conversion test. I think that will just leave the doc updates for Chris once my patch lands in all three branches. That will be RSN, modulo local test suite runs. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7475] codecs missing: base64 bz2 hex zlib hex_codec ...
Uzume added the comment: Many have chimed in on this topic but I thought I would lend my stance--for whatever it is worth. I also believe most of these do not fit concept of a character codec and some sort of transforms would likely be useful, however most are sort of specialized (e.g., there should probably be a generalized compression library interface al la hashlib): rot13: a (albeit simplistic) text cipher (str to str; though bytes to bytes could be argued since since many crypto functions do that) zlib, bz2, etc. (lzma/xz should also be here): all bytes to bytes compression transforms hex(adecimal) uu, base64, etc.: these more or less fit the description of a character codec as they map between bytes and str, however, I am not sure they are really the same thing as these are basically doing a radix transformation to character symbols and the mapping it not strictly from bytes to a single character and back as a true character codec seems to imply. As evidenced by by int() format() and bytes.fromhex(), float.hex(), float.fromhex(), etc., these are more generalized conversions for serializing strings of bits into a textual representation (possibly for human consumption). I personally feel any type/class.hex(), etc. method would be better off as a format() style formatter if they are to exist in such a space at all (i.e., not some more generalized conversion library--which we have but since 3.x could probably use to be updated and cleaned up). -- nosy: +uzume ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7475 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7475] codecs missing: base64 bz2 hex zlib hex_codec ...
Changes by Uzume uz...@users.sourceforge.net: -- nosy: -uzume ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7475 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Roundup Robot added the comment: New changeset 8f847f66a49f by Barry Warsaw in branch '2.7': A follow up for issue #15906: change the test for calling the type conversion http://hg.python.org/cpython/rev/8f847f66a49f New changeset 088b16bd6396 by Barry Warsaw in branch '3.2': A follow up for issue #15906: change the test for calling the type conversion http://hg.python.org/cpython/rev/088b16bd6396 New changeset 9ae9326cd79a by Barry Warsaw in branch 'default': Merge 3.2 fix updates and tests for issue #15906. http://hg.python.org/cpython/rev/9ae9326cd79a -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15599] test_circular_imports() of test_threaded_import fails on FreeBSD 9.0
Roundup Robot added the comment: New changeset 9b40d018e4cf by Stefan Krah in branch 'default': Issue #15599: FreeBSD on KVM cannot handle a very low switch interval. http://hg.python.org/cpython/rev/9b40d018e4cf -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15599 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Barry A. Warsaw added the comment: Chris, it's all yours. I am however going to close the bug as fixed. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Changes by Barry A. Warsaw ba...@python.org: -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Chris Jerdonek added the comment:
Thanks for committing the change. However--
+def test_no_double_type_conversion_of_default(self):
+def extend(str_to_convert):
+return str_to_convert + '*'
+
+parser = argparse.ArgumentParser()
+parser.add_argument('--test', type=extend, default='*')
+args = parser.parse_args([])
+# The test argument will be two stars, one coming from the default
+# value and one coming from the type conversion being called exactly
+# once.
+self.assertEqual(NS(test='**'), args)
This was actually my concern, that the type conversion would be applied twice,
and the reason for my suggesting the test. This expected value is not the one
we want, because it shows that the argument is getting double converted,
though the test is supposed to assert that double conversion doesn't take place.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15906
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Chris Jerdonek added the comment: Oh, never mind. The initial default value has one star to begin with. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4356] Add key argument to bisect module functions
Changes by Terry J. Reedy tjre...@udel.edu: -- versions: +Python 3.4 -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4356 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13990] Benchmarks: 2to3 failures on the py3 side
Brett Cannon added the comment: I can't reproduce the problem anymore. -- resolution: - out of date status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13990 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15935] clarify argparse docs re: add_argument() type and default arguments
New submission from Chris Jerdonek: This issue is to clarify in the documentation the argparse behavior for which tests were added in issue 15906. The behavior involves when the type callable should be applied to default arguments. See, for example, the following comment for what roughly needs to be added: http://bugs.python.org/issue15906#msg170404 I will provide a patch. -- assignee: docs@python components: Documentation keywords: easy messages: 170421 nosy: barry, bethard, cjerdonek, docs@python, r.david.murray priority: normal severity: normal stage: needs patch status: open title: clarify argparse docs re: add_argument() type and default arguments type: behavior versions: Python 2.7, Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15935 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15906] argparse add_argument() confusing behavior when type=str, default=
Chris Jerdonek added the comment: I think that will just leave the doc updates for Chris once my patch lands in all three branches. I created an issue for this here: http://bugs.python.org/issue15935 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10224] Build 3.x documentation using python3.x
Changes by Brett Cannon br...@python.org: -- versions: +Python 3.4 -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10224 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10224] Build 3.x documentation using python3.x
Changes by Chris Jerdonek chris.jerdo...@gmail.com: -- nosy: +cjerdonek ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10224 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15936] Add link from os.urandom to random.SystemRandom
New submission from Jacek Bzdak: It would be great if one sentence was added to os.urandom description: For easy to use interface to system randomness please see random.SystemRandom class. The reason for this change is that many references quote only os.urandom as a cryptographically strong randomeness source in python, and for some people it might be not obvious that there already exists such easy to use api to use cryptographically strong randomness (that is random.SystemRandom class). It would be good to point such people to right class. Myself for example spent last hour trying to create makeshift Random subclass that uses os.urandom as it's randomness source. -- assignee: docs@python components: Documentation messages: 170423 nosy: Jacek.Bzdak, docs@python priority: normal severity: normal status: open title: Add link from os.urandom to random.SystemRandom type: enhancement versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15936 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15935] clarify argparse docs re: add_argument() type and default arguments
Chris Jerdonek added the comment: Attaching patch. -- keywords: +patch Added file: http://bugs.python.org/file27182/issue-15935-1.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15935 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15437] Merge Doc/ACKS.txt names into Misc/ACKS
Chris Jerdonek added the comment: Just an FYI that Ezio asked Georg about this issue on IRC yesterday or the day before, and Georg said +1. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15437 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15927] csv.reader() does not support escaped newline when quoting=csv.QUOTE_NONE
Changes by Chris Jerdonek chris.jerdo...@gmail.com: -- components: +Library (Lib) -None title: cvs.reader does not support escaped newline when quoting=cvs.QUOTE_NONE - csv.reader() does not support escaped newline when quoting=csv.QUOTE_NONE ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15927 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15924] 404 link on Python about page
Chris Jerdonek added the comment: Thanks for the report. However, for this issue, you should e-mail webmas...@python.org instead, as this page describes: http://www.python.org/about/website/ The part of the Python web site affected by this issue is maintained separately from the parts of the web site about the Python language, which is what this bug tracker is for. -- nosy: +cjerdonek resolution: - invalid ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15924 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15924] 404 link on Python about page
Changes by Chris Jerdonek chris.jerdo...@gmail.com: -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15924 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15924] 404 link on Python about page
Ned Deily added the comment: The link has since been fixed thanks to your suggestion. -- components: +Tests -None nosy: +ned.deily ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15924 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15924] 404 link on Python about page
Changes by Berker Peksag berker.pek...@gmail.com: -- components: +None -Tests ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15924 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
