search

jparris / enso

Automatically exported from code.google.com/p/enso
Other
0 stars 0 forks source link

Rewrite existing code to fit PEP-8 style guideline #6

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Since we've agreed to use the PEP-8 style guidelines, somebody needs to go
through the existing Python code and convert it all.

Atul Varma has kindly volunteered, so I'm assigning this to him.

Original issue reported on code.google.com by ebj...@gmail.com on 21 Mar 2008 at 5:38

GoogleCodeExporter commented 8 years ago 
P.S. if anyone wants to help with this and needs to know what, exactly, PEP-8
entails, it's documented here:
http://www.python.org/dev/peps/pep-0008/

Original comment by ebj...@gmail.com on 21 Mar 2008 at 5:40

GoogleCodeExporter commented 8 years ago 
For future reference, the Enso Developers thread that discusses and outlines the
rationale for this change can be found here:

  http://groups.google.com/group/enso-developers/browse_thread/thread/56c0b29ad6b757a7

Original comment by var...@gmail.com on 24 Mar 2008 at 4:11