[Avocado-devel] avocado doesn't see plugins

Thu Jan 7 09:57:18 UTC 2016

Thank all of you for the clarification.

On Wed, Jan 6, 2016 at 7:54 PM, Cleber Rosa <crosa at redhat.com> wrote:

>
>
> ----- Original Message -----
> > From: "Andrei Stepanov" <astepano at redhat.com>
> > To: "Olav Philipp Henschel" <olavph at linux.vnet.ibm.com>
> > Cc: avocado-devel at redhat.com
> > Sent: Wednesday, January 6, 2016 4:26:27 PM
> > Subject: Re: [Avocado-devel] avocado doesn't see plugins
> >
> > Thank you.
> >
> > It would be very nice to have in the documentation few words about
> "python
> > setup.py" process. To understand what is going behind this command. Why
> it
> > is necessary. Just for keeping whole clear picture.
>
> The steps to install Avocado from source are documented here:
>
>
> http://avocado-framework.readthedocs.org/en/0.31.0/GetStartedGuide.html#generic-installation-from-a-git-repository
>
> That includes the "python setup.py" process. Then, simply because it's a
> "get started guide", it should not discuss *why* the steps given are
> necessary.
>
> That was, in turn, documented in the plugins section:
>
>
> http://avocado-framework.readthedocs.org/en/0.31.0/Plugins.html#registering-plugins
>
> Sorry if wasn't crystal clear. We sincerely intended for the process to be
> as smooth as possible, but every single software upgrade can (and usually
> do) bring breakages.
>
> >
> >
> >
> > On Wed, Jan 6, 2016 at 6:30 PM, Olav Philipp Henschel <
> > olavph at linux.vnet.ibm.com> wrote:
> >
> > > I've recently asked about this, the command is:
> > > python setup.py develop --user
> > >
> > >
> > > Olav
> > >
> > >
> > > On 06-01-2016 15:18, Lucas Meneghel Rodrigues wrote:
> > >
> > >> There's a flag to do a user local install instead of system wide,
> > >> which I forgot, but Lukas might remember it.
> > >>
> > >> If you are going to over simplify what was done, yes, we are 'forcing'
> > >> the user to install a pointer for the libraries inside a system wide
> > >> library dir. Now if you use the local install, that will be restricted
> > >> into the user's profile.
> > >>
> > >> I promise this was all done for a good reason. Having plugins
> > >> installed as setuptools entry points is more clear and standard than
> > >> our previous custom method.
> > >>
> > >> Unfortunately, my new job's assignments are leaving me busy, so I have
> > >> limited time to spend with this. I'll try to help by answering and
> > >> delegating tasks, like I just did :)
> > >>
> > >> On Wed, Jan 6, 2016 at 3:03 PM, Andrei Stepanov <astepano at redhat.com>
> > >> wrote:
> > >>
> > >>> Thanks, it helps.
> > >>>
> > >>> Above step definitely breaks system integrity. This is a bit unclear.
> > >>> Why do
> > >>> we install development version into system? Do we have some
> documentation
> > >>> that brings more light on this? Or some policy? Or.... I understand
> that
> > >>> Avocado is under active development, but, Is there some advice for
> > >>> Avocado
> > >>> users? What version should we use and develop for?
> > >>>
> > >>> Spice-qe team uses Avocado from git, mainly because there is no RPMs
> for
> > >>> all
> > >>> OS versions/architectures/releases/betas/alphas/etc that we are
> > >>> interested
> > >>> in.
> > >>>
> > >>> Could you give more information about setup.py step? Do I right
> > >>> understand,
> > >>> that you force us to install avocado into system? Before it NewYear
> it
> > >>> was
> > >>> possible to use Avocado directly from git repo (make links, all this
> > >>> configs), but not now. Did I miss something?
> > >>>
> > >>> Sorry, if I wrote something wrong.
> > >>>
> > >>>
> > >>> On Wed, Jan 6, 2016 at 5:32 PM, Lucas Meneghel Rodrigues <
> > >>> lookkas at gmail.com>
> > >>> wrote:
> > >>>
> > >>>> Did you do:
> > >>>>
> > >>>> python setup.py install
> > >>>> or
> > >>>> python setup.py develop
> > >>>>
> > >>>> In both the avocado source dir and the plugin dir?
> > >>>>
> > >>>> On Wed, Jan 6, 2016 at 2:30 PM, Andrei Stepanov <
> astepano at redhat.com>
> > >>>> wrote:
> > >>>>
> > >>>>> Hello
> > >>>>>
> > >>>>> Any clue about :
> > >>>>>
> > >>>>> pip list | grep stevedore
> > >>>>> stevedore (1.10.0)
> > >>>>>
> > >>>>>
> > >>>>> # ./scripts/avocado vt-bootstrap --vt-type spice --vt-no-downloads
> > >>>>> --vt-update-config
> > >>>>> usage: avocado [-h] [-v] [--config CONFIG_FILE] {} ...
> > >>>>> avocado: error: argument subcommand: invalid choice: 'vt-bootstrap'
> > >>>>> (choose
> > >>>>> from )
> > >>>>> [root at spice-bkr02 avocado]#
> > >>>>>
> > >>>>> # ./scripts/avocado --help
> > >>>>> usage: avocado [-h] [-v] [--config CONFIG_FILE] {} ...
> > >>>>>
> > >>>>> Avocado Test Runner
> > >>>>>
> > >>>>> optional arguments:
> > >>>>>    -h, --help            show this help message and exit
> > >>>>>    -v, --version         show program's version number and exit
> > >>>>>    --config CONFIG_FILE  Use custom configuration from a file
> > >>>>>
> > >>>>> subcommands:
> > >>>>>    valid subcommands
> > >>>>>
> > >>>>>    {}                    subcommand help
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> _______________________________________________
> > >>>>> Avocado-devel mailing list
> > >>>>> Avocado-devel at redhat.com
> > >>>>> https://www.redhat.com/mailman/listinfo/avocado-devel
> > >>>>>
> > >>>>>
> > >>>>
> > >>>> --
> > >>>> Lucas
> > >>>>
> > >>>
> > >>>
> > >>
> > >>
> > > _______________________________________________
> > > Avocado-devel mailing list
> > > Avocado-devel at redhat.com
> > > https://www.redhat.com/mailman/listinfo/avocado-devel
> > >
> >
> > _______________________________________________
> > Avocado-devel mailing list
> > Avocado-devel at redhat.com
> > https://www.redhat.com/mailman/listinfo/avocado-devel
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/avocado-devel/attachments/20160107/60d7cd73/attachment.htm>