Hi,

besides Richard's announcement below,
there will in fact be a stackless 2.8 with a changed executable name
that explicitly does not call itself "python", although it is.

That would be a fine candidate for homebrew, of course.

We have not decided yet, but it is maybe the start of generally maintaining
the "stackless" name for all future versions, because that removes a lot
of naming issues at no cost.

cheers - chris


On 06.01.14 01:24, Werner Thie wrote:
Hi

will that happen on stackless.com with tarballs or somewhere else?

Although being interested in stackless for several years, for me following the recent discussions were both enlightening as well as frustrating, because there is so little information painting a big picture of all the bits and pieces of stackless and its relatives.

Maybe painting an inheritance tree would help?

With my attempt having failed at bringing stackless to the main homebrew repos on OSX on the grounds that 'it is confusing the user because this is just another python and we already have enough problems with OXS's system python and the homebrew one' I felt some hope when reading the discussions about naming stackless differently.

My plan still is to have stackless as a brew formula on OSX and as a port on FreeBSD, so anything which separates stackless from the CPython installation seems to me a step into the right direction.

Werner

On 1/5/14 12:24 PM, Richard Tew wrote:
Hi,

I've been reflecting on the 2.7.6 and 3.3.3 releases of Stackless, and
how I think it's important we do them in a timely fashion.

However, there are a decent number of outstanding issues, so I'd like
to propose a different approach.

I plan to do three release candidate releases:

2.7.6
3.3.3
3.4.0

These will only include the latest finalised changes.

I'll also make a list of outstanding things that need to be addressed
before we can do final releases, and then once these are done, I'll
tag and package up the official source releases.

Then people can step up to do windows and macos installers.

My hope is that then someone who goes to the Stackless web site won't
see old versions only being available.  Ideally we'd be able to
generate windows and macos installers for the intermediate release
candidates, but.. I'm not sure anyone with the right software licenses
will find the time.  We'll see.

Thoughts? Ideas?

Cheers,
Richard.

_______________________________________________
Stackless mailing list
[email protected]
http://www.stackless.com/mailman/listinfo/stackless



_______________________________________________
Stackless mailing list
[email protected]
http://www.stackless.com/mailman/listinfo/stackless


--
Christian Tismer             :^)   <mailto:[email protected]>
Software Consulting          :     Have a break! Take a ride on Python's
Karl-Liebknecht-Str. 121     :    *Starship* http://starship.python.net/
14482 Potsdam                :     PGP key -> http://pgp.uni-mainz.de
phone +49 173 24 18 776  fax +49 (30) 700143-0023
PGP 0x57F3BF04       9064 F4E1 D754 C2FF 1619  305B C09C 5A3B 57F3 BF04
      whom do you want to sponsor today?   http://www.stackless.com/


_______________________________________________
Stackless mailing list
[email protected]
http://www.stackless.com/mailman/listinfo/stackless

Reply via email to