This approach sounds right. the first step is to recognize plugins placed in ~/.spyder2 as copying files here is easy (I know, PR wanted ^^). The dialog would be nice but is not fundamental.
Yeah, my plugins have roughly the same functionnality, but I still think they add some value ! :) The line profiler could be especially useful for people coming from matlab as the ouput is closer to the matlab profiler. In scientific scripts it is very common that a single line takes the most time. Anyway if there's a simple way to install them they don't need to be included in spyder by default. I'll work on my unittest plugin, I promise ! But I'll be quite busy till next year so it will have to wait... Le mardi 10 décembre 2013 03:58:06 UTC+1, Carlos Córdoba a écrit : > > After a bit more thought I came to see that the right approach is the one > followed by Ninja-IDE: > > 1. Create a plugin index in Bitbucket. > > 2. Make Spyder read that index over the web and offer a dialog with the > list of available ones. > > 3. From that dialog the user should be also able to download, install and > uninstall a selected plugin (which we would save in ~/.spyder2) > > It doesn't seem that hard to do but definitely not for 2.3. > > Cheers, > Carlos > > El 09/12/13 12:14, Carlos Córdoba escribió: > > Hi Joseph, > > I'm very interested in including your unit tests plugin. It sounds really > cool! I'm not so sure about the others because they seem to provide kind of > the same functionality that our pep8 warnings and profiler plugin already > do. If you want to maintain them as separate plugins that's fine for us but > then we have to give you the opportunity to make them at least pip > installable. > > I'm not so sure how to do that (perhaps by making spyderplugins a > namespace package?) but we have to definitely solve this situation for all > plugin authors. > > Cheers, > Carlos > > El 04/12/13 08:12, Joseph Martinot-Lagarde escribió: > > So I wrote 2 plugins for spyder right now > (autopep8<https://github.com/Nodd/spyder_autopep8>and line > profiler <https://github.com/Nodd/spyder_line_profiler>, and I have a > quick draft for running unit > tests<https://github.com/Nodd/spyder_unittesting>), > and I wonder how I should try to get them integrated in spyder. I see 2 > options, which may change the way future plugins are managed : > > - Merge them in the official spyder repo. This means that they will > need to be maintained by spyder's team (with the help of any contributor > on > bitbucket including me, of course). > - Keep them separate the eclipse way. In this case there need to be a > way to install them in user space rather than in spyder's directory. A > page > listing available plugins somewhere on the wiki would help discovering > them. > > Now that the developpement is in bitbucket I'd prefer the first solution, > but it depends on how you see the future of spyder ! > -- > 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] <javascript:>. > To post to this group, send email to [email protected]<javascript:> > . > Visit this group at http://groups.google.com/group/spyderlib. > For more options, visit https://groups.google.com/groups/opt_out. > > > > -- 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.
