On Fri, 14 Mar 2014 12:08:22 -0500 Zachary Ware <zachary.ware+py...@gmail.com> wrote:
> On Fri, Mar 14, 2014 at 10:55 AM, Benjamin Peterson <benja...@python.org> > wrote: > > On Fri, Mar 14, 2014, at 08:52 AM, Zachary Ware wrote: > >> On Fri, Mar 14, 2014 at 10:10 AM, Benjamin Peterson <benja...@python.org> > >> wrote: > >> > Why are you readding these when they were apparently purposely removed > >> > in eef7899ea7ab? > >> > >> It is rather ugly to build the docs in a 3.3 checkout, then update to > >> default and run 'hg status' without those entries in .hgignore. I can > >> understand not wanting to be bombarded by all of the untracked files, > >> but it's also pretty easy to enable the purge extension and do "hg > >> purge Doc/tools". > > > > This is why everyone should use the share extension and have separate > > working copies for every branch. :) > > I've been using that setup for a few months now (and cursing myself > for not switching sooner), but I've still found myself annoyed by this > issue a time or two since the doc build chain change. I personally > don't mind whether those entries are in .hgignore or not, but I don't > see the harm in them sticking around (at least until 3.3 is out of > maintenance; updating from 2.7 to default is a great source of > problems even aside from this issue). Indeed, I think it's ok to keep them. Regards Antoine. _______________________________________________ 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
