Neal> How often is the python build broken or otherwise unusable?
Not very often. I use the head branch of the repository as the source of
the interpreter I run on my laptop. It generally takes just a couple
minutes on my now-aging PowerBook to svn up and reinstall. I can only
recall one time in the past where I had to temporarily fall back to 2.4
because of some change that broke an application.
Admittedly, I'm not as sophisticated a user as Fredrik or Glyph, but I
suspect that my usage of the language isn't all that different from most
Python developers out there.
Neal> Is part of your point that these developers only care about
Neal> something called "release" and they won't start testing before
Neal> then? If that's the case why don't we start making
Neal> (semi-)automated alpha releases every month?
How would that be any easier than a user setting up a read-only repository
and svn-up-ing it once a month then using that as the default interpreter on
that person's development machine? I maintain interpreters for 2.3, 2.4 and
bleeding edge at the moment. If I need to it's fairly trivial (a symlink
change) to fall back to the latest stable release.
Glyph, would that sort of scheme work for you?
Skip
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
