[Pythonmac-SIG] Re: [wxPython-mac] More feedback questions

[Kevin Ollivier]

Hi Robin,

For #1, my vote is to just do wxPythonMacOSX for the Mac OS X port, and 
wxPythonMac for Carbon MacPython (I think Stefan's build in Feb. is 
still the current one for this platform). Then just add a note for the 
OS X port that it requires MachoPython.

A thought I had (Jack, I hope you're listening =), what do you guys 
think about changing the name for "MachoPython" to MacPythonX while 
MacPython undergoes the Carbon -> OS X only transition? I think the name 
makes it clearer that it's OS X only, and its probably a bit easier to 
remember as well for those not compiling Mac software. =) Also, is the 
wxPython  Sourceforge site the only place MachoPython is available for 
download?

For #2 and #3, both work for me!

Thanks,

Kevin

On Friday, July 19, 2002, at 09:54  PM, Robin Dunn wrote:

> Hi again.
>
> While thinking about the upcoming 2.3.3 release I have come up with some
> more things that I would like to get feedback from the community on.
>
> 1. Package/Installer naming:  I'm going to standardize a bit and change 
> the
> names of the installers and packages (as in RPMs and .dmg's, *not* 
> Python
> packages) and use the name of the wx port in the name.  For example:
> wxPythonMSW, wxPythonGTK, etc. Hopefully someday there will be a
> wxPythonX11...  I'm not sure though what to do about the Mac OSX 
> version.
> There are in effect several wx ports that run on the Mac, Classic, 
> Carbon,
> and an OSX-only version built using the Apple Developer Tools.  
> Currently
> wxPython only works with the latter one.  So should it be wxPythonMac,
> wxPythonOSX, wxPythonMacOSX, wxPythonMacho, or ???
>
> 2. Python versions:  I plan on doing binary builds for both Python 2.1 
> and
> 2.2, (except on the Mac where it will only be 2.2.)  Is this enough?  If
> not, why not?
>
> 3. Compile options:  I'm thinking about dropping the -hybrid builds (and
> also the -dbg RPM I just announced) and instead do a single build that 
> is
> something in between the FINAL and HYBRID that I've done in the past.
> Specifically it will be like the FINAL in that compiler optimizations 
> will
> be turned on and debugging info won't be generated, but __WXDEBUG__ 
> will be
> turned on so that the various runtime checks will always be there.  As 
> it is
> now it takes me a complete a day to do all the builds and to do test
> installs, much longer if I have to make changes to installers, etc.  I'd
> like to chop that in half if possible.
>
> That's all for now.
>
> --
> Robin Dunn
> Software Craftsman
> http://wxPython.org  Java give you jitters?  Relax with wxPython!
>
>
>
>
>
> _______________________________________________
> wxPython-mac mailing list
> wxPython-mac@lists.wxwindows.org
> http://lists.wxwindows.org/mailman/listinfo/wxpython-mac
>