Test build on the way

Hi all,

There is a new preview being uploaded as I write this, so stay tuned for the R'bot announcement.

Since I didn't quite get everything worked out with eggs yet, this still uses the old package structures, instead of having a runtime-only and a full-package like we discussed before.

I did make some changes in the OS X install however. Now the same wxPython install should be usable from either the system Python or a MacPython install on Leopard. I did this by relocating the Python package dir out of the main site-packages dir for one of the Python's and put it under /usr/local/lib instead. Then I install a .pth file into both of the Pythons that points to this other location. I would appreciate it if you can test this and make sure there are not any problems with doing it this way that I haven't seen yet.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Robin Dunn wrote:

I did make some changes in the OS X install however. Now the same wxPython install should be usable from either the system Python or a MacPython install on Leopard. I did this by relocating the Python package dir out of the main site-packages dir for one of the Python's and put it under /usr/local/lib instead. Then I install a .pth file into both of the Pythons that points to this other location. I would appreciate it if you can test this and make sure there are not any problems with doing it this way that I haven't seen yet.

Did anybody take a look at this in the last test build? Any problems or concerns with it? Any suggestions for an alternate approach?

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Hi Robin,

Robin Dunn wrote:

I did make some changes in the OS X install however. Now the same wxPython install should be usable from either the system Python or a MacPython install on Leopard. I did this by relocating the Python package dir out of the main site-packages dir for one of the Python's and put it under /usr/local/lib instead. Then I install a .pth file into both of the Pythons that points to this other location. I would appreciate it if you can test this and make sure there are not any problems with doing it this way that I haven't seen yet.

Did anybody take a look at this in the last test build? Any problems or concerns with it? Any suggestions for an alternate approach?

I installed it and it worked fine for me, though I didn't really switch around environments or anything.

Thanks,

Kevin

···

On May 9, 2008, at 8:42 PM, Robin Dunn wrote:

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

_______________________________________________
wxpython-dev mailing list
wxpython-dev@lists.wxwidgets.org
http://lists.wxwidgets.org/mailman/listinfo/wxpython-dev

If I may ask...there has been a 2 month period between the test
release and now. I was curious if this is due to you waiting for the
(somewhat interminably) immanent wxWidgets 3.0 release?

There are some features in the test release that interest me, but I am
not allowed to use them until an official "release" version is
available.

Any hint or hope at when the new release is going to happen?

Thanks,
Chris.

···

On Fri, 09 May 2008 20:42:19 -0700, Robin Dunn <robin@alldunn.com> wrote:

Robin Dunn wrote:

I did make some changes in the OS X install however. Now the same
wxPython install should be usable from either the system Python or a
MacPython install on Leopard. I did this by relocating the Python
package dir out of the main site-packages dir for one of the Python's
and put it under /usr/local/lib instead. Then I install a .pth file
into both of the Pythons that points to this other location. I would
appreciate it if you can test this and make sure there are not any
problems with doing it this way that I haven't seen yet.

Did anybody take a look at this in the last test build? Any problems or
concerns with it? Any suggestions for an alternate approach?

Chris Spencer wrote:

If I may ask...there has been a 2 month period between the test
release and now. I was curious if this is due to you waiting for the
(somewhat interminably) immanent wxWidgets 3.0 release?

No, just busy with other things.

There are some features in the test release that interest me, but I am
not allowed to use them until an official "release" version is
available.

Any hint or hope at when the new release is going to happen?

I hope to do a new 2.8.x release real soon (a couple weeks at most) as I need it for my own projects. I'll be doing a new preview build within a few days.

If nothing comes up that derails the current plans, a 2.9.0 release from the wxWidgets team should happen within a few months. After a few more 2.9.x releases it will become 3.0. See ReleaseSeries - wxPyWiki for what the numbers mean.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!