wx package

What would you say to the idea of distributing my wx package with
wxPython? My thinking is this. If we want to post examples of the new
syntax, or convert the demo, or convert PyCrust, we need users to have
the new wx package installed. If wxPython installs it automatically,
they don't have to do a thing. And it won't conflict with existing
code. Sure, it's a tiny bit slower because it's creating the new
namespace dynamically, but it's simple, it works, it's complete, and
it's available now.

Apparently there was a recent discussion among the wxWindows folks and
it looks like their plan is to have one big wx namespace with the wx
prefix dropped. So our new package is a perfect transition.

Thoughts?

···

--
Patrick K. O'Brien
Orbtech http://www.orbtech.com/web/pobrien
-----------------------------------------------
"Your source for Python programming expertise."
-----------------------------------------------

Patrick K. O'Brien wrote:

What would you say to the idea of distributing my wx package with
wxPython? My thinking is this. If we want to post examples of the new
syntax, or convert the demo, or convert PyCrust, we need users to have
the new wx package installed. If wxPython installs it automatically,
they don't have to do a thing. And it won't conflict with existing
code. Sure, it's a tiny bit slower because it's creating the new
namespace dynamically, but it's simple, it works, it's complete, and
it's available now.

Apparently there was a recent discussion among the wxWindows folks and
it looks like their plan is to have one big wx namespace with the wx
prefix dropped. So our new package is a perfect transition.

Thoughts?

My current plan is to discuss it one more time on the -users list and then add it to the release after this one.

···

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

Robin Dunn <robin@alldunn.com> writes:

Patrick K. O'Brien wrote:
> What would you say to the idea of distributing my wx package with
> wxPython? My thinking is this. If we want to post examples of the new
> syntax, or convert the demo, or convert PyCrust, we need users to have
> the new wx package installed. If wxPython installs it automatically,
> they don't have to do a thing. And it won't conflict with existing
> code. Sure, it's a tiny bit slower because it's creating the new
> namespace dynamically, but it's simple, it works, it's complete, and
> it's available now.
> Apparently there was a recent discussion among the wxWindows folks
> and
> it looks like their plan is to have one big wx namespace with the wx
> prefix dropped. So our new package is a perfect transition.
> Thoughts?
>

My current plan is to discuss it one more time on the -users list and
then add it to the release after this one.

Okay, good. (I can't wait to see how much "concern" that stirs up.)

BTW, when your code is going to appear in a book that limits you to a
width of 68 characters you really start to appreciate not having the
wx prefix. :wink:

···

--
Patrick K. O'Brien
Orbtech http://www.orbtech.com/web/pobrien
-----------------------------------------------
"Your source for Python programming expertise."
-----------------------------------------------

Sounds good to me. It provides a means for people to try out the new
method in the 2.4 series without breaking any existing code.

About the question of incrementing the 4th position for each preview
release: it sounds like a good idea to me. In fact, the very fact that
the numbers to the general public will look like this

2.4.0.6
2.4.0.8
2.4.0.12

or something similar will let people know how many releases they didn't
even have to bother installing.... :slight_smile: In other words, it lets people
know that the stability issue is important. My 2 cents... :slight_smile:

···

On Thu, 2003-03-20 at 17:41, Patrick K. O'Brien wrote:

What would you say to the idea of distributing my wx package with
wxPython? My thinking is this. If we want to post examples of the new
syntax, or convert the demo, or convert PyCrust, we need users to have
the new wx package installed. If wxPython installs it automatically,
they don't have to do a thing. And it won't conflict with existing
code. Sure, it's a tiny bit slower because it's creating the new
namespace dynamically, but it's simple, it works, it's complete, and
it's available now.

Apparently there was a recent discussion among the wxWindows folks and
it looks like their plan is to have one big wx namespace with the wx
prefix dropped. So our new package is a perfect transition.

Thoughts?

--
Patrick K. O'Brien
Orbtech http://www.orbtech.com/web/pobrien
-----------------------------------------------
"Your source for Python programming expertise."
-----------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwindows.org

--
Anthony Tuininga
anthony@computronix.com

Computronix
Distinctive Software. Real People.
Suite 200, 10216 - 124 Street NW
Edmonton, AB, Canada T5N 4A3
Phone: (780) 454-3700
Fax: (780) 454-3838