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.
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
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
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-previou…
Laurent Peuch -- Bram
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:
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,
It looks like I am missing something very basic. Can someone help me point
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
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?