On Apr 18, 2005, at 12:09 PM, Dethe Elza wrote:
<snip>
Another low-tech solution would be to start a wiki page with known latest versions, urls to download the latest versions, and the above script. No reinvention of the wheel needed, just leveraging what we already have in a different way.
--Dethe
Isn't this what Bob is doing with http://pythonmac.org/packages/
Being new to this "playground" my concern is the next round of versions since they will likely be applicable by the time I get really productive. Say if Apple goes to 2.4 then what about Bob's build, and subsequently Bob's(?) 2.5 (__future__) build?
I for one would like a more transparent and manageable versioning. I don't want to move things around (I'll play by the rules), but I would like to be able to add new versions and remove old versions of Python and components combined. As I understand it, such is what Bob did with 2.4, but what he did is not overly obvious to me (I understand Bob is working within the conventions and constraints of the Mac OS X implementation) and the additional learning curve distracts from the finished app package (at my age without the time of youth one gets more focused :~).
My 2 cents, Lee C
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
