On 17-01-15 02:32, Nyall Dawson wrote:
Hi,
I'm seeking some clarification on the decisions made during last
nights PSC. Specifically, it looks like it was agreed that LTR
releases would go ahead, but I'm unclear on:
- which release will become LTR?
- will 2.10 become 3.0 and allow API
On 17 Jan 2015 9:19 pm, Richard Duivenvoorde rdmaili...@duif.net wrote:
- I think(!) that slight api changes for composer-code is allowed as
somebody mentioned that that api is not so much used by plugins...
Can this be added to the agenda for the follow up meeting please? To
clarify, it's
Hi,
On Sat, Jan 17, 2015 at 11:19 AM, Richard Duivenvoorde
rdmaili...@duif.net wrote:
- no descision on 3.0 version taken yet
- I think(!) that slight api changes for composer-code is allowed as
somebody mentioned that that api is not so much used by plugins...
As mentioned yesterday, I would
If we are planning on doing a 3.0 I think it really needs to come with
Python 3 and Qt5 on all platforms (We can't have Python 2.7 and Python 3,
that is just going to lead to more pain I think). This is going to break
all the plugins again, are we sure we can do that at this time? If so we
need
On Sat, Jan 17, 2015 at 12:36 PM, Alexander Bruy
alexander.b...@gmail.com wrote:
Agreed with Nathan, 3.0 should come with Pytrhon 3 and Qt5,
or we will have QGIS 4 very soon after QGIS 3
Can you estimate a realistic time plan for these switches to new Python and Qt?
Best wishes,
Anita
If I'm not wrong, support for Qt5 already added by Matthias.
Regarding Python 3, I'm not sure about time plan, as in this
case we depends on OSGeo4W update for Windows platform.
2015-01-17 16:27 GMT+02:00 Anita Graser anitagra...@gmx.at:
On Sat, Jan 17, 2015 at 12:36 PM, Alexander Bruy
Hi!
Depending on the plugin there will surely be a lot of which will not
operate after an update to python3.
And depending on the developer they will be updated or abandoned.
Some will be easy to update - some will be harder to update.
But you are right - if the plugin will NOT be updated we
Thanks Werner,
I was actually thinking of dependencies such as Numpy, Matplotlib, and
other Python packages and whether they will be available for Python 3.
Best wishes,
Anita
On Sat, Jan 17, 2015 at 6:02 PM, Werner Macho werner.ma...@gmail.com wrote:
Hi!
Depending on the plugin there will
Oh - sorry - I did not think of that but:
Numpy Scipy
http://www.scipy.org/scipylib/faq.html#do-numpy-and-scipy-support-python-3-x
matplotlib
http://matplotlib.org/users/whats_new.html
I guess unless you use a _very_ specific module you are safe.
At least I could not find any module I use
Hi all,
Sorry for the long mail but I think it is an important topic.
Increasing the major version number is a rather big step and should be
considered carefully. So before going into too many technical details
(no worries, you find them below) I think it is important to have a
clear idea why we
We have a import hook in place so it would be possible to have just import
PyQt and handle which version is imported on our side however this is a bit
magic and I'm not sure many people would like it. Stuff like this also
breaks tooling because there is no PyQt module so most auto complete will
Right, python 3 has been around long enough the much of the python world
has finally caught up. For those that can't get python 3 they'll just
need to use the last QGIS 2.x release a little longer (there are still
people running 1.8). Please file a ticket now with OSGeo4w to start
preparing to
On Sun, Jan 18, 2015 at 3:59 AM, Nathan Woodrow madman...@gmail.com wrote:
We have a import hook in place so it would be possible to have just import
PyQt and handle which version is imported on our side however this is a bit
magic and I'm not sure many people would like it. Stuff like this
Got the solution via a tweak
-Generate qgs file
-Generate Legend in a seperate file
-Merge both of them
Sharing the code here.Please let me know if anyone has a better solution.
GenerateQGS.py
http://osgeo-org.1560.x6.nabble.com/file/n5182148/GenerateQGS.py
--
View this
14 matches
Mail list logo
