spyder_line_profiler is now finised, if anyone is willing to test it ! Le vendredi 11 octobre 2013 09:24:59 UTC+2, Joseph Martinot-Lagarde a écrit : > > I began a line_profiler plugin, it's on github too : > https://github.com/Nodd/spyder_line_profiler. > It is not complete yet but the backend is already there. Any comment or > help is welcomed ! > > Le mardi 8 octobre 2013 16:22:46 UTC+2, Joseph Martinot-Lagarde a écrit : >> >> I did a very simple plugin to use autopep8 from within spyder.You can >> find it on github : https://github.com/Nodd/spyder_autopep8. If is very >> simple : no gui, no config, only a menu entry. It is not complete yet (see >> tracker) but I intent to make another one for line_profiler (starting from >> the profiler plugin) if I can find the time. >> >> I have a question, will it be possible to install plugins in user space >> rather than in a spyder subdirectory, which with a standard installation >> requires root access ? >> >> Le vendredi 16 août 2013 01:10:18 UTC+2, Lucian Smith a écrit : >>> >>> I am trying to get started on writing a plugin or two for Spyder, and >>> I have a few questions. First, I see by searching around that others >>> have been interested in a 'hello world' type plugin example for Spyder >>> in the past, but nobody ever seems to actually have a working copy of >>> one. Do any of you have one you put together? Barring that, the >>> thing to do seems to be to copy and modify the pylint plugin, which >>> can work, but starts off a bit complicated. Are there particular >>> modules inside spyderlib/ that would also work as plugin examples, >>> were they to be renamed and moved to the plugin directory? >>> >>> Second, for anyone doing plugin development, how do you do your >>> debugging? So far, I've been editing the plugin from within Spyder >>> itself, then shutting it down and re-launching (from bootstrap.py). >>> This works OK, but when something goes wrong, the diagnostics are >>> minimal, and I lose my undo/redo history. And I can't run >>> 'bootstrap.py' from another instance of Spyder, since this doesn't >>> seem to do anything (presumably since it sees Spyder is already >>> running). Do you just launch bootstrap.py from a different IDE >>> altogether? Any recommendations? >>> >>> Finally, I am running into a smallish issue, but due to #2 above, I >>> can't figure out what the problem is. If I change this line in >>> p_pylint.py: >>> >>> self.register_shortcut(pylint_act, context="Pylint", name="Run >>> analysis", default="F8") >>> >>> to: >>> >>> self.register_shortcut(pylint_act, context="Pylint", name="Run >>> analysis", default="Ctrl+F9") >>> >>> the shortcut will indeed change to F9. However, if I try other things >>> like: >>> >>> self.register_shortcut(pylint_act, context="Pylint", name="Run >>> analysis", default="Ctrl+F8") >>> >>> And sometimes even changing it to F9 doesn't work, and it keeps the >>> old F8. Is it caching the value somewhere? Is there a way I can step >>> through what's going on? >>> >>> Thank you! >>> >>> -Lucian >>> >>
-- You received this message because you are subscribed to the Google Groups "spyder" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/spyderlib. For more options, visit https://groups.google.com/groups/opt_out.
