Yeah, I think the complexity comes from the fact that I tried to re-implement
the legacy api using the new functionality. There is a bit of mapping going
on. It would probably look simpler to jump with both feet to using the new
api, but then the changes would be less localized, and I am not certain how
well supported it is in various pythons older than 3.3.
Steven
From: Thomas Kluyver [mailto:tak...@gmail.com]
Sent: Wednesday, October 15, 2014 7:04 PM
To: primary discussion list for use and development of cx_Freeze
Subject: Re: [cx-freeze-users] PEP 420: Implicit Namespace Packages
On 7 October 2014 18:15, Steven Velez
<steven.ve...@autodesk.com<mailto:steven.ve...@autodesk.com>> wrote:
I also renamed the repo to make it look like my main cx_Freeze fork.
The new url is
https://bitbucket.org/svelez/cx_freeze/commits/fb6fcf799703d9aba50d061f6943b8b5cedf5fec
Ah, I see, no problem. I've just had a glance at the code, and my first
impression is that it seems to add quite a bit of complex code that we really
shouldn't need. I don't know much about importlib and namespace packages, but
there must be a better way than that to find modules.
Thomas
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
cx-freeze-users mailing list
cx-freeze-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cx-freeze-users
