Hello Nathan,
Personally I think we should still do 2.8, LTR it, and then we can do 3.0 for
the next release.
Breaking the API again without a LTR in place makes me nervous as the 2.0 API
really wasn't that long ago.
+1000 for LTS
I am with you: please, stop to change the api.
If
In my case, on Win 7 64 bit, QGIS 2.6 crashes with minidump each time I quit,
also doing nothing (that is, no project, no file loaded)
It is normal ?
LTS please.
Regards
Roberto
Inviato da iPhone
Il giorno 07/nov/2014, alle ore 14:53, Giovanni Manghi
giovanni.man...@faunalia.pt ha
Hi
QGIS 3 should come with python 3. I don't think that python 3 can be a
smooth transition so this would require us to make QGIS 4 and break
plugins once again.
Qt5 support does not require QGIS 3.
Geometry and Composer(Layout) may need QGIS 3. But then we can as well
just introduce python 3
Hi Roberto,
Can you open a bug report for this.
Please try to start QGIS with --noplugins and see if that makes a change
for you.
Regards
Matthias
On 08.11.2014 09:19, Geodrinx wrote:
It is not vague:
my QGIS 2.6 on Win 7 64 bit crashes ever when exit with a minidump.
I have no plugin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 08/11/2014 09:42, Matthias Kuhn ha scritto:
QGIS 3 should come with python 3. I don't think that python 3 can
be a smooth transition so this would require us to make QGIS 4 and
break plugins once again.
Qt5 support does not require QGIS 3.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Paolo,
Please don't list Qt5 in breakages.
Thank you
Matthias
On 08.11.2014 09:46, Paolo Cavallini wrote:
Il 08/11/2014 09:42, Matthias Kuhn ha scritto:
QGIS 3 should come with python 3. I don't think that python 3 can
be a smooth
Hi,
I realized that the save selection as was moved to save as. I
appreciate that because it reduces clutter in the layer tree context menu.
I wonder if this should be checked by default whenever there is
something selected on the layer? Just like the field calculator checks
only update selected
On 08/11/2014 8:15 pm, Matthias Kuhn matthias.k...@gmx.ch wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Paolo,
Please don't list Qt5 in breakages.
Hi Matthias,
I'm a little confused - I was under the impression that some web related
classes had been removed from qt5 (hence the
Also PyQt4 imports won't work anymore so that would be a break right?
On Sat, Nov 8, 2014, 7:52 PM Nyall Dawson nyall.daw...@gmail.com wrote:
On 08/11/2014 8:15 pm, Matthias Kuhn matthias.k...@gmx.ch wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Paolo,
Please don't
Hi,
The confusion comes from that there are two different things:
* Qt5 compatibility
* Qt5 binaries
The first one is a thing about the QGIS source code (qt5 branch).
The second one is about compiling/packaging.
The first step does not break anything. And allows to deprecate certain
features
On 08/11/2014 9:05 pm, Matthias Kuhn matthias.k...@gmx.ch wrote:
* Introducing Qt5 support in the QGIS source code does not break
anything.
* Your distro actually shipping QGIS {2,3} compiled against Qt5 may
break stuff.
Makes sense now, thanks. However, by Debian removing Qt4, aren't
On 08.11.2014 11:22, Nyall Dawson wrote:
On 08/11/2014 9:05 pm, Matthias Kuhn matthias.k...@gmx.ch
mailto:matthias.k...@gmx.ch wrote:
* Introducing Qt5 support in the QGIS source code does not break
anything.
* Your distro actually shipping QGIS {2,3} compiled against Qt5 may
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 08/11/2014 10:15, Matthias Kuhn ha scritto:
Please don't list Qt5 in breakages.
sorry, maybe I misunderstood, but thought the plugins have to be
somewhat fixed.
All the best.
- --
Paolo Cavallini - www.faunalia.eu
QGIS PostGIS courses:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 08/11/2014 10:18, Matthias Kuhn ha scritto:
Hi,
I realized that the save selection as was moved to save as. I
appreciate that because it reduces clutter in the layer tree
context menu. I wonder if this should be checked by default
whenever
On Sat, Nov 8, 2014 at 8:01 AM, Nathan Woodrow madman...@gmail.com wrote:
Personally I think we should still do 2.8, LTR it, and then we can do 3.0
for the next release.
I agree with a LTS version (what's LTR??? :-) ). It should be
important that the 2.X will not be abbandoned like as the last
On Sat, Nov 8, 2014 at 8:01 AM, Nathan Woodrow madman...@gmail.com wrote:
Personally I think we should still do 2.8, LTR it, and then we can do 3.0
for the next release.
Breaking the API again without a LTR in place makes me nervous as the 2.0
API really wasn't that long ago.
+1 and even
On Sat, Nov 8, 2014 at 11:53 AM, Paolo Cavallini cavall...@faunalia.it wrote:
Il 08/11/2014 10:18, Matthias Kuhn ha scritto:
Hi,
I realized that the save selection as was moved to save as. I
appreciate that because it reduces clutter in the layer tree
context menu. I wonder if this should be
Hi Anita,
On Sat, 08. Nov 2014 at 12:32:52 +0100, Anita Graser wrote:
On Sat, Nov 8, 2014 at 11:53 AM, Paolo Cavallini cavall...@faunalia.it
wrote:
Il 08/11/2014 10:18, Matthias Kuhn ha scritto:
I think this could result in unexpected outcome for the users.
All the best.
Seems like a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry, my message was a bit short. Please read my response to Nyall for
a more complete discussion.
I just want to make sure that there are no rumours that PR1676 [1] would
break anything.
Once that's in place, we can start to check if/where are
Yes, 2.8 LTR is the least we need to do for users that spent time to
update to 2.0.
Matthias
On 08.11.2014 12:27, Anita Graser wrote:
On Sat, Nov 8, 2014 at 8:01 AM, Nathan Woodrow madman...@gmail.com wrote:
Personally I think we should still do 2.8, LTR it, and then we can do 3.0
for the
Hi Matthias,
2014-11-08 9:44 GMT+01:00 Matthias Kuhn matthias.k...@gmx.ch:
Hi Roberto,
Can you open a bug report for this.
I will do soon.
Please try to start QGIS with --noplugins and see if that makes a change
for you.
I just done your test. At this link you find the capture
http://hub.qgis.org/issues/11600
Roberto
2014-11-08 14:04 GMT+01:00 Geo DrinX geodr...@gmail.com:
Hi Matthias,
2014-11-08 9:44 GMT+01:00 Matthias Kuhn matthias.k...@gmx.ch:
Hi Roberto,
Can you open a bug report for this.
I will do soon.
Please try to start QGIS with --noplugins
On Sat, Nov 8, 2014 at 8:16 AM, Geodrinx geodr...@gmail.com wrote:
In my case, on Win 7 64 bit, QGIS 2.6 crashes with minidump each time I
quit, also doing nothing (that is, no project, no file loaded)
It is normal ?
LTS please.
try (backup) and delete the .qgis2 folder, I have seen
Hi,
While working on the test suite and trying to get all tests to pass I
realized that there are a lot of tests that exist in two versions: C++
and python (e.g. composerhtml, atlas composition). The problem with that
is, that they work on the same set of reference images and either one or
the
+1 for LTS (2.6 or 2.8?).
A new API break risks to make users (and plugin developers) quite nervous!
E.G. the coming QEP from Nyall (about Composer refactoring) breaks Composer
gui API, while it should mantain core. This could be included in an LTS
release, while in QGIS 3.0 back compatibility
Giovanni,
try (backup) and delete the .qgis2 folder, I have seen this a lot on
qgis installations where qgis was previously installed, and purging
.qgis2 usually works.
Great !!! :) Now it works.I will test inserting plugins one by
one.
I updated the issue list
Thank you :)
Vote for 2. Python is a lot easier to test in, and no building step.
On Sat, Nov 8, 2014, 11:30 PM Matthias Kuhn matthias.k...@gmx.ch wrote:
Hi,
While working on the test suite and trying to get all tests to pass I
realized that there are a lot of tests that exist in two versions: C++
and
On Sat, Nov 08, 2014 at 02:30:23PM +0100, Matthias Kuhn wrote:
While working on the test suite and trying to get all tests to pass I
realized that there are a lot of tests that exist in two versions: C++
and python (e.g. composerhtml, atlas composition). The problem with that
is, that they
On Sat, Nov 08, 2014 at 03:00:18PM +, Nathan Woodrow wrote:
Vote for 2. Python is a lot easier to test in, and no building step.
Can python tests effectively be used to find memory errors/leaks ?
--strk;
___
Qgis-developer mailing list
try (backup) and delete the .qgis2 folder, I have seen this a lot on
qgis installations where qgis was previously installed, and purging
.qgis2 usually works.
Great !!! :) Now it works.I will test inserting plugins one by
one.
I have not investigated deeply, but in this cases it
Hi Zoltan,
There are many other file formats besides shapes, including many
databases. So people should stop thinking that the universe only circles
around shapefiles.
With these other file formats it is not very common to ship other files
along with the main file.
Why do you think that
Il 08/11/2014 17.26, Giovanni Manghi ha scritto:
try (backup) and delete the .qgis2 folder, I have seen this a lot on
qgis installations where qgis was previously installed, and purging
.qgis2 usually works.
Great !!! :) Now it works.I will test inserting plugins one by
one.
I have
**If I may** +1 for LTS or LTR
Il 08/11/2014 15.09, G. Allegri ha scritto:
+1 for LTS (2.6 or 2.8?).
A new API break risks to make users (and plugin developers) quite nervous!
IMHO as an user myself i think that a working tool is more valuable than
a new tool,
E.G. the coming QEP from
On 9 November 2014 00:30, Matthias Kuhn matthias.k...@gmx.ch wrote:
(1) We could accept these deviations with anomalies or multiple
reference images.
(2) Or we could remove the C++ test in favor of the python test which
will test the same functionality/codepath and the python binding in
I have this error message while using my scripts (no error in 2.4) on my mac
Erreur non interceptée durant l'exécution de l'algorithme
Traceback (most recent call last):
Traceback (most recent call last):
File
I have this error message while using my scripts (no error in 2.4) on my mac
Erreur non interceptée durant l'exécution de l'algorithme
Traceback (most recent call last):
Traceback (most recent call last):
File
36 matches
Mail list logo
