[Python-Dev] PEP or formal description of Python module structure
Hi, I am trying to figure out what Python module is internally (WIP http://wiki.python.org/moin/techtonik)? Is there already a good piece of documentation that I missed that can answer all these questions already? ...what properties do you get in empty Python module (__doc__, __name__, ...)? ...what of those properties are set by the language standard (required) and what are just optional helpers from/for the interpreter? ...what is the proper way to inspect modules and access their properties at runtime? ...what optional properties are defined by language standard that can you set implicitly? ...how each internal property is used by the interpreter and when it appeared? ...what is the proper way to create module namespace at run-time? I'd like to see some kind of reference of properties with classification required/optional, purpose, when set, who uses, how to approach etc. in one place. -- anatoly t. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] urlretrieve regression in Python 3
Can anybody raise the priority of this issue to make it visible during the next bug hunting day? http://bugs.python.org/issue10836 ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP or formal description of Python module structure
Le 15/10/2012 09:43, anatoly techtonik a écrit : Hi, I am trying to figure out what Python module is internally (WIP http://wiki.python.org/moin/techtonik)? Is there already a good piece of documentation that I missed that can answer all these questions already? ...what properties do you get in empty Python module (__doc__, __name__, ...)? ...what of those properties are set by the language standard (required) and what are just optional helpers from/for the interpreter? ...what is the proper way to inspect modules and access their properties at runtime? ...what optional properties are defined by language standard that can you set implicitly? ...how each internal property is used by the interpreter and when it appeared? ...what is the proper way to create module namespace at run-time? I'd like to see some kind of reference of properties with classification required/optional, purpose, when set, who uses, how to approach etc. in one place. -- anatoly t. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/xavier.combelle%40free.fr from http://docs.python.org/reference/datamodel.html Modules Modules are imported by the import http://docs.python.org/reference/simple_stmts.html#import statement (see section /The import statement/ http://docs.python.org/reference/simple_stmts.html#import). A module object has a namespace implemented by a dictionary object (this is the dictionary referenced by the func_globals attribute of functions defined in the module). Attribute references are translated to lookups in this dictionary, e.g., m.x is equivalent to m.__dict__[x]. A module object does not contain the code object used to initialize the module (since it isn't needed once the initialization is done). Attribute assignment updates the module's namespace dictionary, e.g., m.x = 1 is equivalent to m.__dict__[x] = 1. Special read-only attribute: __dict__ is the module's namespace as a dictionary object. *CPython implementation detail:* Because of the way CPython clears module dictionaries, the module dictionary will be cleared when the module falls out of scope even if the dictionary still has live references. To avoid this, copy the dictionary or keep the module around while using its dictionary directly. Predefined (writable) attributes: __name__ is the module's name; __doc__ is the module's documentation string, or None if unavailable; __file__ is the pathname of the file from which the module was loaded, if it was loaded from a file. The __file__ attribute is not present for C modules that are statically linked into the interpreter; for extension modules loaded dynamically from a shared library, it is the pathname of the shared library file. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] AUTO: Jon K Peck is out of the office
I am out of the office until 10/16/2012. I will be out of the office Monday 10/15/12. I will not have email access during this time. Note: This is an automated response to your message Python-Dev Digest, Vol 111, Issue 31 sent on 10/15/2012 4:00:04. This is the only notification you will receive while this person is away.___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] AUTO: Jon K Peck is out of the office
On Mon, Oct 15, 2012 at 11:04 AM, Jon K Peck p...@us.ibm.com wrote: I am out of the office until 10/16/2012. I will be out of the office Monday 10/15/12. I will not have email access during this time. Note: This is an automated response to your message Python-Dev Digest, Vol 111, Issue 31 sent on 10/15/2012 4:00:04. This is the only notification you will receive while this person is away. Enjoy your day off, John K Peck. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] AUTO: Jon K Peck is out of the office
On Oct 15, 2012, at 11:40 AM, Brian Curtin wrote: On Mon, Oct 15, 2012 at 11:04 AM, Jon K Peck p...@us.ibm.com wrote: I am out of the office until 10/16/2012. I will be out of the office Monday 10/15/12. I will not have email access during this time. Note: This is an automated response to your message Python-Dev Digest, Vol 111, Issue 31 sent on 10/15/2012 4:00:04. This is the only notification you will receive while this person is away. Enjoy your day off, John K Peck. Indeed. And when you get back, please fix your vacation program. :) -Barry ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-checkins] cpython (2.7): don't expect warnings from doctests if they can't run
On Mon, Oct 15, 2012 at 5:38 PM, benjamin.peterson python-check...@python.org wrote: http://hg.python.org/cpython/rev/d39f4a92d823 changeset: 79725:d39f4a92d823 branch: 2.7 user:Benjamin Peterson benja...@python.org date:Mon Oct 15 20:38:21 2012 -0400 summary: don't expect warnings from doctests if they can't run -(class Tester is deprecated, DeprecationWarning)] +depcreations.append((class Tester is deprecated, DeprecationWarning)) There is a typo here. --Chris ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Bumping autoconf from 2.68 to 2.69
Any objections to regenerating configure with autoconf 2.69? The current version is based off 2.68, which was release on the 22nd of September 2010. 2.69 was released on the 24th of April, 2012. (There are some fixes for the more esoteric UNIX platforms that Snakebite will benefit from. Also, I struggled to find a box with 2.68 even installed when I needed to regenerate configure this weekend; it seems all package management/ports have bumped to 2.69.) If there are no objections, can it be applied across the board? 2.7, 3.2, 3.3 and 3.x? Trent. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
