[issue6130] There ought to be a way for extension types to associate documentation with their tp_new or tp_init methods

2014-06-27 Thread Ezio Melotti
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti, larry, ncoghlan stage: - needs patch type: - enhancement versions: +Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6130

[issue6130] There ought to be a way for extension types to associate documentation with their tp_new or tp_init methods

2014-02-03 Thread Mark Lawrence
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- nosy: -BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6130 ___ ___

[issue6130] There ought to be a way for extension types to associate documentation with their tp_new or tp_init methods

2010-08-01 Thread Mark Lawrence
Mark Lawrence breamore...@yahoo.co.uk added the comment: Can anyone provide a way forward for this issue? -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6130 ___

[issue6130] There ought to be a way for extension types to associate documentation with their tp_new or tp_init methods

2009-05-27 Thread Jean-Paul Calderone
New submission from Jean-Paul Calderone exar...@divmod.com: If an extension type supplies a tp_new or tp_init, these will be invoked by the normal instantiation logic. They will also be exposed as `__new__´ and `__init__´ attributes of the type. However, there is no way to supply a docstring