From peter.danecek at ingv.it Sun Mar 13 19:05:42 2016 From: peter.danecek at ingv.it (petr) Date: Mon, 14 Mar 2016 00:05:42 +0100 Subject: [code-quality] question on flake8 @2.5.4: pyflakes version constraint Message-ID: <2FFE3389-EC0E-497D-8734-B6A29BC480D6@ingv.it> Hi, The current flake8 constrains the version of pyflakes to < 1.1 ("pyflakes >= 0.8.1, < 1.1?). Now, pyflakes was updated to 1.1. So could the requirements constraint of flake8 be bumped safely? Thanks! ~petr From graffatcolmingov at gmail.com Mon Mar 14 11:38:13 2016 From: graffatcolmingov at gmail.com (Ian Cordasco) Date: Mon, 14 Mar 2016 10:38:13 -0500 Subject: [code-quality] question on flake8 @2.5.4: pyflakes version constraint In-Reply-To: <2FFE3389-EC0E-497D-8734-B6A29BC480D6@ingv.it> References: <2FFE3389-EC0E-497D-8734-B6A29BC480D6@ingv.it> Message-ID: On Sun, Mar 13, 2016 at 6:05 PM, petr wrote: > Hi, > > The current flake8 constrains the version of pyflakes to < 1.1 ("pyflakes >= 0.8.1, < 1.1?). Now, pyflakes was updated to 1.1. So could the requirements constraint of flake8 be bumped safely? > > Thanks! > ~petr Hi petr, This is planned for flake8 2.6.0. Compatibility is still being tested. There are two pull requests related to this: https://gitlab.com/pycqa/flake8/merge_requests/55 https://gitlab.com/pycqa/flake8/merge_requests/56 When 2.6.0 is being prepared, we will merge those and release the constraint. Cheers, Ian P.S. Sorry for not approving this message sooner. I was out all day yesterday and woke up quite sick. From aayushnaik17 at gmail.com Sat Mar 19 02:33:30 2016 From: aayushnaik17 at gmail.com (Aayush Naik) Date: Sat, 19 Mar 2016 12:03:30 +0530 Subject: [code-quality] Code style detection Message-ID: Hello. I'm working on a project that detects users' code style automatically. Basically, I want a tool that the user will first run on a set of sample files, this tool then will provide certain information which can be used to 'learn' the user's coding style. Can pylint be that tool? That is, can pylint parse through a bunch of files and spit out information like, the 'tab-width' the user has used, or the 'class docstring regex' and other such things? Thank You. Regards, Aayush Naik -------------- next part -------------- An HTML attachment was scrubbed... URL: From graffatcolmingov at gmail.com Sat Mar 19 09:39:42 2016 From: graffatcolmingov at gmail.com (Ian Cordasco) Date: Sat, 19 Mar 2016 08:39:42 -0500 Subject: [code-quality] Code style detection In-Reply-To: References: Message-ID: On Mar 19, 2016 8:29 AM, "Aayush Naik" wrote: > > Hello. > I'm working on a project that detects users' code style automatically. Basically, I want a tool that the user will first run on a set of sample files, this tool then will provide certain information which can be used to 'learn' the user's coding style. Can pylint be that tool? That is, can pylint parse through a bunch of files and spit out information like, the 'tab-width' the user has used, or the 'class docstring regex' and other such things? > Thank You. > > Regards, > Aayush Naik You sound like you want something to generate a baseline of the code base for future runs. I'm not sure if PyLint can do that. Flake8 cannot do that but if you're looking for inspiration, bandit is a static analysis tool that will generate a baseline for a code base. -- Ian -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahirnish at arista.com Wed Mar 23 05:15:48 2016 From: ahirnish at arista.com (Ahirnish Pareek) Date: Wed, 23 Mar 2016 14:45:48 +0530 Subject: [code-quality] Not able to run test_func.py in /test folder Message-ID: Hi, This looks like a very basic question but I am unable to run /test/test_func.py file to check if my changes has broken anything. Following is the error I am seeing. I have Python 2.7.5 installed. >test ahirnish$ chmod +x test_func.py >test ahirnish$ ./test_func.py ./test_func.py: line 16: functional/non regression tests for pylint: No such file or directory ./test_func.py: line 18: import: command not found ./test_func.py: line 19: import: command not found ./test_func.py: line 20: import: command not found from: can't read /var/mail/os from: can't read /var/mail/os.path ./test_func.py: line 25: syntax error near unexpected token `(' ./test_func.py: line 25: `from pylint.testutils import (make_tests, LintTestUsingModule, LintTestUsingFile,' It looks like I am missing something very basic. Can someone help me point out this? Thanks. -- Regards, Ahirnish -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahirnish at arista.com Wed Mar 23 05:22:17 2016 From: ahirnish at arista.com (Ahirnish Pareek) Date: Wed, 23 Mar 2016 14:52:17 +0530 Subject: [code-quality] Not able to run test_func.py in /test folder In-Reply-To: References: Message-ID: Okay, shebang line was missing here. Damn. Even though when I ran it with 'python', i got this - >test ahirnish$ python test_func.py Traceback (most recent call last): File "test_func.py", line 25, in from pylint.testutils import (make_tests, LintTestUsingModule, LintTestUsingFile, ImportError: No module named pylint.testutils Do I need to compile something here? Thanks. On Wed, Mar 23, 2016 at 2:45 PM, Ahirnish Pareek wrote: > Hi, > > This looks like a very basic question but I am unable to run > /test/test_func.py file to check if my changes has broken anything. > > Following is the error I am seeing. I have Python 2.7.5 installed. > > >test ahirnish$ chmod +x test_func.py > >test ahirnish$ ./test_func.py > ./test_func.py: line 16: functional/non regression tests for pylint: No > such file or directory > ./test_func.py: line 18: import: command not found > ./test_func.py: line 19: import: command not found > ./test_func.py: line 20: import: command not found > from: can't read /var/mail/os > from: can't read /var/mail/os.path > ./test_func.py: line 25: syntax error near unexpected token `(' > ./test_func.py: line 25: `from pylint.testutils import (make_tests, > LintTestUsingModule, LintTestUsingFile,' > > It looks like I am missing something very basic. Can someone help me point > out this? > > Thanks. > > -- > Regards, > Ahirnish > -- Regards, Ahirnish -------------- next part -------------- An HTML attachment was scrubbed... URL: From edward.ekelund at axis.com Wed Mar 23 13:09:51 2016 From: edward.ekelund at axis.com (Edward Ekelund) Date: Wed, 23 Mar 2016 17:09:51 +0000 Subject: [code-quality] Pylint: Disable specific warnings for modules in a specific folder Message-ID: <7b2da30a28c948d6b04e84d0d180876a@XBOX03.axis.com> Hi, I would like to disable a set of warnings for modules in a specific folder. Is this possible somehow? If not, can this feature be added? More specifically, we have a folder in our project which contains many function/unit test modules. Some Pylint-warnings, e.g., `invalid-name` and `protected-access` are not helpful in that context, and we would like to be able to disable those checks for all modules in that directory. Also, we would like to avoid adding #-disable boilerplate inside every single file; preferably we would like to add the folder-specific disables in the project's pylintrc-file. Here's my question on Stack Overflow for more context: http://stackoverflow.com/q/36182847/955014 -- Regards, Edward From me at the-compiler.org Wed Mar 23 17:16:09 2016 From: me at the-compiler.org (Florian Bruhin) Date: Wed, 23 Mar 2016 22:16:09 +0100 Subject: [code-quality] Pylint: Disable specific warnings for modules in a specific folder In-Reply-To: <7b2da30a28c948d6b04e84d0d180876a@XBOX03.axis.com> References: <7b2da30a28c948d6b04e84d0d180876a@XBOX03.axis.com> Message-ID: <20160323211609.GQ11428@tonks> Hey! * Edward Ekelund [2016-03-23 17:09:51 +0000]: > I would like to disable a set of warnings for modules in a specific > folder. Is this possible somehow? > > If not, can this feature be added? There's an open issue for it since a while: https://github.com/PyCQA/pylint/issues/618 There was some work on it, but the person who started working on it unfortunately never submitted a pull request :( > More specifically, we have a folder in our project which contains many > function/unit test modules. Some Pylint-warnings, e.g., `invalid-name` > and `protected-access` are not helpful in that context, and we would > like to be able to disable those checks for all modules in that directory. > > Also, we would like to avoid adding #-disable boilerplate inside every > single file; preferably we would like to add the folder-specific > disables in the project's pylintrc-file. Personally I use a script to find my test files (as they don't have __init__.py files because I'm using py.test). That script also adds some disables: https://github.com/The-Compiler/qutebrowser/blob/master/scripts/dev/run_pylint_on_tests.py Florian -- http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From cortex at worlddomination.be Mon Mar 28 11:30:42 2016 From: cortex at worlddomination.be (Laurent Peuch) Date: Mon, 28 Mar 2016 17:30:42 +0200 Subject: [code-quality] release 0.6 of RedBaron, high level parser/modifier of python source file Message-ID: <20160328153042.GA20363@griboiedov> Hello, One year later I've finally made a new release for RedBaron. For those of you that don't know RedBaron, it's a library that allows you to modify you python *source* file with a high level API pretty much like BeautifulSoup with a lot of helper to make this way-harder-than-expected task doable. Life being life, I don't have the same time that I used to have to work on this project, therefor this release mark my decision to now focus on brigging a 1.0 without adding any new big feature but instead focusing on stability, bugfixing and fully support the python 3 grammar (if they stop adding new things all the time). This release also mark the decision of being backward compatible from now one until 2.0. I know that this mailing list is full of "without any free time" people and that this project is quite complicated but I wouldn't be against new contributors :) I'm adding the release notes at the end of this email. Have a nice day, > 0.6 (2016-03-28) > ---------------- > > This release is guaranteed to have a retro-compatible public documented API > from now on until maybe 2.0. > There might be the only exception that if you directly call specific nodes > constructors with FST that this API change, but this is not documented and > simply horribly unpracticable, so I'm expecting no one to do that. > > From now on the focus will be on moving to a stable 1.0 meaning: bugs fixes and > API additions for missing needed features and no more big modifications, this > will be for other releases, the workload is already big enough. > > - BIG improvement on the proxy list merging algorithm, it is not perfect yet (comments aren't handled yet) but it's really a big move forward > - possible retrocompatibility breaking change: from now on the node.find("name") to node.name shortcut ONLY works with possible nodes identifiers. For example node.i_dont_exist_as_an_identifier will raise AttributeError > - new helper method .to_python that wrap ast.literal_eval on compatibile nodes https://redbaron.readthedocs.org/en/latest/other.html#to-python > - breaking: IntNode no longer return an int on .value but a .string instead, use .to_python to have an evaluated version > - fix node.decrease_indentation (that was simply not working) > - fix code_block_node.value was broken on node with no parent > - add string representation for Path object > - now redbaron Path() class can be compared directly to baron paths > without using to_baron_path() helper. > - fix by novocaine: 'function' was used as a function type detector instead of 'def' > - add getitem() method with same api on NodeList and ProxyList > - fix: inconsistencies when inserting lines around code blocks > - inserting a blank lines inserts effectively a \n in a LineProxyList > - new helper methods: .next_recursive and .previous_recursive https://redbaron.readthedocs.org/en/latest/other.html > - fix: doc is tested in CI now, it shouldn't break anymore > - more rendering test for python3, it shouldn't break anymore > - pygments is now an optional dependancy, "pip install redbaron" won't install it, "pip install redbaron[pygments"] will > - new node.next_intuitive and node.previous_intuitive methods for situations where .next/previous doesn't behave the way the user expect it http://redbaron.readthedocs.org/en/latest/other.html#next-intuitive-previous-intuitive -- Laurent Peuch -- Bram From graffatcolmingov at gmail.com Mon Mar 28 12:13:45 2016 From: graffatcolmingov at gmail.com (Ian Cordasco) Date: Mon, 28 Mar 2016 11:13:45 -0500 Subject: [code-quality] release 0.6 of RedBaron, high level parser/modifier of python source file In-Reply-To: <20160328153042.GA20363@griboiedov> References: <20160328153042.GA20363@griboiedov> Message-ID: On Mon, Mar 28, 2016 at 10:30 AM, Laurent Peuch wrote: > Hello, > > One year later I've finally made a new release for RedBaron. For those > of you that don't know RedBaron, it's a library that allows you to > modify you python *source* file with a high level API pretty much like > BeautifulSoup with a lot of helper to make this way-harder-than-expected > task doable. > > Life being life, I don't have the same time that I used to have to > work on this project, therefor this release mark my decision to now > focus on brigging a 1.0 without adding any new big feature but instead > focusing on stability, bugfixing and fully support the python 3 > grammar (if they stop adding new things all the time). This release > also mark the decision of being backward compatible from now one > until 2.0. > > I know that this mailing list is full of "without any free time" > people and that this project is quite complicated but I wouldn't be > against new contributors :) > > I'm adding the release notes at the end of this email. > > Have a nice day, > >> 0.6 (2016-03-28) >> ---------------- >> >> This release is guaranteed to have a retro-compatible public documented API >> from now on until maybe 2.0. >> There might be the only exception that if you directly call specific nodes >> constructors with FST that this API change, but this is not documented and >> simply horribly unpracticable, so I'm expecting no one to do that. >> >> From now on the focus will be on moving to a stable 1.0 meaning: bugs fixes and >> API additions for missing needed features and no more big modifications, this >> will be for other releases, the workload is already big enough. >> >> - BIG improvement on the proxy list merging algorithm, it is not perfect yet (comments aren't handled yet) but it's really a big move forward >> - possible retrocompatibility breaking change: from now on the node.find("name") to node.name shortcut ONLY works with possible nodes identifiers. For example node.i_dont_exist_as_an_identifier will raise AttributeError >> - new helper method .to_python that wrap ast.literal_eval on compatibile nodes https://redbaron.readthedocs.org/en/latest/other.html#to-python >> - breaking: IntNode no longer return an int on .value but a .string instead, use .to_python to have an evaluated version >> - fix node.decrease_indentation (that was simply not working) >> - fix code_block_node.value was broken on node with no parent >> - add string representation for Path object >> - now redbaron Path() class can be compared directly to baron paths >> without using to_baron_path() helper. >> - fix by novocaine: 'function' was used as a function type detector instead of 'def' >> - add getitem() method with same api on NodeList and ProxyList >> - fix: inconsistencies when inserting lines around code blocks >> - inserting a blank lines inserts effectively a \n in a LineProxyList >> - new helper methods: .next_recursive and .previous_recursive https://redbaron.readthedocs.org/en/latest/other.html >> - fix: doc is tested in CI now, it shouldn't break anymore >> - more rendering test for python3, it shouldn't break anymore >> - pygments is now an optional dependancy, "pip install redbaron" won't install it, "pip install redbaron[pygments"] will >> - new node.next_intuitive and node.previous_intuitive methods for situations where .next/previous doesn't behave the way the user expect it http://redbaron.readthedocs.org/en/latest/other.html#next-intuitive-previous-intuitive > > -- > > Laurent Peuch -- Bram > _______________________________________________ > code-quality mailing list > code-quality at python.org > https://mail.python.org/mailman/listinfo/code-quality I'm really happy you sent this. I had forgotten about RedBaron and was going to start looking for a project exactly like it. Would you be interested in moving the project under the umbrella of the PyCQA? We could probably more easily integrate new contributors in an organization. I'll start taking a look at how I could help out with RedBaron since Flake8 will probably start depending on it or something like it. Cheers, Ian From graffatcolmingov at gmail.com Mon Mar 28 12:15:59 2016 From: graffatcolmingov at gmail.com (Ian Cordasco) Date: Mon, 28 Mar 2016 11:15:59 -0500 Subject: [code-quality] release 0.6 of RedBaron, high level parser/modifier of python source file In-Reply-To: References: <20160328153042.GA20363@griboiedov> Message-ID: On Mon, Mar 28, 2016 at 11:13 AM, Ian Cordasco wrote: > I'm really happy you sent this. I had forgotten about RedBaron and was > going to start looking for a project exactly like it. Would you be > interested in moving the project under the umbrella of the PyCQA? We > could probably more easily integrate new contributors in an > organization. I'll start taking a look at how I could help out with > RedBaron since Flake8 will probably start depending on it or something > like it. Of course Baron is also welcome in addition to RedBaron. In particular, I'd love to firm up the Python 3 support (since Flake8 would need that). If you need more PyCQA information, we have some documentation on http://meta.pycqa.org From graffatcolmingov at gmail.com Mon Mar 28 12:35:11 2016 From: graffatcolmingov at gmail.com (Ian Cordasco) Date: Mon, 28 Mar 2016 11:35:11 -0500 Subject: [code-quality] [Social] Who is going to PyCon (US)? Message-ID: Hey everyone, Ian Lee and I were chatting privately and are planning on meeting up at PyCon in Portland. We thought it would probably be a good idea to get a group together for lunch or dinner or something. So, who's going to be there and who wants to plan to meet-up? We don't have to focus our gathering around food, we can plan for a Birds of a Feather meeting instead if that's desirable. We can chat about specific projects, the PyCQA, this list, or whatever. Cheers, Ian From matt at itsmemattchung.com Mon Mar 28 12:49:16 2016 From: matt at itsmemattchung.com (Matt Chung) Date: Mon, 28 Mar 2016 17:49:16 +0100 Subject: [code-quality] [Social] Who is going to PyCon (US)? In-Reply-To: References: Message-ID: <1459183756.2465496.561590378.559C2862@webmail.messagingengine.com> At the moment, I'll be at Pycon between May 28th and the 31st. Would love to join if ya'll plan to meet during those times. Cheers, Matt Chung blog[http://blog.itsmemattchung.com/]?| github[https://github.com/itsmemattchung]?| twitter[https://twitter.com/itsmemattchung]?| linkedin[https://www.linkedin.com/in/matt-chung-32792354] On Mon, Mar 28, 2016, at 05:35 PM, Ian Cordasco wrote: > Hey everyone, > > Ian Lee and I were chatting privately and are planning on meeting up > at PyCon in Portland. We thought it would probably be a good idea to > get a group together for lunch or dinner or something. > > So, who's going to be there and who wants to plan to meet-up? We don't > have to focus our gathering around food, we can plan for a Birds of a > Feather meeting instead if that's desirable. We can chat about > specific projects, the PyCQA, this list, or whatever. > > Cheers, > Ian > _______________________________________________ > code-quality mailing list > code-quality at python.org > https://mail.python.org/mailman/listinfo/code-quality From matt at itsmemattchung.com Mon Mar 28 12:51:03 2016 From: matt at itsmemattchung.com (Matt Chung) Date: Mon, 28 Mar 2016 17:51:03 +0100 Subject: [code-quality] [Social] Who is going to PyCon (US)? In-Reply-To: References: Message-ID: <1459183863.2466746.561592938.3D078565@webmail.messagingengine.com> At the moment, I'll be at Pycon between May 28th and the 31st. Would love to join if ya'll plan to meet during those times. Cheers, Matt Chung blog[http://blog.itsmemattchung.com/]?| github[https://github.com/itsmemattchung]?| twitter[https://twitter.com/itsmemattchung]?| linkedin[https://www.linkedin.com/in/matt-chung-32792354] On Mon, Mar 28, 2016, at 05:35 PM, Ian Cordasco wrote: > Hey everyone, > > Ian Lee and I were chatting privately and are planning on meeting up > at PyCon in Portland. We thought it would probably be a good idea to > get a group together for lunch or dinner or something. > > So, who's going to be there and who wants to plan to meet-up? We don't > have to focus our gathering around food, we can plan for a Birds of a > Feather meeting instead if that's desirable. We can chat about > specific projects, the PyCQA, this list, or whatever. > > Cheers, > Ian > _______________________________________________ > code-quality mailing list > code-quality at python.org > https://mail.python.org/mailman/listinfo/code-quality From thisfred at gmail.com Mon Mar 28 17:22:56 2016 From: thisfred at gmail.com (Eric Casteleijn) Date: Mon, 28 Mar 2016 14:22:56 -0700 Subject: [code-quality] [Social] Who is going to PyCon (US)? In-Reply-To: <1459183863.2466746.561592938.3D078565@webmail.messagingengine.com> References: <1459183863.2466746.561592938.3D078565@webmail.messagingengine.com> Message-ID: I will be at Pycon, and would love to attend such a meeting, though I realize I've only been lurking here so far. I'd like to contribute more though. I live in Portland, so any date is likely to work for me. On Mon, Mar 28, 2016 at 9:51 AM, Matt Chung wrote: > At the moment, I'll be at Pycon between May 28th and the 31st. Would > love to join if ya'll plan to meet during those times. > > > Cheers, > Matt Chung > blog[http://blog.itsmemattchung.com/] | > github[https://github.com/itsmemattchung] | > twitter[https://twitter.com/itsmemattchung] | > linkedin[https://www.linkedin.com/in/matt-chung-32792354] > > On Mon, Mar 28, 2016, at 05:35 PM, Ian Cordasco wrote: > > Hey everyone, > > > > Ian Lee and I were chatting privately and are planning on meeting up > > at PyCon in Portland. We thought it would probably be a good idea to > > get a group together for lunch or dinner or something. > > > > So, who's going to be there and who wants to plan to meet-up? We don't > > have to focus our gathering around food, we can plan for a Birds of a > > Feather meeting instead if that's desirable. We can chat about > > specific projects, the PyCQA, this list, or whatever. > > > > Cheers, > > Ian > > _______________________________________________ > > code-quality mailing list > > code-quality at python.org > > https://mail.python.org/mailman/listinfo/code-quality > _______________________________________________ > code-quality mailing list > code-quality at python.org > https://mail.python.org/mailman/listinfo/code-quality > -- - eric casteleijn -------------- next part -------------- An HTML attachment was scrubbed... URL: From graffatcolmingov at gmail.com Mon Mar 28 18:53:06 2016 From: graffatcolmingov at gmail.com (Ian Cordasco) Date: Mon, 28 Mar 2016 17:53:06 -0500 Subject: [code-quality] [Social] Who is going to PyCon (US)? In-Reply-To: References: <1459183863.2466746.561592938.3D078565@webmail.messagingengine.com> Message-ID: On Mon, Mar 28, 2016 at 4:22 PM, Eric Casteleijn wrote: > I will be at Pycon, and would love to attend such a meeting, though I > realize I've only been lurking here so far. I'd like to contribute more > though. I live in Portland, so any date is likely to work for me. Don't worry about being a "lurker". :-) You'll likely be our source of a location to head to if we can't get a BoF space (which I think will suit us well). I look forward to seeing you, Matt, Ian, and whomever else comes. :-) Cheers, Ian From cortex at worlddomination.be Wed Mar 30 18:02:10 2016 From: cortex at worlddomination.be (Laurent Peuch) Date: Thu, 31 Mar 2016 00:02:10 +0200 Subject: [code-quality] release 0.6 of RedBaron, high level parser/modifier of python source file In-Reply-To: References: <20160328153042.GA20363@griboiedov> Message-ID: <20160330220210.GA6248@griboiedov> Hello, On Mon, Mar 28, 2016 at 11:15:59AM -0500, Ian Cordasco wrote: > On Mon, Mar 28, 2016 at 11:13 AM, Ian Cordasco > wrote: > > I'm really happy you sent this. I had forgotten about RedBaron and was > > going to start looking for a project exactly like it. Would you be > > interested in moving the project under the umbrella of the PyCQA? We > > could probably more easily integrate new contributors in an > > organization. I'll start taking a look at how I could help out with > > RedBaron since Flake8 will probably start depending on it or something > > like it. > > Of course Baron is also welcome in addition to RedBaron. In > particular, I'd love to firm up the Python 3 support (since Flake8 > would need that). > > If you need more PyCQA information, we have some documentation on > http://meta.pycqa.org Thanks a lot for this proposition :) After reading the documentation, I am very tempted to say yes, but I have one small hesitation (not about the CoC, I'm actually quite happy that you have one): PyCQA define itself as "a loose organization of people who maintain projects in roughly the same domain: automatic style and quality reporting" but that's not exactly (red)baron is doing. While it's not very far away (like a low level more general tool that can be used to build those kind of tools), it's still a bit different, won't that be a problem? -- Laurent Peuch -- Bram From graffatcolmingov at gmail.com Wed Mar 30 18:12:00 2016 From: graffatcolmingov at gmail.com (Ian Cordasco) Date: Wed, 30 Mar 2016 17:12:00 -0500 Subject: [code-quality] release 0.6 of RedBaron, high level parser/modifier of python source file In-Reply-To: <20160330220210.GA6248@griboiedov> References: <20160328153042.GA20363@griboiedov> <20160330220210.GA6248@griboiedov> Message-ID: On Wed, Mar 30, 2016 at 5:02 PM, Laurent Peuch wrote: > Hello, > > On Mon, Mar 28, 2016 at 11:15:59AM -0500, Ian Cordasco wrote: >> On Mon, Mar 28, 2016 at 11:13 AM, Ian Cordasco >> wrote: >> > I'm really happy you sent this. I had forgotten about RedBaron and was >> > going to start looking for a project exactly like it. Would you be >> > interested in moving the project under the umbrella of the PyCQA? We >> > could probably more easily integrate new contributors in an >> > organization. I'll start taking a look at how I could help out with >> > RedBaron since Flake8 will probably start depending on it or something >> > like it. >> >> Of course Baron is also welcome in addition to RedBaron. In >> particular, I'd love to firm up the Python 3 support (since Flake8 >> would need that). >> >> If you need more PyCQA information, we have some documentation on >> http://meta.pycqa.org > > Thanks a lot for this proposition :) > > After reading the documentation, I am very tempted to say yes, but I > have one small hesitation (not about the CoC, I'm actually quite happy > that you have one): PyCQA define itself as "a loose organization of > people who maintain projects in roughly the same domain: automatic > style and quality reporting" but that's not exactly (red)baron is > doing. While it's not very far away (like a low level more general > tool that can be used to build those kind of tools), it's still a bit > different, won't that be a problem? Not really. That's a living document and we can amend it to use language that would make (Red)Baron feel more comfortable joining. When I wrote that, I was mostly describing the state of things rather than the future which was a bit silly of me. I feel like RedBaron would be a good fit, especially since I'm not exactly sure astroid on its own can be squeezed into that statement. Maybe we should just remove the "automatic style and reporting" bit to keep it a bit more general? From cortex at worlddomination.be Wed Mar 30 18:44:48 2016 From: cortex at worlddomination.be (Laurent Peuch) Date: Thu, 31 Mar 2016 00:44:48 +0200 Subject: [code-quality] release 0.6 of RedBaron, high level parser/modifier of python source file In-Reply-To: References: <20160328153042.GA20363@griboiedov> <20160330220210.GA6248@griboiedov> Message-ID: <20160330224448.GA26952@griboiedov> On Wed, Mar 30, 2016 at 05:12:00PM -0500, Ian Cordasco wrote: > On Wed, Mar 30, 2016 at 5:02 PM, Laurent Peuch > wrote: > > Hello, > > > > On Mon, Mar 28, 2016 at 11:15:59AM -0500, Ian Cordasco wrote: > >> On Mon, Mar 28, 2016 at 11:13 AM, Ian Cordasco > >> wrote: > >> > I'm really happy you sent this. I had forgotten about RedBaron and was > >> > going to start looking for a project exactly like it. Would you be > >> > interested in moving the project under the umbrella of the PyCQA? We > >> > could probably more easily integrate new contributors in an > >> > organization. I'll start taking a look at how I could help out with > >> > RedBaron since Flake8 will probably start depending on it or something > >> > like it. > >> > >> Of course Baron is also welcome in addition to RedBaron. In > >> particular, I'd love to firm up the Python 3 support (since Flake8 > >> would need that). > >> > >> If you need more PyCQA information, we have some documentation on > >> http://meta.pycqa.org > > > > Thanks a lot for this proposition :) > > > > After reading the documentation, I am very tempted to say yes, but I > > have one small hesitation (not about the CoC, I'm actually quite happy > > that you have one): PyCQA define itself as "a loose organization of > > people who maintain projects in roughly the same domain: automatic > > style and quality reporting" but that's not exactly (red)baron is > > doing. While it's not very far away (like a low level more general > > tool that can be used to build those kind of tools), it's still a bit > > different, won't that be a problem? > > Not really. That's a living document and we can amend it to use > language that would make (Red)Baron feel more comfortable joining. > When I wrote that, I was mostly describing the state of things rather > than the future which was a bit silly of me. I feel like RedBaron > would be a good fit, especially since I'm not exactly sure astroid on > its own can be squeezed into that statement. Maybe we should just > remove the "automatic style and reporting" bit to keep it a bit more > general? Oh, I don't have strong feelings regarding a modification of this document, it was more about the existing group, but if you think it's ok then it's a "yes" from me :) I'll take a look tomorrow about migrating the repositories to the organisation. (ps: I won't be there at pyconUS, too far away, not enough money and time) -- Laurent Peuch -- Bram