Tim Peters wrote: > Yes. please. svn:externals should always pin to a specific revision > (or at least to a "frozen" tag). Updating to a new revision then is > just a propedit away (to change the revision number); ditto for > backing off to an older revision if the newer one has problems.
wasn't the whole point for this exercise to make sure that the included version was always up to date. if you pin it to a given version, all we got from this was a dependence on another SVN server. (and a can of SVN worms, including issues with locking/cleanup, etc) </F> _______________________________________________ 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
