I don't know what's the ongoing progress on this topic but I think that a
system for the dependencies management should be embedded inside QGIS. I'm
not in favour for a plugin to do that.
Having an integrated pip would be more transparent to the user and the
plugin developers. The developer should
In my opinion, a much simpler and cleaner approach (at least from the point
of view of a normal user), would be to allow, in QGis Windows (standalone
installer), the user not to point to (or not install) an internal Python,
but to refer to an external installation. For instance, to point to a
On Thu, Mar 6, 2014 at 8:11 PM, Mauro Alberti alberti@gmail.com wrote:
In my opinion, a much simpler and cleaner approach (at least from the
point of view of a normal user), would be to allow, in QGis Windows
(standalone installer), the user not to point to (or not install) an
internal
Windows doesn't ship with any version of Python. Yay Windows! So we
bundle our own. I personally don't mind this so much because it's easier
to control the setup if we bundle it.
The main thing here is just including pip and easy_install in all the
windows installs, standalone and
Hi Mauro,
On Thu, 06. Mar 2014 at 11:11:14 +0100, Mauro Alberti wrote:
In my opinion, a much simpler and cleaner approach (at least from the point
of view of a normal user), would be to allow, in QGis Windows (standalone
installer), the user not to point to (or not install) an internal Python,
Hi Jurgen,
On Thu, Mar 6, 2014 at 11:32 AM, Jürgen E. j...@norbit.de wrote:
Python installed via Python(x,y), where there is already a plenty of
modules installed and it is very easy to install/update via
pip/easy_install and so on.
Hi
The only gotcha to this is that different plugins might require different
versions of dependencies. We also toyed around in the past with the idea of
each plugin having its own virtualenv for deps and then linking in the QGIS
provided site_packages dir into that virtualenv too.
Regards
Tim
The only gotcha to this is that different plugins might require different
versions of dependencies. We also toyed around in the past with the idea of
each plugin having its own virtualenv for deps and then linking in the QGIS
provided site_packages dir into that virtualenv too.
This would
or we can manage a
- light way (light in the plugin point of view) with simple requirement.txt
(or whatever)
or a
- robust and idependent way managing virtualenv
or a
- kaos way mixing :)
Luigi Pirelli
On 6 March 2014 13:18, Tim Sutton li...@linfiniti.com wrote:
Hi
The only gotcha to this
Hi,
On Thu, Mar 6, 2014 at 5:18 AM, Tim Sutton li...@linfiniti.com wrote:
Hi
The only gotcha to this is that different plugins might require different
versions of dependencies. We also toyed around in the past with the idea of
each plugin having its own virtualenv for deps and then linking
Hi
On Thu, Mar 6, 2014 at 6:46 PM, Larry Shaffer lar...@dakotacarto.comwrote:
Hi,
On Thu, Mar 6, 2014 at 5:18 AM, Tim Sutton li...@linfiniti.com wrote:
Hi
The only gotcha to this is that different plugins might require different
versions of dependencies. We also toyed around in the past
Hi to all,
I'm trying to realize a little plugin to install python modules on windows
via pip.
In first, I would like make a simple thing:
Run get-pip.py inside the plugin but I encounter two different problem:
What is the shell to call? (Please, don't mind If I point at dufour, is my
qgis
12 matches
Mail list logo
