I think the "correct" thing to do is whatever the regular Python
team does for OS-X builds (under the implicit Stackless "be as compatible
as possible" principle).

I believe that the build script by default should build a universal version against SDK 10.4u which is compatible with 10.4 to current (and theoretically with 10.3 with all updates -- and theoretically future versions as well as Apple is trying to make 10.4 as forward compatible as possible). It looks like something changed very recently ( http://bugs.python.org/issue6957 ) so there may be some issue with 10.6
which I don't know about.

I assume (but haven't checked) that the DMG on the python.org site
for OS-X is still against 10.4u.

P.S. Much of this will soon be moot for 2.6.3 ... it sounds like 2.6.4 will be out very
soon due to a couple of problems with the 2.6.3 release...


On Oct 6, 2009, at 7:52 AM, Aleksandar Radulovic wrote:

Hi,

I am running 10.6 and 10.5 versions of OS X, so I've installed 10.5
build of Stackless.

Question is, should we support 10.3 and 10.4 versions of OSX with binary builds
or just leave them with option of building it themselves?

I personally think it's ok to provide only the 10.5 binary installer.

-alex.

On Tue, Oct 6, 2009 at 3:27 AM, Richard Tew <richard.m....@gmail.com> wrote:
MacOS users.  What's up with the MacOS version on these installers?
Does it matter? Can I just provide one of them for all versions of
MacOS, are separate versions needed?  Can't you all just move to
Windows? (I kid on that last one)

Cheers,
Richard.


---------- Forwarded message ----------
From: Aleksandar Radulovic <a...@a13x.net>
Date: Tue, Oct 6, 2009 at 10:15 AM
Subject: Re: Stackless Python 2.6.3 for OSX (dmg)
To: Richard Tew <richard.m....@gmail.com>


Hi Richard,

I build 2.6.3 for 10.3, 10.4 and 10.5 - even with default settings
(10.3) it still adds the target
to the name, so it's just a matter of renaming the installer, I guess.

I've put all three on the same location, they only differ in the target name:
http://a13x.net/stackless/stackless-2.6.3-macosx10.3-2009-10-05.dmg
http://a13x.net/stackless/stackless-2.6.3-macosx10.4-2009-10-05.dmg
http://a13x.net/stackless/stackless-2.6.3-macosx10.5-2009-10-05.dmg

Would be best to check with others on the mailing list to see which
target is the
most used one..

I'll build the 3.1.1 tomorrow, I had some problems with it earlier today..

Best regards,
alex.

On Mon, Oct 5, 2009 at 8:31 PM, Aleksandar Radulovic <a...@a13x.net> wrote:
Hi Richard,

I've managed to compile and build the installer using 10.5 as deployment target,
that's probably where the name comes from..

Question is, considering that Snow Leopard came out (10.6) and 10.5 seems to be
on majority of systems, should we support 10.4?

Anyways, I can rebuild the DMG for 10.4, that shouldn't be a problem..
Will let you know..

-alex.

On Mon, Oct 5, 2009 at 7:09 PM, Richard Tew <richard.m....@gmail.com> wrote:
On Tue, Oct 6, 2009 at 12:32 AM, Aleksandar Radulovic <a...@a13x.net > wrote:
Hi, Richard..

I've finished with the build of Stackless for OS X, you can fetch it from here: http://a13x.net/stackless/stackless-2.6.3- macosx10.5-2009-10-05.dmg

I'll let you knwo when I build the 3.1.1..

Regards,
alex.

Hi Alex,

Thanks for this. I see this is named with the MacOS version 10.5, is
that important?  The others are versionless with regard to MacOS in
the file name, and if there is no difference with regard to this, I'd
prefer to have the filenames consistent.

Cheers,
Richard.




--
a lex 13 x
http://www.a13x.info




--
a lex 13 x
http://www.a13x.info

_______________________________________________
Stackless mailing list
Stackless@stackless.com
http://www.stackless.com/mailman/listinfo/stackless




--
a lex 13 x
http://www.a13x.info

_______________________________________________
Stackless mailing list
Stackless@stackless.com
http://www.stackless.com/mailman/listinfo/stackless



_______________________________________________
Stackless mailing list
Stackless@stackless.com
http://www.stackless.com/mailman/listinfo/stackless

Reply via email to