Showing content from http://mail.python.org/pipermail/python-dev/attachments/20140120/e05cef28/attachment.html below:
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><br>
On 01/19/2014 08:29 AM, Ethan Furman wrote:<br>
</div>
<blockquote cite="mid:52DBFD65.8050307@stoneleaf.us" type="cite">On
01/19/2014 03:32 AM, Georg Brandl wrote:
<br>
<blockquote type="cite">Am 19.01.2014 11:19, schrieb Larry
Hastings:
<br>
<blockquote type="cite">Not kidding, my best idea so far is
"foo.clinic.h.h",
<br>
</blockquote>
<br>
Why not always put clinic into its own directory?
<br>
<br>
Modules/mathmodule.c -> Modules/clinic/mathmodule.c.h
<br>
Modules/mathmodule.h -> Modules/clinic/mathmodule.h.h
<br>
<br>
At least that is consistent, allows easy exclusion in tools, and
gets rid
<br>
of the additional "clinic" in the filename.
<br>
</blockquote>
<br>
+1
<br>
<br>
If AC will work with both .c and .h files. I think a separate
directory is the way to go.<br>
</blockquote>
<br>
In theory, Argument Clinic works with any file for which it can
iterate over by lines and recognize comments. It current supports C
and Python files and automatically recognizes a bunch of extensions.<br>
<br>
--------------------<br>
<br>
Okay, I'm taking a poll. I will total your answers and take the
result... strongly under advisement. ;-)<br>
<br>
The rules:<br>
* The poll will be over in 48 hours, maybe sooner if a winner
emerges early.<br>
* Please express your vote from -1 to +1. -0 and +0 will only be
differentiated during a tiebreaker.<br>
* If you don't vote for a contestant, your vote will be assumed to
be 0.<br>
* You may change your vote at any time while the poll is still
running.<br>
* If you wish to nominate a new contestant, you may. Please give
the contestant a name, and express how it would transform the
filenames "foo.c" and "foo.h". I would strongly prefer that all
transformations be expressable using str.format(transformation,
filename="foo.c", basename="foo", extension=".c") .<br>
<br>
<br>
The contestants so far:<br>
<br>
Contestant 1: "Add .clinic.h"<br>
<blockquote>foo.c -> foo.c.clinic.h<br>
foo.h -> foo.h.clinic.h<br>
</blockquote>
Contestant 2: "Add .ac.h"<br>
<blockquote>foo.c -> foo.c.ac.h<br>
foo.h -> foo.h.ac.h<br>
</blockquote>
Contestant 3: "Add .clinic"<br>
<blockquote>foo.c -> foo.c.clinic<br>
foo.h -> foo.h.clinic<br>
</blockquote>
Contestant 4: "Put in clinic directory, add .h"<br>
<blockquote>foo.c -> clinic/foo.c.h<br>
foo.h -> clinic/foo.h.h<br>
</blockquote>
Contestant 5: "Put in __clinic__ directory, add .h"<br>
<blockquote>foo.c -> __clinic__/foo.c.h<br>
foo.h -> __clinic__/foo.h.h<br>
</blockquote>
<br>
I didn't add a contestant for what Stefan Krah originally suggested
("foo.c -> foo.h") because it's not clear how this would handle
"foo.h".<br>
<br>
<br>
You'll notice the current behavior is no longer in the running,<br>
<br>
<br>
<i>/arry</i><br>
</body>
</html>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4