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 ezio.melotti
Recipients Arfrever, asvetlov, danielsh, eli.bendersky, ezio.melotti, flox, ncoghlan, python-dev, serhiy.storchaka, tshepang
Date 2013-02-27.04:08:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1361938132.24.0.162487923955.issue15083@psf.upfronthosting.co.za>
In-reply-to
Content
> The next logical step is to make all test classes in test_xml_etree 
> accept the ET module in some way and store it, using it to get classes 
> & function. I.e. no more global "ET" and "pyET" at all.

The idiom suggested by PEP 399 has the two modules (cmod and pymod) as globals, and then simply sets them as class attributes.  Is there any reason why this should be avoided in this case?
History
Date User Action Args
2013-02-27 04:08:52ezio.melottisetrecipients: + ezio.melotti, ncoghlan, Arfrever, eli.bendersky, asvetlov, flox, tshepang, python-dev, serhiy.storchaka, danielsh
2013-02-27 04:08:52ezio.melottisetmessageid: <1361938132.24.0.162487923955.issue15083@psf.upfronthosting.co.za>
2013-02-27 04:08:52ezio.melottilinkissue15083 messages
2013-02-27 04:08:51ezio.melotticreate