[Python-Dev] python-dev Summary for 2004-11-16 through 2004-11-30 [draft] (original) (raw)

Brett C. bac at OCF.Berkeley.EDU
Sat Jan 1 04:11:43 CET 2005


With school starting up again Monday and New Years being tomorrow I don't plan to send this out until Tuesday.

Hope everyone has a good New Years.

-Brett


===================== Summary Announcements

PyCon_ is coming up! Being held March 23-25 in Washington, DC, registration is now open at http://www.python.org/pycon/2005/register.html for credit card users (you can pay by check as well; see the general info page for the conference).

.. _PyCon: http://www.python.org/pycon/2005/

========= Summaries


Would you like the source with your function?

Would you like all functions and classes to contain a pycode attribute that contains a string of the code used to compile that code object? Well, that very idea was proposed. You would use a command-line switch to turn on the feature in order to remove the memory and any performance overhead for the default case of not needing this feature.

Some might ask why this is needed when inspect.getsource and its ilk exist. The perk is that pycode would always exist while inspect.getsource is a best attempt but cannot guarantee it will have the source.

Beyond a suggested name change to source, various people have suggested very different uses. Some see it as a convenient way to save interpreter work easily and thus not lose any nice code snippet developed interactively. Others see a more programmatic use (such as AOP "advice" injection). Both are rather different and led to the thread ending on the suggestion that a PEP be written that specifies what the intended use-case to make sure that need is properly met.

Contributing threads:

=============== Skipped Threads

strings is not significant to the parser

ASCII on your own



More information about the Python-Dev mailing list