Pyflakes forked to Frosted
Hi Everyone, I just wanted to let you know, after Pyflakes seemed dead for about 5 months I created a fork called Frosted: https://github.com/timothycrosley/frosted While it seems that Pyflakes is somewhat alive again, In the fork a lot of code has been simplified and a lot of necessary but missing features (such as configuration) have been added. Additionally, I've merged in a lot of improvements from the Pyflakes community at large. I will be working hard to improve Frosted further, and any suggestions / feature improvements that are recommended will be met with enthusiasm :). While, I would be willing to merge the two projects at some later point, I think in the short-term the rapid development and freedom working under a new project name will bring - will be very beneficial. I have added Florent Xicluna and Steven Myint as collaborators on the project, as these are both developers I have high regard for, and remove the possibility of me being the single source of failure for unmerged pull-requests. So if you have time, please check out the project, request features, and make pull requests. Lets make a great Python code checker even better! Thanks! Timothy
If you're going to continue to maintain this fork you should join the mailing list so your messages do not need to be moderated. That said, I have a few points of feedback for you: Error numbers in tools such as pep8 and pyflakes (although flake8 adds them to pyflakes) are usually not made to be entirely successive. For the most part, there are groupings of errors. The best explanation of this is pep8's documentation: http://pep8.readthedocs.org/en/latest/intro.html#error-codes Anything starting with E1 is related to indentation, anything starting with E2 is related to whitespace. These are conceptually classes of errors. PyLint also follows this convention if I remember correctly and you would do well to do the same. The error codes that Flake8 adds to PyFlakes follow that convention as well. This probably also means that if you're following semver that this will be a new major version bump since you're changing how items are ignored. On Sun, Jan 19, 2014 at 9:50 AM, timothy crosley <timothy.crosley@gmail.com> wrote:
Hi Everyone,
I just wanted to let you know, after Pyflakes seemed dead for about 5 months I created a fork called Frosted:
https://github.com/timothycrosley/frosted
While it seems that Pyflakes is somewhat alive again, In the fork a lot of code has been simplified and a lot of necessary but missing features (such as configuration) have been added. Additionally, I've merged in a lot of improvements from the Pyflakes community at large. I will be working hard to improve Frosted further, and any suggestions / feature improvements that are recommended will be met with enthusiasm :).
While, I would be willing to merge the two projects at some later point, I think in the short-term the rapid development and freedom working under a new project name will bring - will be very beneficial. I have added Florent Xicluna and Steven Myint as collaborators on the project, as these are both developers I have high regard for, and remove the possibility of me being the single source of failure for unmerged pull-requests.
So if you have time, please check out the project, request features, and make pull requests. Lets make a great Python code checker even better!
Thanks!
Timothy
_______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality
Hi Ian, I do plan on maintaining this fork, and I had just subscribed and verified my email. I'm not sure why it still required moderation - is there a waiting period? Different subscription modes? In any case, Thanks for the helpful feedback! I will implement this conceptual error codes, as I agree it is more logical and standard. I am following semantic versioning so it will mean incrementing to new major version - but it shouldn't be too big of a deal as frosted does not yet have a large group of users. Thanks! Timothy On Sun, Jan 19, 2014 at 11:35 AM, Ian Cordasco <graffatcolmingov@gmail.com>wrote:
If you're going to continue to maintain this fork you should join the mailing list so your messages do not need to be moderated.
That said, I have a few points of feedback for you:
Error numbers in tools such as pep8 and pyflakes (although flake8 adds them to pyflakes) are usually not made to be entirely successive. For the most part, there are groupings of errors. The best explanation of this is pep8's documentation: http://pep8.readthedocs.org/en/latest/intro.html#error-codes
Anything starting with E1 is related to indentation, anything starting with E2 is related to whitespace. These are conceptually classes of errors. PyLint also follows this convention if I remember correctly and you would do well to do the same. The error codes that Flake8 adds to PyFlakes follow that convention as well.
This probably also means that if you're following semver that this will be a new major version bump since you're changing how items are ignored.
On Sun, Jan 19, 2014 at 9:50 AM, timothy crosley <timothy.crosley@gmail.com> wrote:
Hi Everyone,
I just wanted to let you know, after Pyflakes seemed dead for about 5 months I created a fork called Frosted:
https://github.com/timothycrosley/frosted
While it seems that Pyflakes is somewhat alive again, In the fork a lot of code has been simplified and a lot of necessary but missing features (such as configuration) have been added. Additionally, I've merged in a lot of improvements from the Pyflakes community at large. I will be working hard to improve Frosted further, and any suggestions / feature improvements that are recommended will be met with enthusiasm :).
While, I would be willing to merge the two projects at some later point, I think in the short-term the rapid development and freedom working under a new project name will bring - will be very beneficial. I have added Florent Xicluna and Steven Myint as collaborators on the project, as these are both developers I have high regard for, and remove the possibility of me being the single source of failure for unmerged pull-requests.
So if you have time, please check out the project, request features, and make pull requests. Lets make a great Python code checker even better!
Thanks!
Timothy
_______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality
Also, feel free to list this mailing list in your readme. Pylint, pep8, PyFlakes, mccabe, and Flake8 all use this as their project mailing lists. On Jan 19, 2014 11:00 AM, "timothy crosley" <timothy.crosley@gmail.com> wrote:
Hi Ian,
I do plan on maintaining this fork, and I had just subscribed and verified my email. I'm not sure why it still required moderation - is there a waiting period? Different subscription modes?
In any case, Thanks for the helpful feedback! I will implement this conceptual error codes, as I agree it is more logical and standard. I am following semantic versioning so it will mean incrementing to new major version - but it shouldn't be too big of a deal as frosted does not yet have a large group of users.
Thanks!
Timothy
On Sun, Jan 19, 2014 at 11:35 AM, Ian Cordasco <graffatcolmingov@gmail.com
wrote:
If you're going to continue to maintain this fork you should join the mailing list so your messages do not need to be moderated.
That said, I have a few points of feedback for you:
Error numbers in tools such as pep8 and pyflakes (although flake8 adds them to pyflakes) are usually not made to be entirely successive. For the most part, there are groupings of errors. The best explanation of this is pep8's documentation: http://pep8.readthedocs.org/en/latest/intro.html#error-codes
Anything starting with E1 is related to indentation, anything starting with E2 is related to whitespace. These are conceptually classes of errors. PyLint also follows this convention if I remember correctly and you would do well to do the same. The error codes that Flake8 adds to PyFlakes follow that convention as well.
This probably also means that if you're following semver that this will be a new major version bump since you're changing how items are ignored.
Hi Everyone,
I just wanted to let you know, after Pyflakes seemed dead for about 5 months I created a fork called Frosted:
https://github.com/timothycrosley/frosted
While it seems that Pyflakes is somewhat alive again, In the fork a lot of code has been simplified and a lot of necessary but missing features (such as configuration) have been added. Additionally, I've merged in a lot of improvements from the Pyflakes community at large. I will be working hard to improve Frosted further, and any suggestions / feature improvements
recommended will be met with enthusiasm :).
While, I would be willing to merge the two projects at some later
On Sun, Jan 19, 2014 at 9:50 AM, timothy crosley <timothy.crosley@gmail.com> wrote: that are point, I
think in the short-term the rapid development and freedom working under a new project name will bring - will be very beneficial. I have added Florent Xicluna and Steven Myint as collaborators on the project, as these are both developers I have high regard for, and remove the possibility of me being the single source of failure for unmerged pull-requests.
So if you have time, please check out the project, request features, and make pull requests. Lets make a great Python code checker even better!
Thanks!
Timothy
_______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality
Just released version 1.1.0 which categorizes as suggested, and includes many other community driven improvements. Thanks! Tim On Sun, Jan 19, 2014 at 12:00 PM, timothy crosley <timothy.crosley@gmail.com
wrote:
Hi Ian,
I do plan on maintaining this fork, and I had just subscribed and verified my email. I'm not sure why it still required moderation - is there a waiting period? Different subscription modes?
In any case, Thanks for the helpful feedback! I will implement this conceptual error codes, as I agree it is more logical and standard. I am following semantic versioning so it will mean incrementing to new major version - but it shouldn't be too big of a deal as frosted does not yet have a large group of users.
Thanks!
Timothy
On Sun, Jan 19, 2014 at 11:35 AM, Ian Cordasco <graffatcolmingov@gmail.com
wrote:
If you're going to continue to maintain this fork you should join the mailing list so your messages do not need to be moderated.
That said, I have a few points of feedback for you:
Error numbers in tools such as pep8 and pyflakes (although flake8 adds them to pyflakes) are usually not made to be entirely successive. For the most part, there are groupings of errors. The best explanation of this is pep8's documentation: http://pep8.readthedocs.org/en/latest/intro.html#error-codes
Anything starting with E1 is related to indentation, anything starting with E2 is related to whitespace. These are conceptually classes of errors. PyLint also follows this convention if I remember correctly and you would do well to do the same. The error codes that Flake8 adds to PyFlakes follow that convention as well.
This probably also means that if you're following semver that this will be a new major version bump since you're changing how items are ignored.
Hi Everyone,
I just wanted to let you know, after Pyflakes seemed dead for about 5 months I created a fork called Frosted:
https://github.com/timothycrosley/frosted
While it seems that Pyflakes is somewhat alive again, In the fork a lot of code has been simplified and a lot of necessary but missing features (such as configuration) have been added. Additionally, I've merged in a lot of improvements from the Pyflakes community at large. I will be working hard to improve Frosted further, and any suggestions / feature improvements
recommended will be met with enthusiasm :).
While, I would be willing to merge the two projects at some later
On Sun, Jan 19, 2014 at 9:50 AM, timothy crosley <timothy.crosley@gmail.com> wrote: that are point, I
think in the short-term the rapid development and freedom working under a new project name will bring - will be very beneficial. I have added Florent Xicluna and Steven Myint as collaborators on the project, as these are both developers I have high regard for, and remove the possibility of me being the single source of failure for unmerged pull-requests.
So if you have time, please check out the project, request features, and make pull requests. Lets make a great Python code checker even better!
Thanks!
Timothy
_______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality
Hello, this was interesting to me: Error numbers in tools such as pep8 and pyflakes (although flake8 adds
them to pyflakes) are usually not made to be entirely successive. For the most part, there are groupings of errors. The best explanation of this is pep8's documentation: http://pep8.readthedocs.org/en/latest/intro.html#error-codes
Anything starting with E1 is related to indentation, anything starting with E2 is related to whitespace. These are conceptually classes of errors. PyLint also follows this convention if I remember correctly and you would do well to do the same. The error codes that Flake8 adds to PyFlakes follow that convention as well.
So for my compiler Nuitka, there are very few warnings so far, mostly because it is very limited in its tracing abilities, but I am expanding this now, and so far I was kind of clueless on how to properly format error and warning messages. It probably will a while, before I find the need to expand it, but it would be good to have a common ground, reusable data. For PyLint, these texts seem spread out in the variables files. Is there an easy way to access the PyLint warning/error message texts. Would you be OK with me to grep these out of PyLint or Wiki, and use them under ASF2 in my project as well. I would of course prefer, for these to exist a place that makes reuse easier. Basically, I am saying, why isn't this some kind of standard. And can we make it one. Yours, Kay
On 19 janvier 18:12, Kay Hayen wrote:
Hello,
Hi,
Error numbers in tools such as pep8 and pyflakes (although flake8 adds
them to pyflakes) are usually not made to be entirely successive. For the most part, there are groupings of errors. The best explanation of this is pep8's documentation: http://pep8.readthedocs.org/en/latest/intro.html#error-codes
Anything starting with E1 is related to indentation, anything starting with E2 is related to whitespace. These are conceptually classes of errors. PyLint also follows this convention if I remember correctly and you would do well to do the same. The error codes that Flake8 adds to PyFlakes follow that convention as well.
So for my compiler Nuitka, there are very few warnings so far, mostly because it is very limited in its tracing abilities, but I am expanding this now, and so far I was kind of clueless on how to properly format error and warning messages.
It probably will a while, before I find the need to expand it, but it would be good to have a common ground, reusable data. For PyLint, these texts seem spread out in the variables files.
Is there an easy way to access the PyLint warning/error message texts. Would you be OK with me to grep these out of PyLint or Wiki, and use them under ASF2 in my project as well. I would of course prefer, for these to exist a place that makes reuse easier.
Basically, I am saying, why isn't this some kind of standard. And can we make it one.
as Pylint author I would say it's fine by me but warn that in Pylint we're slowly but surely moving from numercial ids (E0601, W0402...) to symbolic ids (bad-indent, bad-name) which carry slightly less information but are much more easy to read and remember. -- Sylvain Thénault, LOGILAB, Paris (01.45.32.03.12) - Toulouse (05.62.17.16.42) Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services CubicWeb, the semantic web framework: http://www.cubicweb.org
Hello, first, thank you Timothy for your interest in Pyflakes. Unfortunately I did not have time to look at Frosted yet. In the first quarter of 2013, I took over the maintenance of Pyflakes, and I did merge the various contributions into the mainstream repository. At the same time, I helped Ian to prepare the new version of Flake8 while making it easier to anyone to write custom extensions. This was released as Flake8 2.0 which leverages the extension mechanism of the pep8 tool. Sadly, for the past 6 months I did have not enough time to prepare a new release of Pyflakes. I wish I have some time available soon, and I can review more PRs. For Pyflakes, I give priority on stability, reliability and compatibility over new features, though. As an example, I will probably turn off the feature for doctest checking by default, because people found it a bit disruptive for their existing code bases : https://bugs.launchpad.net/pyflakes/+bug/1223150 With the latest developments in Flake8, the recommended path to implement a new feature is to write an extension. Some documentation here: http://flake8.readthedocs.org/en/latest/extensions.html And see also examples on PyPI (pep8-naming, mccabe, flake8-docstrings). For the record, there's a numbers' policy for the codification of Flake8 warnings, which complements the pep8 list: http://flake8.readthedocs.org/en/latest/warnings.html You will find codes for the Pyflakes tool on this page too. Thank you again for your involvement in the development of Frosted. In one way or another, it will benefit to Pyflakes and the Flake8 tool too. -- Florent 2014/1/19 Ian Cordasco <graffatcolmingov@gmail.com>:
If you're going to continue to maintain this fork you should join the mailing list so your messages do not need to be moderated.
That said, I have a few points of feedback for you:
Error numbers in tools such as pep8 and pyflakes (although flake8 adds them to pyflakes) are usually not made to be entirely successive. For the most part, there are groupings of errors. The best explanation of this is pep8's documentation: http://pep8.readthedocs.org/en/latest/intro.html#error-codes
Anything starting with E1 is related to indentation, anything starting with E2 is related to whitespace. These are conceptually classes of errors. PyLint also follows this convention if I remember correctly and you would do well to do the same. The error codes that Flake8 adds to PyFlakes follow that convention as well.
This probably also means that if you're following semver that this will be a new major version bump since you're changing how items are ignored.
On Sun, Jan 19, 2014 at 9:50 AM, timothy crosley <timothy.crosley@gmail.com> wrote:
Hi Everyone,
I just wanted to let you know, after Pyflakes seemed dead for about 5 months I created a fork called Frosted:
https://github.com/timothycrosley/frosted
While it seems that Pyflakes is somewhat alive again, In the fork a lot of code has been simplified and a lot of necessary but missing features (such as configuration) have been added. Additionally, I've merged in a lot of improvements from the Pyflakes community at large. I will be working hard to improve Frosted further, and any suggestions / feature improvements that are recommended will be met with enthusiasm :).
While, I would be willing to merge the two projects at some later point, I think in the short-term the rapid development and freedom working under a new project name will bring - will be very beneficial. I have added Florent Xicluna and Steven Myint as collaborators on the project, as these are both developers I have high regard for, and remove the possibility of me being the single source of failure for unmerged pull-requests.
So if you have time, please check out the project, request features, and make pull requests. Lets make a great Python code checker even better!
Thanks!
Timothy
participants (5)
-
Florent -
Ian Cordasco -
Kay Hayen -
Sylvain Thénault -
timothy crosley