[Stackless] Stackless on macos x

[Denis Fourt]

Ok,
Why 2.7.5 instead of 2.7.6? Because I was advised to use the same revision as Python (which I understood as CPython)
Yes, it is a Python problem not a stackless one. But on macos x getting the readline seems not that easy because of the name conflict with the equivalent lib chosen by apple.
Thanks for all the help,
Denis

> Date: Wed, 7 May 2014 12:42:18 +1200
> From: richard.m.tew at gmail.com
> To: stackless at stackless.com
> Subject: Re: [Stackless] Stackless on macos x
> 
> Get the corresponding source code for Python, compile it the same way.
> 
> It should have all the same problems you mention.  The Stackless
> changes are completely unrelated to them.
> 
> Not sure why you are using 2.7.5, there's a 2.7.6 tarball on the web
> site download page.  Or a 2.7.6 slp tag, you could use instead if you
> really wanted to.
> 
> Richard.
> 
> On 5/7/14, Denis Fourt <denis.prog at hotmail.com> wrote:
> > So I update to 2.7.5-slp. Here are my results (with clang):
> > make complains about :
> > Python build finished, but the necessary bits to build these modules were
> > not found:_bsddb             dl                 gdbm            imageop
> >       linuxaudiodev      ossaudiodev     readline           spwd
> >   sunaudiodev     To find the necessary bits, look in setup.py in
> > detect_modules() for the module's name.
> >  Some look unrelated to macos, but the readline would be nice to have. There
> > was an option but the readme says it is deprecated. Any other important
> > missed module here?
> > Framework installation failed at the end (on a local directory, no sudo
> > problem here) regular installation succeeded.
> > Regards,
> > Denis
> > From: denis.prog at hotmail.com
> > To: stackless at stackless.com
> > Date: Tue, 6 May 2014 10:58:49 -0400
> > Subject: Re: [Stackless] Stackless on macos x
> >
> >
> >
> >
> > Thanks for the information.
> > Here is a short list of what I have found confusing :
> > a) on http://www.stackless.com/wiki/Mercurial :It is not clear if the
> > version numbers are not up to date or if it is the right revisions for that
> > versions. In my opinion it should be clear how to choose the latest stable
> > releases.
> > b) choosing the right revision number seems impossible : so many available
> > when browsing the sources (for example what means default? where is 2.7.6?)
> > and then I tried to infer from the precompiled and in some cases I failed
> > (2.7.6.r3, 3.1.3-slp, if I remember well).
> > c) on http://www.stackless.com/wiki/Download the version numbers of the
> > precompiled do not always match the already installed CPython 2.7.6 for os
> > 10.9 when it is actually 2.7.5.
> > Hope this help,
> > Denis
> >> Date: Tue, 6 May 2014 17:11:38 +1200
> >> From: richard.m.tew at gmail.com
> >> To: stackless at stackless.com
> >> Subject: Re: [Stackless] Stackless on macos x
> >>
> >> Denis,
> >>
> >> Despite what the website says, Stackless can be as simple as you want
> >> to make it.
> >>
> >> Use the same compiler that is used by Python.  Use the same revision
> >> tags as Python but with the added 'slp'.
> >>
> >> If you find the website confusing please point out where it is
> >> confusing and ideally the particular words you find confusing on it.
> >>
> >> Cheers,
> >> Richard.
> >>
> >> On 5/6/14, Denis Fourt <denis.prog at hotmail.com> wrote:
> >> > Hi,
> >> > I would like to try stackless. I am using macos 10.9 presently (in case
> >> > of
> >> > trouble I can still use 10.6). There is no ready to use installer that
> >> > match
> >> > the version of the already installed (by apple) python, so I do not
> >> > think
> >> > this is the best way (even if the versions had matched I would have
> >> > avoided
> >> > it, CPython does not replace the original, why Stackless should?)
> >> > I can download the sources or clone the repository, but :I do not know
> >> > which
> >> > revision/branch/tag to use (the information on the web site looks a bit
> >> > out
> >> > dated)I do not know which compiler to use : clang or the old gcc4.2if
> >> > the
> >> > compiler choice has an impact later when installing packages.
> >> > An alternative would be to use PyPy : for what reasons should I prefer
> >> > Stackless (not taking into account the fact that some Python packages
> >> > like
> >> > numpy do not work with PyPy)?
> >> > Thanks for the help,
> >> > Denis
> >>
> >> _______________________________________________
> >> Stackless mailing list
> >> Stackless at stackless.com
> >> http://www.stackless.com/mailman/listinfo/stackless
> >  		 	   		
> >
> > _______________________________________________
> > Stackless mailing list
> > Stackless at stackless.com
> > http://www.stackless.com/mailman/listinfo/stackless
> 
> _______________________________________________
> Stackless mailing list
> Stackless at stackless.com
> http://www.stackless.com/mailman/listinfo/stackless
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.stackless.com/pipermail/stackless/attachments/20140507/0526cc9d/attachment.html>