[issue20613] Wrong line information in bytecode generated by compiler module

2015-03-10 Thread Arnaud Fontaine
Arnaud Fontaine added the comment: compiler module being deprecated does not mean that it's not used. For example, it is used by RestrictedPython as part of Zope2. As I could not figure out a way to fix this bug properly, I reverted the following commit and have not had any problem so far

[issue21308] PEP 466: backport ssl changes

2014-07-31 Thread Arnaud Fontaine
Arnaud Fontaine added the comment: Would it be possible to also backport the changes to httplib.py to support TLS SNI as many libraries (including setuptools) relies on this module to download files and some servers reject clients not supporting TLS SNI (such as cloud.github.com)? I have

[issue20613] Wrong line information in bytecode generated by compiler module

2014-02-12 Thread Arnaud Fontaine
New submission from Arnaud Fontaine: I know that compiler module is deprecated since 2.6, but I found a regression introduced in version 2.7 by the following cleanup commit (replacing pyassem.py modified in this commit by the one just before does not trigger this bug): http://hg.python.org

[issue12776] argparse: type conversion function should be called only once

2012-03-18 Thread Arnaud Fontaine
Arnaud Fontaine ar...@debian.org added the comment: Could you please apply this patch? It's been 4 months without reply now... -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12776

[issue12776] argparse: type conversion function should be called only once

2012-01-25 Thread Arnaud Fontaine
Arnaud Fontaine ar...@debian.org added the comment: ping? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12776 ___ ___ Python-bugs-list mailing

[issue12776] argparse: type conversion function should be called only once

2011-12-15 Thread Arnaud Fontaine
Arnaud Fontaine ar...@debian.org added the comment: Could you add a test to verify that custom actions are still getting the converted values passed to their __call__? I suspect this may not be happening under the current patch - if that's the case, you may also need to add

[issue12776] argparse: type conversion function should be called only once

2011-12-15 Thread Arnaud Fontaine
Changes by Arnaud Fontaine ar...@debian.org: Added file: http://bugs.python.org/file23972/py2.7-argparse-call-type-function-once-v4.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12776

[issue12776] argparse: type conversion function should be called only once

2011-12-15 Thread Arnaud Fontaine
Changes by Arnaud Fontaine ar...@debian.org: Added file: http://bugs.python.org/file23973/py3k-argparse-call-type-function-once-v4.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12776

[issue12776] argparse: type conversion function should be called only once

2011-11-24 Thread Arnaud Fontaine
Arnaud Fontaine ar...@debian.org added the comment: Does the patch I attached fix your issue? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12776

[issue12776] argparse: type conversion function should be called only once

2011-11-24 Thread Arnaud Fontaine
Arnaud Fontaine ar...@debian.org added the comment: It would definitely help if you could apply the patch for Python 2.7 manually on your local installation (after making a backup of course). You can just download the patch for Python 2.7 then (only the first part of the patch can be applied

[issue12776] argparse: type conversion function should be called only once

2011-11-24 Thread Arnaud Fontaine
Arnaud Fontaine ar...@debian.org added the comment: I have had a look at the issue more closely and my initial patch was not completely right as it didn't work properly with argparse_test.py despite all tests passing. Therefore, I have amended my patch to not check whether action.default

[issue12776] argparse: type conversion function should be called only once

2011-11-24 Thread Arnaud Fontaine
Changes by Arnaud Fontaine ar...@debian.org: Added file: http://bugs.python.org/file23775/py2.7-argparse-call-type-function-once-v3.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12776

[issue12776] argparse: type conversion function should be called only once

2011-11-24 Thread Arnaud Fontaine
Changes by Arnaud Fontaine ar...@debian.org: Added file: http://bugs.python.org/file23776/py3k-argparse-call-type-function-once-v3.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12776

[issue12776] argparse: type conversion function should be called only once

2011-11-24 Thread Arnaud Fontaine
Arnaud Fontaine ar...@debian.org added the comment: BTW, about argparse_test, the default should be either '0' or 0 but not '\t' AFAIK because even the default value is converted using the given type function. It fails even with the last 2.7 version but it works well with my patch

[issue12776] argparse: type conversion function should be called only once

2011-09-30 Thread Arnaud Fontaine
Arnaud Fontaine ar...@debian.org added the comment: Any news about applying these patches? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12776

[issue12776] argparse: type conversion function should be called only once

2011-08-21 Thread Arnaud Fontaine
Arnaud Fontaine ar...@debian.org added the comment: Thanks for the review. Sorry to send that here instead of the review page, but I get an error when replying: Invalid XSRF token.. This looks good, especially if all existing tests still pass as you report, but I wonder about one thing

[issue12776] argparse: type conversion function should be called only once

2011-08-21 Thread Arnaud Fontaine
Changes by Arnaud Fontaine ar...@debian.org: Removed file: http://bugs.python.org/file22927/py2.7-argparse-call-type-function-once.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12776

[issue12776] argparse: type conversion function should be called only once

2011-08-21 Thread Arnaud Fontaine
Changes by Arnaud Fontaine ar...@debian.org: Removed file: http://bugs.python.org/file22928/py3k-argparse-call-type-function-once.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12776

[issue12776] argparse: type conversion function should be called only once

2011-08-21 Thread Arnaud Fontaine
Changes by Arnaud Fontaine ar...@debian.org: Added file: http://bugs.python.org/file22978/py2.7-argparse-call-type-function-once.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12776

[issue12776] argparse: type conversion function should be called only once

2011-08-21 Thread Arnaud Fontaine
Changes by Arnaud Fontaine ar...@debian.org: Added file: http://bugs.python.org/file22979/py3k-argparse-call-type-function-once.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12776

[issue12776] argparse: type conversion function should be called only once

2011-08-18 Thread Arnaud Fontaine
New submission from Arnaud Fontaine ar...@debian.org: When specifying a function to be called in type keyword argument of add_argument(), the function is actually called twice (when a default value is set and then when the argument is given). While this may not be a problem in most cases

[issue12776] argparse: type conversion function should be called only once

2011-08-18 Thread Arnaud Fontaine
Changes by Arnaud Fontaine ar...@debian.org: -- keywords: +patch Added file: http://bugs.python.org/file22927/py2.7-argparse-call-type-function-once.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12776

[issue12776] argparse: type conversion function should be called only once

2011-08-18 Thread Arnaud Fontaine
Changes by Arnaud Fontaine ar...@debian.org: Added file: http://bugs.python.org/file22928/py3k-argparse-call-type-function-once.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12776

[issue8269] Missing return values for PyUnicode C/API functions

2010-03-31 Thread Arnaud Fontaine
Arnaud Fontaine ar...@debian.org added the comment: I meant whether it returns a new reference or not. For instance, documentation for PyUnicode_FromObject() and PyUnicode_AsWideChar() states that a new reference is returned, but this is most specified for most functions in Unicode Object

[issue8269] Missing return values for PyUnicode C/API functions

2010-03-31 Thread Arnaud Fontaine
Arnaud Fontaine ar...@debian.org added the comment: I meant whether it returns a new reference or not. For instance, documentation for PyUnicode_FromObject() and PyUnicode_AsWideChar() states that a new reference is returned, but this is not specified for most functions in Unicode Object

[issue8269] Missing return values for PyUnicode C/API functions

2010-03-30 Thread Arnaud Fontaine
New submission from Arnaud Fontaine ar...@debian.org: For example, PyUnicode_FromFormat() does not specify the return value but it does not seem to be only one. I only have a basic knowledge of Python C/API, so I am not sure whether it is meaningful. -- assignee: georg.brandl