| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| | |
It sets testpaths since e5572e9, and it looks like `-vv -s` was left
from debugging Windows failures remotely?!
If `-vv -s` or a variant should be kept, it would better go into
pytest's `addopts` setting - or could be set on CI via `PYTEST_ADDOPTS`.
|
|\ \
| | |
| | | |
Setup coverage
|
| |\ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
- add coverage factor to tox
- report coverage to codecov.io
- configure testpaths for pytest, instead of passing it through tox
command
|
| |/
|/| |
|
|\ \
| | |
| | | |
Fix bug with parsing WrapModes from config file
|
| |/ |
|
|\ \
| | |
| | | |
Fix no_lines_before with empty section
|
| |/
| |
| |
| |
| | |
This fixes "no_lines_before" to also be respected from previous empty
sections.
|
|\ \
| | |
| | | |
Add -rr/--reverse-relative option (issue #417)
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This new option changes the sort order of relative imports. The new default
sort order is from furthest to closest (most dots to least dots):
from ... import a
from ...foo import x
from .. import b
from ..bar import y
from . import c
from .baz import z
With the new -rr/--reverse-relative option, the order of the relative
import *levels* (inter-order) is reversed, but the ordering within each
relative import level (intra-order) remains the same (i.e. normal lexical
order).
from . import c
from .baz import z
from .. import b
from ..bar import y
from ... import a
from ...foo import x
Signed-off-by: Peter Grayson <pete@jpgrayson.net>
|
|\ \
| | |
| | |
| | |
| | | |
blueyed/fix-test_inconsistent_behavior_in_python_2_and_3_issue_479
Fix test_inconsistent_behavior_in_python_2_and_3_issue_479
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
This also failed for me with "future" being installed.
Not sure if it makes sense to keep it in the first place, since isort
appears to require py34 now.
Ref: https://github.com/timothycrosley/isort/issues/479#issuecomment-316235116
|
|\ \
| | |
| | | |
tests: fix default_settings_path
|
| |/
| |
| |
| |
| |
| |
| | |
Restore `chdir` after tests.
This is relevant for when pytest-cov would display coverage in the end,
and would use absolute paths due to this.
|
|\ \
| | |
| | | |
allow named multi_line_import arguments
|
| | | |
|
| | | |
|
| |/ |
|
|\ \
| | |
| | | |
Fix include_trailing_comma docs
|
| |/ |
|
|\ \
| | |
| | | |
Add LRU cache to RequirementsFinder._get_names
|
| | |
| | |
| | |
| | |
| | | |
This is in order to satisfy mypy as the return type should be the same as the
super class.
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This caches the result of the function for future invocations with the same
input, which can massively speed up future invocations if they have the same
input as previous calls.
In the case of this function this happens a lot, and each invocation is quite
expensive as the requirements file is parsed every time.
This gives a quite significant performance boost. I've tried running `isort`
with and without this patch on two different applications on Python 3.7.2 and
one one application the run time drops from 12.67 seconds to 1.3 seconds and
on the other it drops from 28.29 seconds to 2.1 seconds.
This optimisation is similiar to the one which was done for the 4.3.x branch
here: https://github.com/timothycrosley/isort/pull/856.
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
|/| |
|
| |\
| | |
| | | |
Feature/fix windows support
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
as it didn't seem to fix the windows issue
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| | |
| | | |
Add LRU cache to RequirementsFinder._get_files_from_dir
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This caches the result of the function for future invocations with the same
input, which can massively speed up future invocations if they have the same
input as previous calls.
In the case of this function this happens a lot, as it always is tried with all
parent paths in the file system from `isort` starting point.
The "backports.functools_lru_cache" package is used for Python 2 as it doesn't
have the built in `lru_cache` decorator which was added in Python 3.2.
Some benchmarks against a folder with 182 Python files with all finders enabled:
Python 2.7.15: Before 32 seconds, after 4 seconds.
Python 3.7.2: Before 28 seconds, after 2 seconds.
|
| |\
| | |
| | | |
Disable requirements based finders
|
| |/ |
|