Author of the Python autocompletion framework Jedi and its VIM-plugin jedi-vim.
I love Python, PostgreSQL, Vim, Linux and Bash.
If you are interested in my work, follow me on github.
|
May
13 |
|
awarded | Benefactor |
|
May
13 |
|
comment |
Using py.test with coverage doesn't include imports As discussed on github (github.com/davidhalter/jedi/pull/214) you'll get the bounty, because you gave me the right idea. however, this didn't work. |
|
May
13 |
|
accepted | Using py.test with coverage doesn't include imports |
|
May
13 |
|
answered | Using py.test with coverage doesn't include imports |
|
May
13 |
|
comment |
Vim autocomplete for Python Yes, I'm sorry for that. But that's a VIM problem (old version): github.com/davidhalter/jedi-vim/issues/27 |
|
May
12 |
|
comment |
Using py.test with coverage doesn't include imports This is our __init__.py github.com/davidhalter/jedi/blob/master/jedi/__init__.py
|
|
May
11 |
|
revised |
Using py.test with coverage doesn't include imports added 85 characters in body |
|
May
11 |
|
awarded | Promoter |
|
May
7 |
|
comment |
Using py.test with coverage doesn't include imports Yes. We have a conftest.py. It indirectly imports jedi. However, moving these indirect imports into the functions, also didn't help (or is that also a problem???). The file is here: github.com/davidhalter/jedi/blob/master/test/conftest.py
|
|
May
6 |
|
awarded | Yearling |
|
May
6 |
|
asked | Using py.test with coverage doesn't include imports |
|
Apr
30 |
|
awarded | Popular Question |
|
Apr
29 |
|
awarded | Revival |
|
Apr
19 |
|
awarded | Necromancer |
|
Apr
17 |
|
awarded | Nice Answer |
|
Mar
28 |
|
awarded | Popular Question |
|
Mar
23 |
|
awarded | Popular Question |
|
Mar
22 |
|
awarded | Nice Question |
|
Mar
21 |
|
awarded | Revival |
|
Mar
17 |
|
awarded | Nice Answer |
