Am 26.06.2013 16:24, schrieb Victor Stinner:
2013/6/26 Eric V. Smith e...@trueblade.com:
I think that's exactly what's happening.
From the bug report:
find $(srcdir) '(' -name '*.fdc' -o -name '*~' \
-o -name '[@,#]*' -o -name '*.old' \
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
Hi Georg,
2013/7/1 Georg Brandl g.bra...@gmx.net:
Am 26.06.2013 16:24, schrieb Victor Stinner:
2013/6/26 Eric V. Smith e...@trueblade.com:
I think that's exactly what's happening.
From the bug report:
find $(srcdir) '(' -name '*.fdc' -o -name '*~' \
-o
On Mon, 01 Jul 2013 23:05:56 +0200, Victor Stinner victor.stin...@gmail.com
wrote:
Hi Georg,
2013/7/1 Georg Brandl g.bra...@gmx.net:
Am 26.06.2013 16:24, schrieb Victor Stinner:
2013/6/26 Eric V. Smith e...@trueblade.com:
I think that's exactly what's happening.
From the bug report:
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
Am 01.07.2013 23:05, schrieb Victor Stinner:
Hi Georg,
2013/7/1 Georg Brandl g.bra...@gmx.net:
Am 26.06.2013 16:24, schrieb Victor Stinner:
2013/6/26 Eric V. Smith e...@trueblade.com:
I think that's exactly what's happening.
From the bug report:
find $(srcdir) '(' -name '*.fdc'
On Tue, Jun 25, 2013 at 10:11:04PM -0400, Eric V. Smith e...@trueblade.com
wrote:
On 6/25/2013 9:33 PM, Senthil Kumaran wrote:
On Tue, Jun 25, 2013 at 5:58 PM, Benjamin Peterson benja...@python.org
mailto:benja...@python.org wrote:
2013/6/25 Victor Stinner
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?
find
On Wed, Jun 26, 2013 at 08:18:27AM -0400, Eric V. Smith e...@trueblade.com
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
On 26 Jun, 2013, at 14:18, Eric V. Smith e...@trueblade.com 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.
On 6/26/2013 8:44 AM, Oleg Broytman wrote:
On Wed, Jun 26, 2013 at 08:18:27AM -0400, Eric V. Smith
e...@trueblade.com 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
On 6/26/2013 8:57 AM, Ronald Oussoren wrote:
On 26 Jun, 2013, at 14:18, Eric V. Smith e...@trueblade.com 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
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
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.
distclean
On Wed, Jun 26, 2013 at 8:12 AM, a.cava...@cavallinux.eu 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
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. I
On 26 Jun, 2013, at 15:39, Barry Warsaw ba...@python.org 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
On Wed, 26 Jun 2013 09:39:54 -0400, Barry Warsaw ba...@python.org 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
2013/6/26 Eric V. Smith e...@trueblade.com:
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' \
*~, .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
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
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
e...@trueblade.com wrote:
find $(srcdir)/* ...
to avoid this problem. It won't expand the .hg top-level directory.
Or find \( -type d -name .hg
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
2013/6/25 Victor Stinner victor.stin...@gmail.com:
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:
On Tue, Jun 25, 2013 at 5:58 PM, Benjamin Peterson benja...@python.orgwrote:
2013/6/25 Victor Stinner victor.stin...@gmail.com:
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
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
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
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 to
On 6/25/2013 9:33 PM, Senthil Kumaran wrote:
On Tue, Jun 25, 2013 at 5:58 PM, Benjamin Peterson benja...@python.org
mailto:benja...@python.org wrote:
2013/6/25 Victor Stinner victor.stin...@gmail.com
mailto:victor.stin...@gmail.com:
And then I ran make distclean...
29 matches
Mail list logo
