Hello all, I recently integrated pyflakes into Leo <http://leoeditor.com/> and am awed by its speed and elegance. Its simplicity is pure genius. A few days ago I set up the pyflakes-study google group <https://groups.google.com/forum/#!forum/pyflakes-study> and corresponding github repo <https://github.com/edreamleo/pyflakes-study> and have been happily playing around with the pyflakes code ever since. To properly see what I have done you will have to look at the .leo file with Leo. To paraphrase Richard Feynman, that which I cannot alter I do not understand. By this criterion I now understand almost every line of pyflakes. Hehe. It's possible to speed up pyflakes by at least 10% by using a less elegant traversal scheme, as describe here <https://groups.google.com/forum/#!topic/pyflakes-study/amxtB0MKOGI>. Not sure whether you would be interested--there are some drawbacks. It's also possible to speed up pyflakes by an additional 5% merely by removing the scope property, as described in today's post <https://groups.google.com/forum/#!topic/pyflakes-study/9WoO9shG5fk>. This post also describes a buglet in pyflakes and its fix. Most of today's post is geared toward a new tool I am considering. This would compare name conventions with actual usage. The first phase might be a scope resolver, using a simplified version of the pyflakes code. The second phase will have to do a whole lot more with Ast.Attribute :-) You might call the new tool a follow up to my make-stub-files project <https://groups.google.com/forum/#!topic/python-static-type-checking/n68MH1xoOwE>, with corresponding github repo <https://github.com/edreamleo/make-stub-files>. I announced make-stub-files in my largely unsuccessful python-static-typechecking <https://groups.google.com/forum/#%21forum/python-static-type-checking> group. Boy, am I happy mypy <http://mypy-lang.org/> is doing the heavy lifting. I would appreciate any comments, suggestions and corrections you might have. Edward ------------------------------------------------------------------------------------------ Edward K. Ream: edreamleo@gmail.com Leo: http://leoeditor.com/ ------------------------------------------------------------------------------------------
Edward, thanks for doing this work. It looks really great. I'm pretty slammed with personal commitments right now, but I promise I'll get to this eventually. Thanks again for the excellent contribution. On Fri, May 27, 2016 at 10:55 AM Edward K. Ream <edreamleo@gmail.com> wrote:
Hello all,
I recently integrated pyflakes into Leo <http://leoeditor.com/> and am awed by its speed and elegance. Its simplicity is pure genius. A few days ago I set up the pyflakes-study google group <https://groups.google.com/forum/#!forum/pyflakes-study> and corresponding github repo <https://github.com/edreamleo/pyflakes-study> and have been happily playing around with the pyflakes code ever since. To properly see what I have done you will have to look at the .leo file with Leo.
To paraphrase Richard Feynman, that which I cannot alter I do not understand. By this criterion I now understand almost every line of pyflakes. Hehe.
It's possible to speed up pyflakes by at least 10% by using a less elegant traversal scheme, as describe here <https://groups.google.com/forum/#!topic/pyflakes-study/amxtB0MKOGI>. Not sure whether you would be interested--there are some drawbacks.
It's also possible to speed up pyflakes by an additional 5% merely by removing the scope property, as described in today's post <https://groups.google.com/forum/#!topic/pyflakes-study/9WoO9shG5fk>. This post also describes a buglet in pyflakes and its fix.
Most of today's post is geared toward a new tool I am considering. This would compare name conventions with actual usage. The first phase might be a scope resolver, using a simplified version of the pyflakes code. The second phase will have to do a whole lot more with Ast.Attribute :-)
You might call the new tool a follow up to my make-stub-files project <https://groups.google.com/forum/#!topic/python-static-type-checking/n68MH1xoOwE>, with corresponding github repo <https://github.com/edreamleo/make-stub-files>. I announced make-stub-files in my largely unsuccessful python-static-typechecking <https://groups.google.com/forum/#%21forum/python-static-type-checking> group. Boy, am I happy mypy <http://mypy-lang.org/> is doing the heavy lifting.
I would appreciate any comments, suggestions and corrections you might have.
Edward
------------------------------------------------------------------------------------------ Edward K. Ream: edreamleo@gmail.com Leo: http://leoeditor.com/
------------------------------------------------------------------------------------------ _______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality
On Tue, May 31, 2016 at 9:34 AM, Phil Frost <indigo@bitglue.com> wrote:
Edward, thanks for doing this work. It looks really great.
I'm pretty slammed with personal commitments right now, but I promise I'll get to this eventually. Thanks again for the excellent contribution.
You're welcome. Thanks for the kind words. I'd like to test the new code using the pyflakes unit tests. Alas, Anaconda's <https://www.continuum.io/why-anaconda>frozen import feature is making this difficult. importlib seems fixated on the official package. Hopefully soon... Edward
On Tue, May 31, 2016 at 9:34 AM, Phil Frost <indigo@bitglue.com> wrote:
Edward, thanks for doing this work. It looks really great. The project is complete, imo, with a concluding post here <https://groups.google.com/forum/#!topic/pyflakes-study/pJDC6A3zCHQ>. All comments and corrections welcome.
Edward
participants (2)
-
Edward K. Ream -
Phil Frost