Since AGW is constantly getting updated (thanks Andrea), I’m wondering how wxPython-users stay on top of things. In the past, I’ve removed the default agw directory and replaced with with a checkout of the AGW SVN repo. That more or less works but becomes less manageable as the number of wxPython installations grow. Since it’s a nested package, I can’t simply relocate it without causing issues. If you’re someone that likes to keep AGW up-to-date, how do you manage it?
I use the same but only have a few wxPython installations on my machine and others using my application will get it as a py2exe'd version.
Werner
···
On 21/09/2012 01:54, Mears wrote:
Since AGW is constantly getting updated (thanks Andrea), I'm wondering how wxPython-users stay on top of things. In the past, I've removed the default agw directory and replaced with with a checkout of the AGW SVN repo. That more or less works but becomes less manageable as the number of wxPython installations grow. Since it's a nested package, I can't simply relocate it without causing issues. If you're someone that likes to keep AGW up-to-date, how do you manage it?
Since AGW is constantly getting updated (thanks Andrea), I’m wondering how wxPython-users stay on top of things. In the past, I’ve removed the default agw directory and replaced with with a checkout of the AGW SVN repo.
I’d do something similar, but rather than overwriting the wx-supplied age, I’d put it somewhere else, and change my import lines. In other words, pretend that agw is simply a third party package that does not ship with wx.
Chris
···
On Sep 20, 2012, at 4:54 PM, Mears joshuadavidson@gmail.com wrote:
That more or less works but becomes less manageable as the number of wxPython installations grow. Since it’s a nested package, I can’t simply relocate it without causing issues. If you’re someone that likes to keep AGW up-to-date, how do you manage it?
–
To unsubscribe, send email to wxPython-users+unsubscribe@googlegroups.com
or visit http://groups.google.com/group/wxPython-users?hl=en
The problem with this is AGW doesn’t use relative imports and imports itself from wx.lib.agw. e.g. aui/init.py: import wx.lib.agw.aui as aui
···
On Friday, September 21, 2012 9:10:56 AM UTC-6, Chris Barker wrote:
On Sep 20, 2012, at 4:54 PM, Mears joshuad...@gmail.com wrote:
Since AGW is constantly getting updated (thanks Andrea), I’m wondering how wxPython-users stay on top of things. In the past, I’ve removed the default agw directory and replaced with with a checkout of the AGW SVN repo.
I’d do something similar, but rather than overwriting the wx-supplied age, I’d put it somewhere else, and change my import lines. In other words, pretend that agw is simply a third party package that does not ship with wx.
Chris
That more or less works but becomes less manageable as the number of wxPython installations grow. Since it’s a nested package, I can’t simply relocate it without causing issues. If you’re someone that likes to keep AGW up-to-date, how do you manage it?
–
To unsubscribe, send email to wxPython-user...@googlegroups.com
or visit http://groups.google.com/group/wxPython-users?hl=en
How many wxPython installations are you working with? I can’t imagine working with more than 2. I am aiming to release with 2.9.4 but I develop with 2.8.10.1 still since my IDE doesn’t play nice with 2.9.4 yet. I’ve found I need/want to update AGW only now and then, so to keep it “current enough” should take perhaps 5 minutes every few months, if that.
It seems like a non-problem, but maybe I don’t understand how you are doing things.
···
On Thu, Sep 20, 2012 at 7:54 PM, Mears joshuadavidson@gmail.com wrote:
Since AGW is constantly getting updated (thanks Andrea), I’m wondering how wxPython-users stay on top of things. In the past, I’ve removed the default agw directory and replaced with with a checkout of the AGW SVN repo. That more or less works but becomes less manageable as the number of wxPython installations grow.
If you are using the SVN checkout in each pythons Site Packages
directory then all you need to do is to have a single batch/bash script
that calls svn update on each of your installations, e.g. assuming you
already have checked out AVG in installations for python 2.5, 2.6, 2.7 &
2.9 all you need to do is:
svn update c:\Python25\Lib\site-packages\wx-2.8-msw-unicode\wx\lib\agw
svn update c:\Python26\Lib\site-packages\wx-2.8-msw-unicode\wx\lib\agw
svn update c:\Python27\Lib\site-packages\wx-2.8-msw-unicode\wx\lib\agw
svn update c:\Python29\Lib\site-packages\wx-2.8-msw-unicode\wx\lib\agw
Note if you are using tortoise svn then you will need to use:
TortoiseProc.exe /command:update
/path:"c:\Python25\Lib\site-packages\wx-2.8-msw-unicode\wx\lib\agw", etc.
Putting something like the above in a .bat file, (windows), or bash
script, (Linux or Mac?), should allow you to update all your
installations periodically with a single command.
Gadget/Steve
···
On 21/09/2012 12:54 AM, Mears wrote:
Since AGW is constantly getting updated (thanks Andrea), I'm wondering
how wxPython-users stay on top of things. In the past, I've removed
the default agw directory and replaced with with a checkout of the AGW
SVN repo. That more or less works but becomes less manageable as the
number of wxPython installations grow. Since it's a nested package, I
can't simply relocate it without causing issues. If you're someone
that likes to keep AGW up-to-date, how do you manage it?
--
To unsubscribe, send email to wxPython-users+unsubscribe@googlegroups.com
or visit http://groups.google.com/group/wxPython-users?hl=en