Hey all, I would first like to apologize for my complete disappearance from everything related to this list. Between finishing my masters, moving 1000 miles away and starting a new job (before I was even able to acquire domestic internet), I haven't had time for much of anything. In spite of that poor excuse, I'm sprinting on Flake8 today (trying to fix bugs and get other things written), and I wanted community feedback on a few things. First, is there any interest in developing a pylint plugin for Flake8? If so, who's interested in working with me on it. (I doubt we will finish it today, but I'd at least like to start it.) Second, can anyone provide some guidance (or at least opinions) on issue #85 on Flake8's bug tracker[1]. I'm conflicted about using a script to manage which version of python we use and I am quite partial to the method of appending the python version to the executable's name. However, if others have strong opinions on this, I'm quite willing to listen and would love more information. Finally, if there is anyone willing to collaborate with me on issues #95 [2], #97 [3], and #99 [4], I'd heartily appreciate it. To save you a few clicks, here are some summaries of those issues: #95: Generate code quality visualizations akin to: https://github.com/jsoverson/plato #97: Maintainability index based off McCabe, Halstead and SLOC #99: Machine readable output. This can probably take full advantage of pep8 features without needing to do anything special with Flake8. Firehose may also be of interest. [1]: https://bitbucket.org/tarek/flake8/issue/85 [2]: https://bitbucket.org/tarek/flake8/issue/95 [3]: https://bitbucket.org/tarek/flake8/issue/97 [4]: https://bitbucket.org/tarek/flake8/issue/99 Thanks in advance, Ian
Hi Ian, I'm interested in helping out, and #99 looks like the easiest place to get started learning the codebase. I also like the idea of a pylint plugin. Carl On 4 Jul 2013 17:42, "Ian Cordasco" <graffatcolmingov@gmail.com> wrote:
Hey all,
I would first like to apologize for my complete disappearance from everything related to this list. Between finishing my masters, moving 1000 miles away and starting a new job (before I was even able to acquire domestic internet), I haven't had time for much of anything. In spite of that poor excuse, I'm sprinting on Flake8 today (trying to fix bugs and get other things written), and I wanted community feedback on a few things.
First, is there any interest in developing a pylint plugin for Flake8? If so, who's interested in working with me on it. (I doubt we will finish it today, but I'd at least like to start it.)
Second, can anyone provide some guidance (or at least opinions) on issue #85 on Flake8's bug tracker[1]. I'm conflicted about using a script to manage which version of python we use and I am quite partial to the method of appending the python version to the executable's name. However, if others have strong opinions on this, I'm quite willing to listen and would love more information.
Finally, if there is anyone willing to collaborate with me on issues #95 [2], #97 [3], and #99 [4], I'd heartily appreciate it. To save you a few clicks, here are some summaries of those issues:
#95: Generate code quality visualizations akin to: https://github.com/jsoverson/plato #97: Maintainability index based off McCabe, Halstead and SLOC #99: Machine readable output. This can probably take full advantage of pep8 features without needing to do anything special with Flake8. Firehose may also be of interest.
[1]: https://bitbucket.org/tarek/flake8/issue/85 [2]: https://bitbucket.org/tarek/flake8/issue/95 [3]: https://bitbucket.org/tarek/flake8/issue/97 [4]: https://bitbucket.org/tarek/flake8/issue/99
Thanks in advance, Ian _______________________________________________ code-quality mailing list code-quality@python.org http://mail.python.org/mailman/listinfo/code-quality
Hi Ian, On 04 juillet 11:42, Ian Cordasco wrote:
First, is there any interest in developing a pylint plugin for Flake8? If so, who's interested in working with me on it. (I doubt we will finish it today, but I'd at least like to start it.)
On my side, I can't commit to find time to work on this but I would definitly like to have pylint integrated there and I'm willing to help anyone working on it. That would probably be a good opportunity to find common stuff done in pylint and flake8: I'm pretty sure both project may learn from each other on high-level stuff such as message control, ast handling, analysis execution... Pylint has been there for a while and has imo (truly objectivly, of course ;) neat features on that side. Cheers, -- 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
On 09/07/2013 08:36, Sylvain Thénault wrote:
Hi Ian,
First, is there any interest in developing a pylint plugin for Flake8? If so, who's interested in working with me on it. (I doubt we will finish it today, but I'd at least like to start it.) On my side, I can't commit to find time to work on this but I would definitly
On 04 juillet 11:42, Ian Cordasco wrote: like to have pylint integrated there and I'm willing to help anyone working on it. That would probably be a good opportunity to find common stuff done in pylint and flake8: I'm pretty sure both project may learn from each other on high-level stuff such as message control, ast handling, analysis execution... Pylint has been there for a while and has imo (truly objectivly, of course ;) neat features on that side.
Cheers,
Be aware of the licensing issue, though : depending on the way flake8 works (subprocess or import), the GPL license of Pylint could be an issue if the flake8 authors want to stick to MIT. Alexandre
-- Tarek Ziadé | http://ziade.org On Wed, Jul 10, 2013, at 01:25 PM, afayolle wrote:
On 09/07/2013 08:36, Sylvain Thénault wrote:
Hi Ian,
First, is there any interest in developing a pylint plugin for Flake8? If so, who's interested in working with me on it. (I doubt we will finish it today, but I'd at least like to start it.) On my side, I can't commit to find time to work on this but I would definitly
On 04 juillet 11:42, Ian Cordasco wrote: like to have pylint integrated there and I'm willing to help anyone working on it. That would probably be a good opportunity to find common stuff done in pylint and flake8: I'm pretty sure both project may learn from each other on high-level stuff such as message control, ast handling, analysis execution... Pylint has been there for a while and has imo (truly objectivly, of course ;) neat features on that side.
Cheers,
Be aware of the licensing issue, though : depending on the way flake8 works (subprocess or import), the GPL license of Pylint could be an issue if the flake8 authors want to stick to MIT.
Yeah that's an issue indeed. I would like to stick with a BSD-like licence
Alexandre _______________________________________________ code-quality mailing list code-quality@python.org http://mail.python.org/mailman/listinfo/code-quality
On mer. 17 juil. 2013 12:24:46 CEST, Tarek Ziadé wrote:
Yeah that's an issue indeed. I would like to stick with a BSD-like licence
Well, changing the license of a piece of code such as Pylint may not be that easy... There are several different contributors involved, and I'm not certain where main contributors (Logilab / Sylvain) stand on this. -- Alexandre
Le 8/25/13 9:36 AM, afayolle a écrit :
Yeah that's an issue indeed. I would like to stick with a BSD-like licence Well, changing the license of a piece of code such as Pylint may not be
On mer. 17 juil. 2013 12:24:46 CEST, Tarek Ziadé wrote: that easy... There are several different contributors involved, and I'm not certain where main contributors (Logilab / Sylvain) stand on this.
-- Alexandre
maybe we could bind it through the command line to avoid the licence conflict ?
On 25 août 09:36, afayolle wrote:
On mer. 17 juil. 2013 12:24:46 CEST, Tarek Ziadé wrote:
Yeah that's an issue indeed. I would like to stick with a BSD-like licence
Well, changing the license of a piece of code such as Pylint may not be that easy... There are several different contributors involved, and I'm not certain where main contributors (Logilab / Sylvain) stand on this.
Logilab and I prefer to stick to the GPL mostly for philosophical reasons. If it stands to be a limitation to Pylint usage and development, we may change our mind. That being said, as pointed by Alexandre, there as been a lot of contributors to Pylint for the last 10 years, so even if we (Logilab) decided to change the license, it would take some time to do it properly by asking for approval from the main contributors (supposing they would agree on the licence change). -- 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
On Mon, Aug 26, 2013 at 7:50 AM, Sylvain Thénault <sylvain.thenault@logilab.fr> wrote:
On 25 août 09:36, afayolle wrote:
On mer. 17 juil. 2013 12:24:46 CEST, Tarek Ziadé wrote:
Yeah that's an issue indeed. I would like to stick with a BSD-like licence
Well, changing the license of a piece of code such as Pylint may not be that easy... There are several different contributors involved, and I'm not certain where main contributors (Logilab / Sylvain) stand on this.
Logilab and I prefer to stick to the GPL mostly for philosophical reasons. If it stands to be a limitation to Pylint usage and development, we may change our mind. That being said, as pointed by Alexandre, there as been a lot of contributors to Pylint for the last 10 years, so even if we (Logilab) decided to change the license, it would take some time to do it properly by asking for approval from the main contributors (supposing they would agree on the licence change).
I could be entirely wrong here but I think we would be "safe" if we were to keep this as a plugin. Consider the fact that the plugin registers itself with Flake8 upon installation and Flake8 blindly imports it at run-time. With that in mind, we're never explicitly doing anything like `from pylint import (...)` or `from flake8_pylint import (...)` so we're never using the API of either per se. Since we're never actually doing that, I think we're exempt from the GPL's restrictions. The plugin, however, would have to be licensed under the GPL (or another license in the GPL's family). Again, I could be completely wrong, so don't take the above blindly as truth. My memory could very well be faulty at this early of an hour.
Le 8/26/13 3:26 PM, Ian Cordasco a écrit :
On Mon, Aug 26, 2013 at 7:50 AM, Sylvain Thénault <sylvain.thenault@logilab.fr> wrote:
On 25 août 09:36, afayolle wrote:
Yeah that's an issue indeed. I would like to stick with a BSD-like licence Well, changing the license of a piece of code such as Pylint may not be
On mer. 17 juil. 2013 12:24:46 CEST, Tarek Ziadé wrote: that easy... There are several different contributors involved, and I'm not certain where main contributors (Logilab / Sylvain) stand on this. Logilab and I prefer to stick to the GPL mostly for philosophical reasons. If it stands to be a limitation to Pylint usage and development, we may change our mind. That being said, as pointed by Alexandre, there as been a lot of contributors to Pylint for the last 10 years, so even if we (Logilab) decided to change the license, it would take some time to do it properly by asking for approval from the main contributors (supposing they would agree on the licence change). I could be entirely wrong here but I think we would be "safe" if we were to keep this as a plugin. Consider the fact that the plugin registers itself with Flake8 upon installation and Flake8 blindly imports it at run-time. With that in mind, we're never explicitly doing anything like `from pylint import (...)` or `from flake8_pylint import (...)` so we're never using the API of either per se. Since we're never actually doing that, I think we're exempt from the GPL's restrictions. The plugin, however, would have to be licensed under the GPL (or another license in the GPL's family).
Again, I could be completely wrong, so don't take the above blindly as truth. My memory could very well be faulty at this early of an hour.
We can also ask the FSF what's the best practice here I guess. Plugins vs CLI calls sound like quite an edge case
_______________________________________________ code-quality mailing list code-quality@python.org http://mail.python.org/mailman/listinfo/code-quality
On Mon, Aug 26, 2013 at 8:29 AM, Tarek Ziadé <tarek@ziade.org> wrote:
We can also ask the FSF what's the best practice here I guess.
Plugins vs CLI calls sound like quite an edge case
Last time I asked a question along these lines I got neither a friendly nor helpful response. Perhaps if you know someone, you could get a better answer.
afayolle <afayolle.ml@free.fr> writes:
Be aware of the licensing issue, though : depending on the way flake8 works (subprocess or import), the GPL license of Pylint could be an issue if the flake8 authors want to stick to MIT.
What is the issue, exactly? As I understand it, a work licensed under GPL terms can be derived in part from work under different license terms, so long as that license does not impose any further restrictions. Redistribution of the derived work would need to satisfy simultaneously all the license terms of all the parts from which it derives. Is Flake8 distributed under license terms that impose restrictions additional to the GPL? If not, I don't know what the problem is. -- \ 德不孤、必有鄰。 | `\ (The virtuous are not abandoned, they shall surely | _o__) have neighbours.) —孔夫子 Confucius, 551 BCE – 479 BCE | Ben Finney
participants (6)
-
afayolle -
Ben Finney -
Carl Crowder -
Ian Cordasco -
Sylvain Thénault -
Tarek Ziadé