Has anyone experienced any problems with py2exe with the new wxPython
2.9.1.1 on XP SP3.
I am getting a strange traceback error when I try and run the
executable.
File "wx\__init__.pyo", line 45, in <module>
File "wx\_core.pyo", line 125, in <module>
AttributeError: 'module' object has no attribute 'PROCESS_ENTER'
It works perfectly with wxPython 2.8
I am having trouble isolating the problem and I’m not sure if it’s
some of my other win32 module imports causing this new problem.
Does it run properly without py2exe? Is it possible that your build or dist folder still has files from an old build that are not getting overwritten for new builds?
On 1/21/11 7:19 AM, lorne wrote:
Has anyone experienced any problems with py2exe with the new wxPython
2.9.1.1 on XP SP3.I am getting a strange traceback error when I try and run the
executable.File "wx\__init__.pyo", line 45, in<module>
File "wx\_core.pyo", line 125, in<module>
AttributeError: 'module' object has no attribute 'PROCESS_ENTER'It works perfectly with wxPython 2.8
I am having trouble isolating the problem and I�m not sure if it�s
some of my other win32 module imports causing this new problem.
--
Robin Dunn
Software Craftsman
It does run properly without py2exe build and I have a clean dist.
That is what is so wierd about it. I just tried a very plain wxPython
and the py2exe build worked.
It looks like I need to isolate some of my other modules which must be
conflicting in some way.
On Jan 21, 12:26 pm, Robin Dunn <ro...@alldunn.com> wrote:
On 1/21/11 7:19 AM, lorne wrote:
> Has anyone experienced any problems with py2exe with the new wxPython
> 2.9.1.1 on XP SP3.> I am getting a strange traceback error when I try and run the
> executable.> File "wx\__init__.pyo", line 45, in<module>
> File "wx\_core.pyo", line 125, in<module>
> AttributeError: 'module' object has no attribute 'PROCESS_ENTER'> It works perfectly with wxPython 2.8
> I am having trouble isolating the problem and I m not sure if it s
> some of my other win32 module imports causing this new problem.Does it run properly without py2exe? Is it possible that your build or
dist folder still has files from an old build that are not getting
overwritten for new builds?--
Robin Dunn
Software Craftsmanhttp://wxPython.org
It kind of sounds like something is getting into py2exe that is shadowing a wx class or method. I don’t see how that could happen though.
On Fri, Jan 21, 2011 at 1:58 PM, Lorne White lorne.white@telusplanet.net wrote:
It does run properly without py2exe build and I have a clean dist.
That is what is so wierd about it. I just tried a very plain wxPython
and the py2exe build worked.
It looks like I need to isolate some of my other modules which must be
conflicting in some way.
On Jan 21, 12:26 pm, Robin Dunn ro...@alldunn.com wrote:
On 1/21/11 7:19 AM, lorne wrote:
Has anyone experienced any problems with py2exe with the new wxPython
2.9.1.1 on XP SP3.
I am getting a strange traceback error when I try and run the
executable.
File “wx_init_.pyo”, line 45, in
File “wx_core.pyo”, line 125, in
AttributeError: ‘module’ object has no attribute ‘PROCESS_ENTER’
It works perfectly with wxPython 2.8
I am having trouble isolating the problem and I m not sure if it s
some of my other win32 module imports causing this new problem.
Does it run properly without py2exe? Is it possible that your build or
dist folder still has files from an old build that are not getting
overwritten for new builds?
–
Robin Dunn
Software Craftsmanhttp://wxPython.org
–
To unsubscribe, send email to wxPython-users+unsubscribe@googlegroups.com
or visit http://groups.google.com/group/wxPython-users?hl=en
Mike Driscoll
I found some old frame styles I was using which has shifted the
Attribute error to new one.
It is strange it doesn't show up with a normal python console launch.
Just py2exe builds.
I'm still digging around looking for the remaining ones.
It's something to keep in mind for anyone migrating from their older
code. Thanks for your assistance.
On Jan 21, 1:26 pm, Mike Driscoll <m...@pythonlibrary.org> wrote:
On Fri, Jan 21, 2011 at 1:58 PM, Lorne White <lorne.wh...@telusplanet.net>wrote:
> It does run properly without py2exe build and I have a clean dist.
> That is what is so wierd about it. I just tried a very plain wxPython
> and the py2exe build worked.> It looks like I need to isolate some of my other modules which must be
> conflicting in some way.> On Jan 21, 12:26 pm, Robin Dunn <ro...@alldunn.com> wrote:
> > On 1/21/11 7:19 AM, lorne wrote:> > > Has anyone experienced any problems with py2exe with the new wxPython
> > > 2.9.1.1 on XP SP3.> > > I am getting a strange traceback error when I try and run the
> > > executable.> > > File "wx\__init__.pyo", line 45, in<module>
> > > File "wx\_core.pyo", line 125, in<module>
> > > AttributeError: 'module' object has no attribute 'PROCESS_ENTER'> > > It works perfectly with wxPython 2.8
> > > I am having trouble isolating the problem and I m not sure if it s
> > > some of my other win32 module imports causing this new problem.> > Does it run properly without py2exe? Is it possible that your build or
> > dist folder still has files from an old build that are not getting
> > overwritten for new builds?> > --
> > Robin Dunn
> > Software Craftsmanhttp://wxPython.org> --
> To unsubscribe, send email to wxPython-users+unsubscribe@googlegroups.com<wxPython-users%2Bunsubscribe@googlegroups.com>
> or visithttp://groups.google.com/group/wxPython-users?hl=enIt kind of sounds like something is getting into py2exe that is shadowing a
wx class or method. I don't see how that could happen though.--
-----------------
Mike DriscollBlog: http://blog.pythonlibrary.org- Hide quoted text -
- Show quoted text -
Ah-ha. Somehow I completely missed that you're using the new wx. I
don't use that yet. Hopefully Robin will know more.
On Jan 21, 4:08 pm, Lorne White <lorne.wh...@telusplanet.net> wrote:
I found some old frame styles I was using which has shifted the
Attribute error to new one.It is strange it doesn't show up with a normal python console launch.
Just py2exe builds.I'm still digging around looking for the remaining ones.
It's something to keep in mind for anyone migrating from their older
code. Thanks for your assistance.
-------------------
Mike Driscoll