On 25 Jan 2015 01:09, "Benjamin Peterson" <benja...@python.org> wrote: > > > > On Sat, Jan 24, 2015, at 03:00, Nick Coghlan wrote: > > On 20 January 2015 at 10:53, Benjamin Peterson <benja...@python.org> > > wrote: > > > > > > > > > On Mon, Jan 19, 2015, at 19:40, Neil Girdhar wrote: > > >> I was also wondering why files like Python/graminit.c are in the > > >> respository? They generate spurious merge conflicts. > > > > > > Convenience mostly. > > > > It also gets us a round a couple of bootstrapping problems, where > > generating some of those files requires a working Python interpreter, > > which you may not have if you just cloned the source tree or unpacked > > the tarball. > > We could distribute the generated files in tarballs as part of the > release process.
It's far more developer friendly to aim to have builds from a source check-out "just work" if we can. That's pretty much where we are today (getting external dependencies for the optional parts on *nix can still be a bit fiddly - it may be worth maintaining instructions for at least apt and yum in the developer guide that cover that) Cheers, Nick.
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
