You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @srusskih thanks for the idea. I wouldn't like to pollute the global settings object in ST with our or settings, except if this setting becomes a kind of standard across other Python-related packages for ST (which I see you're working on with other projects).
That is, I wouldn't want to require the user to put something outside of "django-nose-test" for configuring DjangoNoseTest.
As the middle ground, we could first check if "python" is defined in "django-nose-test", then try to fall-back to "python_interpreter" in settings. This would allow people who use "python_interpreter" for different extensions to have it in one place, while still allowing them to modify only DjangoNoseTest behaviour if they so choose.
I want propose move python out of
django-nose-test
object and rename to python_interpreterIt will makes simple work flow for users how use SublimePythonIDE and SublimeJEDI (srusskih/SublimeJEDI#100)
How this will looks like:
@dobarkod, what you think about that ?
The text was updated successfully, but these errors were encountered: