On 3/16/2012 11:57 AM, Glenn Linderman wrote: > So I think I'm finally beginning to see the underlying reason why Van is > desiring this consistency: It is not that he wants to check in his > installation of Python, but that he wants to check in his installation > of his packages and scripts into a source control environment, and then > be able to check out that source control environment into an > installation of Python on another machine of a different architecture. > In an environment where a source control system is pervasive and well > used, this would be an effective deployment alternative to developing a > packaging/distribution solution using distutils, distutels2, packaging, > easy_install, eggs, or peanuts, or any other such scheme. > > But! > > Source control environments don't lend themselves to being used for > anything except exact replication of file and directory structure, so > when the different architectures have different directory structures, > this deployment technique cannot easily work.... except, as Van has > discussed, by tweaking the development machine's environment to match > that of the deployment machines... and that only works in the case where > the deployment happens to only one architecture, and the development > machine can be tweaked to match... but deploying to multiple machine > having different architectures and directory structures would be > impossible using the source control deployment technique, because of the > different directory structures.
This is exactly correct.CIRCULAR 230 NOTICE: To ensure compliance with requirements imposed by U.S. Treasury Regulations, Haynes and Boone, LLP informs you that any U.S. tax advice contained in this communication (including any attachments) was not intended or written to be used, and cannot be used, for the purpose of (i) avoiding penalties under the Internal Revenue Code or (ii) promoting, marketing or recommending to another party any transaction or matter addressed herein. CONFIDENTIALITY NOTICE: This electronic mail transmission is confidential, may be privileged and should be read or retained only by the intended recipient. If you have received this transmission in error, please immediately notify the sender and delete it from your system. _______________________________________________ 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