Looking for workaround of the issue with the isort python library
21 views
Skip to first unread message
Satoshi Tanda
Dec 21, 2018, 12:43:24 PM12/21/18
to EditorConfig
Hi,
I am having a hard time to deply .editorconfig for my work project, due to the issue where the isort python library fails to handle the "root" due to it not being under any section.
I am aware of that this is not this project's issue at at all, but am desperately looking for workaround, because the issue has not been taken care of by the author of the library for almost a year. If any of you here has any ideas on workaround this, please let me know.
The obvious idea is not to use the root property, but I would like to avoid this where possible.
Thank you for your help.
Best,
Satoshi
Satoshi Tanda
Dec 21, 2018, 7:24:09 PM12/21/18
to EditorConfig
Hi Hong,
I am attempting to deploy .editorconfig to my work repository where
its the build process involves execution of multiple scripts,
including Pylint. Pylint internally uses isort, and isort finds the
.editorconfig file during its config file discovery step. This results
in exception from isort and eventually, failure of the build process.
Essentially, the issue is a combination of 1) the format of
EditoConfig (specifically, "root" has to be at the global section), 2)
the fact that isort cannot handle the format, and 3) I cannot find
reasonable way to change the build script to avoid 2). The only
option I seem to have is to find workaround by playing with 1). Not
using the "root" property is the obvious answer, but also wondered if
anyone here had the same issue and/or can think of a way to specify
"root" under some section.
I did not find any mention about isort in this mailing list, so I
understand it might not known to anyone here, and also, there might
not be any workaround I can make purely with tweaking contents of
.editorconfig, but I figured I can ask experts here.
I am attempting to deploy .editorconfig to my work repository where
its the build process involves execution of multiple scripts,
including Pylint. Pylint internally uses isort, and isort finds the
.editorconfig file during its config file discovery step. This results
in exception from isort and eventually, failure of the build process.
Essentially, the issue is a combination of 1) the format of
EditoConfig (specifically, "root" has to be at the global section), 2)
the fact that isort cannot handle the format, and 3) I cannot find
reasonable way to change the build script to avoid 2). The only
option I seem to have is to find workaround by playing with 1). Not
using the "root" property is the obvious answer, but also wondered if
anyone here had the same issue and/or can think of a way to specify
"root" under some section.
I did not find any mention about isort in this mailing list, so I
understand it might not known to anyone here, and also, there might
not be any workaround I can make purely with tweaking contents of
.editorconfig, but I figured I can ask experts here.
Best,
Satoshi
Reply all
Reply to author
Forward
0 new messages