Hello Sir!
First, thank you for creating this tool.
next, I would recommend perltidy as a program to emulate. I'll paste the
output of perltidy --help below.
http://perltidy.sourceforge.net/
I could probably write a wrapper script to do this if you'd like.
Cheers,
C.J.
$ perltidy --help
Chuck Rhode schrieb:
> Thomas Heller wrote this on Tue, Dec 05, 2006 at 07:06:30PM +0100. My
> reply is below.
>
>> There is still one major issue. pythonTidy uses open(input-file,
>> "rb") to open the Python module to tidy up. That does not work on
>> Windows, at least if the file has (as it s
Thomas Heller wrote this on Tue, Dec 05, 2006 at 07:06:30PM +0100. My
reply is below.
> There is still one major issue. pythonTidy uses open(input-file,
> "rb") to open the Python module to tidy up. That does not work on
> Windows, at least if the file has (as it should) "\r\n" newlines.
Thank
Thomas Heller wrote this on Tue, Dec 05, 2006 at 07:06:30PM +0100. My
reply is below.
> I suggest you open the file with open(input-file, "rU").
This doesn't work so pretty good while reading from sys.stdin, so I'm
still at the drawing board.
--
.. Chuck Rhode, Sheboygan, WI, USA
.. 1979 Honda
rzed wrote this on Tue, Dec 05, 2006 at 08:19:28PM -0500. My reply is
below.
> I ran PythonTidy on a wxPython sample, and found that wx.CONSTANTS
> were being translated to wx.Constants, which won't do at all.
Find the first line in the PythonTidy code where the following global
variables are d
Chuck Rhode <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
> That went well. PythonTidy has been looked at at least 10**2
> times, and I have received a couple of complaints, which I hope
> I have addressed satisfactorily -- plenty good enough for a beta
> test. The basic concept stands.
Chuck Rhode schrieb:
> That went well. PythonTidy has been looked at at least 10**2 times,
> and I have received a couple of complaints, which I hope I have
> addressed satisfactorily -- plenty good enough for a beta test. The
> basic concept stands.
Sure.
There is still one major issue. python
Thomas Heller wrote this on Fri, Dec 01, 2006 at 10:12:38PM +0100. My reply is
below.
> Chuck Rhode schrieb:
> > o Command-line args: Please give an example of a standard command that
> > I might emulate w.r.t. standard argument use.
> Well, at least it would be nice if I could call
> 'PythonT
Thomas Heller wrote this on Fri, Dec 01, 2006 at 10:12:38PM +0100. My reply is
below.
> Here is part of a diff before and after running PythonTidy on it:
>
>
> -def comptr_setitem(self, index, value):
> -# We override the __setitem__ method of the
> -# POINTER(P
Chuck Rhode schrieb:
> Thomas Heller wrote this on Thu, Nov 30, 2006 at 09:50:25PM +0100. My
> reply is below.
>
>> The two things that bother me at the moment are how the comments are
>> formatted (dunno if that can be customized or changed easily), and
>> it would be good if the script took com
Thomas Heller wrote this on Thu, Nov 30, 2006 at 09:50:25PM +0100. My
reply is below.
> The two things that bother me at the moment are how the comments are
> formatted (dunno if that can be customized or changed easily), and
> it would be good if the script took command line args instead of
> wo
Chuck Rhode schrieb:
> I couldn't find a routine to clean up, regularize, and reformat Python
> code, so I wrote one:
>
> http://www.lacusveris.com/PythonTidy/PythonTidy.python
>
> Now, I'm looking for beta-testers. Compensation is a bit on the low
> side. In fact it's limited to the satisfac
Chuck Rhode wrote:
[...]
> Thanks, too, for trying *PythonTidy*.
No, thanks you for writing such a tool!
> [...] nevertheless, most [options] are declared near the beginning where
> they sit just begging for end-user involvement. See: CODING_SPEC and
> SHEBANG.
The fact that I immediately notic
Roberto Bonvallet wrote this on Thu, Nov 30, 2006 at 01:21:55PM +. My
reply is below.
> About changing the shebang line: I'll take it as a bug.
> About changing the encoding declaration from vim-style to
> emacs-style: I'll take it as an insult :)
Ooh!
> Both are comments, and should be
Laurent Pointal a écrit :
> See http://www.python.org/dev/peps/pep-0263/
Aye, sorry for my missreading...
[seem I hurt the emacs guy]
--
http://mail.python.org/mailman/listinfo/python-list
In <[EMAIL PROTECTED]>, Laurent Pointal wrote:
> Roberto Bonvallet a écrit :
>> # vim: set fileencoding=utf-8 :
> ...
>> # -*- coding: utf-8 -*-
> ...
>> About changing the shebang line: I'll take it as a bug.
>> About changing the encoding declaration from vim-style to emacs-style:
>> I'll take
Laurent Pointal wrote:
> ...
>> # vim: set fileencoding=utf-8 :
> ...
>> # -*- coding: utf-8 -*-
> ...
>
> This is not "emacs-style", this is Python normalized source encoding
> directive for correct interpretation of u"..." strings by Python
> interpreter.
>
> See http://www.python.org/dev/peps/
[Roberto]
> # vim: set fileencoding=utf-8 :
> ...
> # -*- coding: utf-8 -*-
> ...
> About changing the encoding declaration from vim-style to emacs-style:
> I'll take it as an insult :)
[Laurent]
> This is not "emacs-style", this is Python normalized source encoding
> directive for correct interp
Roberto Bonvallet a écrit :
> Chuck Rhode wrote:
>> I couldn't find a routine to clean up, regularize, and reformat Python
>> code, so I wrote one:
>>
>> http://www.lacusveris.com/PythonTidy/PythonTidy.python
>>
>> Now, I'm looking for beta-testers. Compensation is a bit on the low
>> side. In f
Chuck Rhode wrote:
> I couldn't find a routine to clean up, regularize, and reformat Python
> code, so I wrote one:
>
> http://www.lacusveris.com/PythonTidy/PythonTidy.python
>
> Now, I'm looking for beta-testers. Compensation is a bit on the low
> side. In fact it's limited to the satisfactio
20 matches
Mail list logo
