I don't see the warning.
Upgrade your version (pylint is always in motion).


On Sun, Oct 18, 2020 at 3:25 PM Martin Blais <[email protected]> wrote:

> I think the problem is that pylint doesn't grok NamedTuple, but it does
> collections.namedtuple.
> The problem is pylint.
>
>
> On Sun, Oct 18, 2020 at 10:18 AM Ondřej Švec <[email protected]> wrote:
>
>> I have the same problem. I am running Beancount on WSL. Everything
>> installed using pip3 install.
>> Beancount 2.3.2
>> Python 3.8.2
>> Pylint 2.6.0
>>
>> from beancount.core.data import Transaction
>> Transaction() <- Transaction is not callable (py-lint(not-callable).
>> Transaction: NamedTuple
>>
>> However, running bean-extract works like charm, so it's just annoying
>> during development.
>>
>> On Saturday, 17 October 2020 at 21:40:54 UTC+2 Sam Bragg wrote:
>>
>>> Working with the utrade example
>>> <https://github.com/beancount/beancount/blob/master/examples/ingest/office/importers/utrade/utrade_csv.py>,
>>> pylint tells me data.Transaction is not callable
>>>
>>> Snippet from my code:
>>>
>>> from beancount.core import data
>>>
>>> data.Transaction(...)
>>>
>>> If it matters, I am using VSCode and pipenv to manage venvs.
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Beancount" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beancount/d5047dec-7fed-487e-bffe-ce70cb8fb835n%40googlegroups.com
>> <https://groups.google.com/d/msgid/beancount/d5047dec-7fed-487e-bffe-ce70cb8fb835n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/CAK21%2BhObnTskuGCXq7ULCpur_u86us4tnbnWHDmkU4DQw27irg%40mail.gmail.com.

Reply via email to