Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-07-01 Thread Georg Brandl
Am 01.07.2013 23:05, schrieb Victor Stinner: > Hi Georg, > > 2013/7/1 Georg Brandl : >> Am 26.06.2013 16:24, schrieb Victor Stinner: >>> 2013/6/26 Eric V. Smith : I think that's exactly what's happening. From the bug report: find $(srcdir) '(' -name '*.fdc' -o -nam

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-07-01 Thread Eric V. Smith
On 7/1/2013 5:13 PM, R. David Murray wrote: > distclean still needs to be fixed, so please open a new issue for > adding buildclean or whatever you want to call it, as Eric requested > in the existing issue. I finally got around to testing it today, so I'm going to check in my change to 18312 some

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-07-01 Thread R. David Murray
On Mon, 01 Jul 2013 23:05:56 +0200, Victor Stinner wrote: > Hi Georg, > > 2013/7/1 Georg Brandl : > > Am 26.06.2013 16:24, schrieb Victor Stinner: > >> 2013/6/26 Eric V. Smith : > >>> I think that's exactly what's happening. > >>> > >>> From the bug report: > >>> > >>> find $(srcdir) '('

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-07-01 Thread Victor Stinner
Hi Georg, 2013/7/1 Georg Brandl : > Am 26.06.2013 16:24, schrieb Victor Stinner: >> 2013/6/26 Eric V. Smith : >>> I think that's exactly what's happening. >>> >>> From the bug report: >>> >>> find $(srcdir) '(' -name '*.fdc' -o -name '*~' \ >>>-o -name '[@,#]*'

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-07-01 Thread Gregory P. Smith
If we disallowed builds *from in source tree* requiring all output to go into a separate build output directory instead (like any sane person does*) we wouldn't need a crazy find in the source tree to mess things up. ;) this can be done today: $ mkdir foo && cd foo && ../my-hg/2.7/configure --src

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-07-01 Thread R. David Murray
On Mon, 01 Jul 2013 08:33:38 +0200, Georg Brandl wrote: > Am 26.06.2013 16:24, schrieb Victor Stinner: > > 2013/6/26 Eric V. Smith : > >> I think that's exactly what's happening. > >> > >> From the bug report: > >> > >> find $(srcdir) '(' -name '*.fdc' -o -name '*~' \ > >>

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-30 Thread Georg Brandl
Am 26.06.2013 16:24, schrieb Victor Stinner: > 2013/6/26 Eric V. Smith : >> I think that's exactly what's happening. >> >> From the bug report: >> >> find $(srcdir) '(' -name '*.fdc' -o -name '*~' \ >>-o -name '[@,#]*' -o -name '*.old' \ >>

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-26 Thread Eric V. Smith
On 6/26/2013 9:02 AM, Eric V. Smith wrote: > On 6/26/2013 8:44 AM, Oleg Broytman wrote: >> On Wed, Jun 26, 2013 at 08:18:27AM -0400, "Eric V. Smith" >> wrote: >> find $(srcdir)/* ... >> >> to avoid this problem. It won't expand the .hg top-level directory. > >Or find \( -t

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-26 Thread Stephen J. Turnbull
Victor Stinner writes: > In my opinion, make distclean should only remove files generated by > configure and a build. It should not remove random files. FWIW, the GNU standard for these targets is something like: ## make clean or make mostlyclean ## Delete all files from the current dir

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-26 Thread a . cavallo
*~, .orig, .rej, .back should be kept. They are not generated by configure nor make. Ideally they should be left untracked not ignored. While devs can certainly add them to the .hgignore list to make life easier, a repository should be clean of extra files (or shown as untracked). I'd add t

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-26 Thread Victor Stinner
2013/6/26 Eric V. Smith : > I think that's exactly what's happening. > > From the bug report: > > find $(srcdir) '(' -name '*.fdc' -o -name '*~' \ >-o -name '[@,#]*' -o -name '*.old' \ >-o -name '*.orig' -o -name '*.rej' \ >

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-26 Thread R. David Murray
On Wed, 26 Jun 2013 09:39:54 -0400, Barry Warsaw wrote: > On Jun 26, 2013, at 09:04 AM, Eric V. Smith wrote: > > >I run 'make distclean' fairly often, but maybe it's just out of habit. > >If I'm adding/deleting modules, I want to make sure there are no build > >artifacts. And since I have modifie

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-26 Thread Ronald Oussoren
On 26 Jun, 2013, at 15:39, Barry Warsaw wrote: > On Jun 26, 2013, at 09:04 AM, Eric V. Smith wrote: > >> I run 'make distclean' fairly often, but maybe it's just out of habit. >> If I'm adding/deleting modules, I want to make sure there are no build >> artifacts. And since I have modified files

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-26 Thread Barry Warsaw
On Jun 26, 2013, at 09:04 AM, Eric V. Smith wrote: >I run 'make distclean' fairly often, but maybe it's just out of habit. >If I'm adding/deleting modules, I want to make sure there are no build >artifacts. And since I have modified files, a clean checkout won't help >(easily, at least). As do I.

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-26 Thread Zachary Ware
On Wed, Jun 26, 2013 at 8:12 AM, wrote: >Eric V. Smith wrote: >> How would that work? How could hg purge the .bak, .orig, .rej, .old, >> etc. files? > > > hg purge (it's an extension) removes anything that isn't tracked (and not > ignored in the .hgignore): kind of distclean. > > I hope this help

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-26 Thread Antoine Pitrou
Le Wed, 26 Jun 2013 15:12:45 +0200, a.cava...@cavallinux.eu a écrit : > > > How would that work? How could hg purge the .bak, .orig, .rej, .old, > > etc. files? > > hg purge (it's an extension) removes anything that isn't tracked (and > not ignored in the .hgignore): kind of distclean. distclea

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-26 Thread a . cavallo
How would that work? How could hg purge the .bak, .orig, .rej, .old, etc. files? hg purge (it's an extension) removes anything that isn't tracked (and not ignored in the .hgignore): kind of distclean. I hope this helps ___ Python-Dev mailing list

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-26 Thread Eric V. Smith
On 6/26/2013 8:57 AM, Ronald Oussoren wrote: > > On 26 Jun, 2013, at 14:18, Eric V. Smith wrote: > >> On 6/26/2013 6:43 AM, a.cava...@cavallinux.eu wrote: >>> .. or having hg "purging" unwanted build artifact (probably cleaning up >>> the .hgignore file first) >> >> How would that work? How coul

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-26 Thread Eric V. Smith
On 6/26/2013 8:44 AM, Oleg Broytman wrote: > On Wed, Jun 26, 2013 at 08:18:27AM -0400, "Eric V. Smith" > wrote: > find $(srcdir)/* ... > > to avoid this problem. It won't expand the .hg top-level directory. Or find \( -type d -name .hg -prune \) -o ... >> >> I'm torn. You

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-26 Thread Ronald Oussoren
On 26 Jun, 2013, at 14:18, Eric V. Smith wrote: > On 6/26/2013 6:43 AM, a.cava...@cavallinux.eu wrote: >> .. or having hg "purging" unwanted build artifact (probably cleaning up >> the .hgignore file first) > > How would that work? How could hg purge the .bak, .orig, .rej, .old, > etc. files? >

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-26 Thread Oleg Broytman
On Wed, Jun 26, 2013 at 08:18:27AM -0400, "Eric V. Smith" wrote: > >>> find $(srcdir)/* ... > >>> > >>> to avoid this problem. It won't expand the .hg top-level directory. > >> > >>Or find \( -type d -name .hg -prune \) -o ... > > I'm torn. Yours is more obvious, but we'd likely need to add

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-26 Thread Eric V. Smith
On 6/26/2013 8:18 AM, Eric V. Smith wrote: > On 6/26/2013 6:43 AM, a.cava...@cavallinux.eu wrote: >> .. or having hg "purging" unwanted build artifact (probably cleaning up >> the .hgignore file first) > > How would that work? How could hg purge the .bak, .orig, .rej, .old, > etc. files? > f

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-26 Thread Eric V. Smith
On 6/26/2013 6:43 AM, a.cava...@cavallinux.eu wrote: > .. or having hg "purging" unwanted build artifact (probably cleaning up > the .hgignore file first) How would that work? How could hg purge the .bak, .orig, .rej, .old, etc. files? >>> find $(srcdir)/* ... >>> >>> to avoid this problem. It wo

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-26 Thread a . cavallo
.. or having hg "purging" unwanted build artifact (probably cleaning up the .hgignore file first) find $(srcdir)/* ... to avoid this problem. It won't expand the .hg top-level directory. Or find \( -type d -name .hg -prune \) -o ... Oleg. __

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-26 Thread Oleg Broytman
On Tue, Jun 25, 2013 at 10:11:04PM -0400, "Eric V. Smith" wrote: > On 6/25/2013 9:33 PM, Senthil Kumaran wrote: > > > > > > > > On Tue, Jun 25, 2013 at 5:58 PM, Benjamin Peterson > > wrote: > > > > 2013/6/25 Victor Stinner >

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-25 Thread Eric V. Smith
On 6/25/2013 9:33 PM, Senthil Kumaran wrote: > > > > On Tue, Jun 25, 2013 at 5:58 PM, Benjamin Peterson > wrote: > > 2013/6/25 Victor Stinner >: > > And then I ran "make distclean"... > > You've left us hanging... >

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-25 Thread Mark Janssen
> One month ago, unit tests were added to IDLE (cool!) with a file > called @README.txt. The @ was used to see the name on top in a listing > of the directory. It's like this. Whenever you use special characters in a file name, you're asking for trouble. The shell and the OS have negotiate how t

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-25 Thread Mark Janssen
> It's like this. Whenever you use special characters in a file name, > you're asking for trouble. The shell and the OS have negotiate how to > interpret it. It bigger than git, and not a bug. Sorry, I meant mercurial, not git. -- MarkJ Tacoma, Washington __

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-25 Thread Steven D'Aprano
On 26/06/13 08:44, Victor Stinner wrote: And then I ran "make distclean"... Victor, you're a cruel, cruel man. You've told us everything except the solution to the mystery. -- Steven ___ Python-Dev mailing list Python-Dev@python.org http://mail.p

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-25 Thread Senthil Kumaran
On Tue, Jun 25, 2013 at 5:58 PM, Benjamin Peterson wrote: > 2013/6/25 Victor Stinner : > > And then I ran "make distclean"... > > You've left us hanging... > > Yeah, the final part is here: http://bz.selenic.com/show_bug.cgi?id=3954#c4 But still I have question as why hg complained about @README i

Re: [Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-25 Thread Benjamin Peterson
2013/6/25 Victor Stinner : > And then I ran "make distclean"... You've left us hanging... -- Regards, Benjamin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mai

[Python-Dev] End of the mystery "@README.txt Mercurial bug"

2013-06-25 Thread Victor Stinner
Hi, One month ago, unit tests were added to IDLE (cool!) with a file called @README.txt. The @ was used to see the name on top in a listing of the directory. Some developers began to get strange Mercurial errors like: "abort: data/Lib/idlelib/idle_test/@README.txt.i at 7573717b9e6f: no match" " 8