This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author skrah
Recipients Trundle, alex, asvetlov, barry, bfroehle, chris.jerdonek, daniel.urban, david.villa, dmalcolm, eric.smith, ezio.melotti, gregory.p.smith, jcea, jkloth, larry, mark.dickinson, pitrou, skrah, v+python
Date 2012-12-09.19:20:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1355080851.95.0.338218480753.issue16612@psf.upfronthosting.co.za>
In-reply-to
Content
Here are some things that I'm interested in right now:

   1) From what kind of data structure are signature objects generated?

   2) Is there an easy way to do this manually?

   3) Can at least part of the verboseness go into header files (virtually
      all compilers support "static inline" in header files)?

   4) Why don't approaches work that look simpler on the surface, like
      http://mail.python.org/pipermail/python-dev/2012-December/122934.html ?

   5) Are C contributors in general happy (or at least tolerate) the new
      verboseness?


Sure, we can discuss 1) to 3) here. For recording objections or approaches
that don't work (think FAQ "Why don't you just do X?") a PEP would be nice
to have.


If I'm the only one who is slightly bothered by the aesthetic and readability
aspects, then 5) obviously need not be discussed. Most people, however, will
probably find out about the change only once Python 3.4 is released.
History
Date User Action Args
2012-12-09 19:20:52skrahsetrecipients: + skrah, barry, gregory.p.smith, jcea, mark.dickinson, pitrou, larry, eric.smith, jkloth, ezio.melotti, v+python, alex, Trundle, asvetlov, dmalcolm, daniel.urban, chris.jerdonek, bfroehle, david.villa
2012-12-09 19:20:51skrahsetmessageid: <1355080851.95.0.338218480753.issue16612@psf.upfronthosting.co.za>
2012-12-09 19:20:51skrahlinkissue16612 messages
2012-12-09 19:20:51skrahcreate