R. Jayakrishnan added the comment:
I would prefer this issue concludes with a navigation to the new proposed
enhancement.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18704
___
R. Jayakrishnan added the comment:
Thanks for showing great interest on this idea.
As usual, it seems this will going to be another nice project with IDLE for me.
Better to close this issue then, and create an appropriate initiation with the
suggested points(preferring a commencement by core
Raymond Hettinger added the comment:
[TJR]
I am opposed to this specific proposal and
think this issue should be closed.
[Ramchandra Apte]
Agree with Terry Reedy.
[R. Jayakrishnan]
Better to close this issue then ...
I agree as well.
--
resolution: - rejected
status: open -
Ezio Melotti added the comment:
I think modern editors are expected to have this sort of functionality
built into them [1].
Mine doesn't :)
XCode is simply amazing where it will pop up errors and quote the C99
standard [2].
That's a standard though, the ones in PEP8 are just
Terry J. Reedy added the comment:
Summary:
I am in favor of making more Python code analysis available from within Idle. I
have an alternate, more generalized proposal. I am opposed to this specific
proposal and think this issue should be closed.
Alternatives: when and how to analyze.
1.
Ramchandra Apte added the comment:
Agree with Terry Reedy.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18704
___
___
Python-bugs-list mailing
Todd Rovito added the comment:
Ezio,
I think modern editors are expected to have this sort of functionality built
into them [1]. XCode is simply amazing where it will pop up errors and quote
the C99 standard [2]. We don't expect IDLE to have all that functionality but
it seemed to us
Todd Rovito added the comment:
Raymond,
Would you prefer PyFlakes instead? Try to consider IDLE being for beginners
so they need all the help they can get. Advanced users can always turn the
extension off. Thanks for your input.
--
___
Python
Changes by Todd Rovito rovit...@gmail.com:
--
nosy: +terry.reedy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18704
___
___
Python-bugs-list
Ezio Melotti added the comment:
Can't this be developed as an external extension?
I don't see a reason to include it in the stdlib, especially if it requires
other dependencies (like the pep8 module).
--
nosy: +ezio.melotti
status: open - pending
Raymond Hettinger added the comment:
-1 on giving PEP 8 any more weight than it already has.
Automated PEP 8 checker tools do away the human commen sense component (the
foolish consistency quote is in PEP 8 for a reason).
Another downside is that rigid adherence to PEP 8 tends to focus
Changes by Raymond Hettinger raymond.hettin...@gmail.com:
--
versions: -Python 2.7, Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18704
___
Changes by R. Jayakrishnan raaj...@gmail.com:
--
nosy: +philwebster
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18704
___
___
Python-bugs-list
Ramchandra Apte added the comment:
I like the idea of having a PEP8-checker for IDLE.
--
nosy: +Ramchandra Apte
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18704
___
New submission from R. Jayakrishnan:
This is to create an IDLE extension that would integrate PEP8 (Syntax Style
Checker https://pypi.python.org/pypi/pep8 ) into the IDLE editor window,so the
developer who is using the IDLE editor can quickly and frequently check the
PEP8 standards of the
Changes by R. Jayakrishnan raaj...@gmail.com:
--
nosy: +Todd.Rovito
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18704
___
___
Python-bugs-list
16 matches
Mail list logo
