These are chat archives for spyder-ide/public

13th
May 2019
CAM Gerlach
@CAM-Gerlach
May 13 01:56
@paulgureghian_gitlab No, this has nothing to do with Spyder. That conda env file is just presumably really out of date, as it points to deprecated packages and an obsolete, broken repo URL. Therefore, I recommend you not bother using it and either find a newer version or create one yourself. Thanks and best of luck.
If you want to install the Spyder deps without Spyder, you can just do conda install spyder --only-deps, or use our requirements.txt files.
Rohan
@RohanVB
May 13 22:06
Hi, I wnted to make some changes to the pylint plugin in spyder. Is there a way I can do so and reflect the changes within the same python instance? without exiting spyder every time I make a change
CAM Gerlach
@CAM-Gerlach
May 13 22:09
You mean @jitseniesen 's Spyder-Unittest? Not really to my knowlege, you need to close and reopen Spyder in order to reload it unless you build something bespoke into the plugin itself. But you can control and change things from insider Spyder itself, via the Internal Console, and you certainly can (and should) have two Spyder instances open, one you're using to do the development, and the other one to actually test your changes.
paulgureghian
@paulgureghian_gitlab
May 13 22:55
Is it possible to run Go and / or Julia in Spyder ?
CAM Gerlach
@CAM-Gerlach
May 13 23:04
@paulgureghian_gitlab Go is a compiled language, so it cannot simply just be "run" at all. There have been discussions about adding Julia support, but it would need sustained developer resources with experience in Julia to make it happen, and/or substantial funding to pay people to do the same.
Rohan
@RohanVB
May 13 23:34
Hi @CAM-Gerlach I was actually trying to modify plugin.py and create a user plugin in /.spyder/plugins/ which is my own modified version of pylint. In sublime-text as soon as I make changes to a file containing the plugin, the plugin is reloaded and the changes are reflected. In vim, I just need to re-run PackageInstall by vim-plug and it reloads all the packages.
For spyder I would have to develop on one instance, and close/open the second instance?
CAM Gerlach
@CAM-Gerlach
May 13 23:45

which is my own modified version of pylint

@RohanVB Why not making the changes to the pylint ("Static Code Analysis") plugin directly?

For spyder I would have to develop on one instance, and close/open the second instance?

Essentially, yes, unless you build a mechanism to reload your plugin into it, because Spyder plugins are very different from those in Sublime and Vim. For those editors, plugins are external packages, that can only interface with the editor itself through a certain set of APIs. In Spyder, plugins are first-class modules that can do almost anything that the built-in ones (Editor, Console, Static Code Analysis, Profiler, etc) can, since the built-in ones are actually structured as plugins themselves. Therefore, as a more integral part of Spyder, they can't easily be reloaded without some effort. However, on the other hand, unlike for those other editors, a properly-written plugin can generally function as a stand-alone GUI widget, as do all our internal ones. So, depending on what you're trying to test, you can usually just launch the plugin without the whole Spyder mainwindow (which can be done almost instantly) and play around with it there, as do the vast majority of our unit tests. Only if you need to test its interaction with something else in the Spyder GUI do you really need to launch it inside a full-on Spyder MainWindow (and you can often just Mock what you need to avoid even that, if you're writing unit tests).

That said, with some effort you might be able to code up support for reloading a plugin; it just hasn't been done since is only really useful to plugin developers, and it can be mostly avoided with mocking and good unit tests.