[issue20293] pydoc fails with the "unspecified" default value

2014-01-26 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Since Argument Clinic no more supports "unspecified" default value, this issue can be closed. -- resolution: -> out of date stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue20293] pydoc fails with the "unspecified" default value

2014-01-23 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- nosy: +yselivanov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue20293] pydoc fails with the "unspecified" default value

2014-01-22 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Without the "= unspecified" parameters will be non-optional. -- ___ Python tracker ___ ___ Python

[issue20293] pydoc fails with the "unspecified" default value

2014-01-22 Thread Larry Hastings
Larry Hastings added the comment: > This is because in pure Python functions we have no enough > information. I believe than origin expression is more useful > in the help. That doesn't matter. inspect.Signature would have to change in order to provide the original expression, and it's not go

[issue20293] pydoc fails with the "unspecified" default value

2014-01-22 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: > Yes, that is how it must work. This is symmetric with pure Python functions: This is because in pure Python functions we have no enough information. I believe than origin expression is more useful in the help. Compare: >>> import re, inspect >>> p = re.c

[issue20293] pydoc fails with the "unspecified" default value

2014-01-22 Thread Larry Hastings
Larry Hastings added the comment: I missed the detail that you were working with a patch applied. I suspect the problem is, you misspelled one of the expressions you provided as a default value. Try str(inspect.signature(x)) on every function you converted. I bet one of them will throw an ex

[issue20293] pydoc fails with the "unspecified" default value

2014-01-22 Thread Larry Hastings
Larry Hastings added the comment: Yes, that is how it must work. This is symmetric with pure Python functions: >>> import inspect >>> import zlib >>> def foo(a=zlib.Z_DEFAULT_COMPRESSION): pass ... >>> str(inspect.signature(foo)) '(a=-1)' -- __

[issue20293] pydoc fails with the "unspecified" default value

2014-01-22 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Seems this is related issue: >>> import zlib, inspect >>> zlib.compressobj.__text_signature__ '(level=Z_DEFAULT_COMPRESSION, method=DEFLATED, wbits=MAX_WBITS, memLevel=DEF_MEM_LEVEL, strategy=Z_DEFAULT_STRATEGY, zdict=None)' >>> str(inspect.signature(zlib.com

[issue20293] pydoc fails with the "unspecified" default value

2014-01-19 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: I just built from a new clone of trunk (last revision is d0e2437136f5), and I still get the error. -- resolution: works for me -> stage: committed/rejected -> status: closed -> open ___ Python tracker

[issue20293] pydoc fails with the "unspecified" default value

2014-01-19 Thread Larry Hastings
Larry Hastings added the comment: Closing. Reopen it if you get a reproducible test case with a fresh checkout of trunk. -- resolution: -> works for me stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue20293] pydoc fails with the "unspecified" default value

2014-01-18 Thread Berker Peksag
Berker Peksag added the comment: > I just built from a new clone of trunk, and it works fine for me. It works fine for me, too (revision 8f11493cf727). -- nosy: +berker.peksag ___ Python tracker __

[issue20293] pydoc fails with the "unspecified" default value

2014-01-18 Thread Larry Hastings
Larry Hastings added the comment: I just built from a new clone of trunk, and it works fine for me. I didn't see the exception you report--I get the documentation for zlib. Do you still get the error if you build from a new clone of the current trunk? -- _

[issue20293] pydoc fails with the "unspecified" default value

2014-01-18 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: That happens with current trunk (revision 1469c4fde8cd) and a patch for zlib from issue20193 [1]. [1] http://bugs.python.org/file33523/zlib_clinic.patch -- ___ Python tracker _

[issue20293] pydoc fails with the "unspecified" default value

2014-01-18 Thread Larry Hastings
Larry Hastings added the comment: Just checking--that happens with current trunk? Revision 32f9e0ae23f7 or newer? -- ___ Python tracker ___ _

[issue20293] pydoc fails with the "unspecified" default value

2014-01-18 Thread Serhiy Storchaka
New submission from Serhiy Storchaka: With patch for the zlib module (issue20193) which uses the "unspecified" default value: $ ./python -m pydoc zlib Traceback (most recent call last): File "/home/serhiy/py/cpython/Lib/inspect.py", line 1997, in wrap_value value = eval(s, module_dict)