stackless.com with tarballs.

Cheers,
Richard.

On 1/6/14, Werner Thie <[email protected]> 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
>

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

Reply via email to