[Pyrex] SageX merged back to Pyrex?

[Andreas Kostyrka]

Well, it's the usual situation with non mainstream upstream providers. Lucky for you, pyrex is open source. :)

Basically, you can choose one of these, I'd personally choose SageX (as they seem to be most active). As a worst case fallback the worst that can happen to you is that you'll start to maintain an internal fork. There are version management tools today that make this kind of stuff bearable.

btw, that's not an unique situation with Pyrex, it's rather general to all software, more or less. (And if you believe that a commercial producer will protect your investement in some tool, VB6 comes to mind *eg*)

Andreas

-- Ursprüngl. Mitteil. --
Betreff:	Re: [Pyrex] SageX merged back to Pyrex?
Von:	skip at pobox.com
Datum:		25.07.2007 13:55


    Andreas> Stupid question, why do you want it to be merged back? AFAIK,
    Andreas> SageX is way more actively maintained than Pyrex?

My understanding is/was that SageX is a fork of Pyrex.  I also see mention
of something called lxml-Pyrex which is different in some ways as well,
though how, I couldn't tell from the couple posts I saw that referenced it.
All these forks make it confusing.  Do I install Pyrex?  SageX?  lxml-Pyrex?
What do I gain/give up with each one?  I'm investigating this for adoption
at work.  I can hardly recommend one over the others at this point.

Skip