[Dev] removing egenix from the externals tree
Robin Dunn
robin at alldunn.com
Fri Jun 10 08:16:21 PDT 2005
Mike Taylor wrote:
> With the work Andi has done with PyIcu and the subsequent removal of all
> things mx.DateTime, my thought was that we could remove egenix.mx from
> the build.
>
> I ran a quick search of the source (find . -name '*.py' -print | xargs
> grep 'mx.' ) to search for any imports of the mx modules and except for
> mx itself the only hits I saw were in wx. Specifically
> wx/lib/masked/timectrl.py
>
> Will this reference to mx cause grief when I pull egenix.mx from the
> build? I ran a version of Chandler that did not have egenix built into
> it and my running of the various smoke-tests seemed to say it was safe,
> but I figured I would ask before checking in the new external/Makefile
The use of mxDateTime is optional in that module. If it's able to
import mx.DateTime then it enables some additional functionality to be
able to use mx.DateTime objects, but if the module is not found then it
gacefully degrades.
try:
from mx import DateTime
accept_mx = True
except ImportError:
accept_mx = False
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
More information about the Dev
mailing list