On Fri, Feb 1, 2013 at 1:35 PM, Jürgen E. wrote:
> Hi Etienne,
>
> On Fri, 01. Feb 2013 at 13:01:35 -0200, Etienne Tourigny wrote:
>> Is there a way we can make this suggestion visible, other than adding
>> it to the api docs?
>
> There is now. Apparently since python 2.7 all deprecation warnings
Hi Etienne,
On Fri, 01. Feb 2013 at 13:01:35 -0200, Etienne Tourigny wrote:
> Is there a way we can make this suggestion visible, other than adding
> it to the api docs?
There is now. Apparently since python 2.7 all deprecation warnings where
disabled by default. The messages now appear in the
On Fri, Feb 1, 2013 at 12:40 PM, Angus Carr wrote:
> Hi,
>
> I am a plugin developer who was bitten by this API change. It's easily
> worked around with a try...except... structure, but that becomes unneeded
> clutter. I am working on a plugin that I want to work in the future API and
> the stable
On Fri, Feb 1, 2013 at 12:40 PM, Angus Carr wrote:
> Hi,
>
> I am a plugin developer who was bitten by this API change. It's easily
> worked around with a try...except... structure, but that becomes unneeded
> clutter. I am working on a plugin that I want to work in the future API and
> the stable
Hi,
I am a plugin developer who was bitten by this API change. It's easily
worked around with a try...except... structure, but that becomes unneeded
clutter. I am working on a plugin that I want to work in the future API and
the stable API at version 1.8, so right now I need that clutter to make i
On Thu, Jan 24, 2013 at 10:40 AM, Martin Dobias wrote:
> On Thu, Jan 24, 2013 at 1:32 PM, Alexander Bruy
> wrote:
>> Hi Pirmin,
>>
>> as I can see in API docs (using your link) there is a note:
>>
>> Note:
>> This method is deprecated since QGIS 1.8, you should use
>> addMapLayers rather.
>
>
On Thu, Jan 24, 2013 at 01:40:48PM +0100, Martin Dobias wrote:
> On Thu, Jan 24, 2013 at 1:32 PM, Alexander Bruy
> wrote:
> > Hi Pirmin,
> >
> > as I can see in API docs (using your link) there is a note:
> >
> > Note:
> > This method is deprecated since QGIS 1.8, you should use
> > addMapLaye
Hi Pirmin,
On Thu, 24. Jan 2013 at 13:26:36 +0100, Pirmin Kalberer wrote:
> Where exactly is it marked as deprecated? At least not in the API docs [1].
Well, without an explicit comment that might not be too obvious in doxygen as
it only leaves the Q_DECL_DEPRECATED tag in front of the methods (
On Thu, Jan 24, 2013 at 1:32 PM, Alexander Bruy
wrote:
> Hi Pirmin,
>
> as I can see in API docs (using your link) there is a note:
>
> Note:
> This method is deprecated since QGIS 1.8, you should use
> addMapLayers rather.
A bit off-topic, but I find it weird that addMapLayer() method has
be
On 01/24/2013 01:30 PM, Werner Macho wrote:
> There is a lot of outdated, wrong information somewhere in the wiki -
> (including my translation pages as well).
> And I agree that all this things should be either deleted or made
> unavailable to public..
Maybe we could just mark those pages as depre
Hi Pirmin,
as I can see in API docs (using your link) there is a note:
Note:
This method is deprecated since QGIS 1.8, you should use
addMapLayers rather.
Regarding PyQGIS CookBook I agree that it should be updated
to reflect all API changes. But I think it is better to update it after
mergi
Hmm
That reminds me on the consolidation efforts ..
There is a lot of outdated, wrong information somewhere in the wiki -
(including my translation pages as well).
And I agree that all this things should be either deleted or made
unavailable to public..
But who is going to do it? I guess thats the
Hi Alex,
Am Donnerstag, 24. Januar 2013, 10.40:00 schrieb Alexander Bruy:
>
> please note that most of this methods were marked as deprecated for
> a long time. Some of them are deprecated since QGIS 1.6 or even
> earlier.
Where exactly is it marked as deprecated? At least not in the API docs [1
Hi Jürgen,
On 01/24/2013 10:04 AM, Jürgen E. Fischer wrote:
Hi Matthias,
On Thu, 24. Jan 2013 at 09:43:28 +0100, Matthias Kuhn wrote:
Already done in f2029b4ec.
Nice.
How do I need to tag deprecated methods to trigger this?
/Deprecated/ in the .sip
We (or better put Qt) already have that t
Hi Matthias,
On Thu, 24. Jan 2013 at 09:43:28 +0100, Matthias Kuhn wrote:
>> Already done in f2029b4ec.
> Nice.
> How do I need to tag deprecated methods to trigger this?
/Deprecated/ in the .sip
>> We (or better put Qt) already have that too (Q_DECL_DEPRECATED). But there
>> it's a compile tim
Hi Jürgen
On 01/24/2013 09:37 AM, Jürgen E. Fischer wrote:
Hi Matthias,
On Thu, 24. Jan 2013 at 08:59:47 +0100, Matthias Kuhn wrote:
The question is, where and when to communicate it to the developer:
* The MessageLog (why not)
Already done in f2029b4ec.
Nice.
How do I need to tag deprecat
Hi Matthias,
On Thu, 24. Jan 2013 at 08:59:47 +0100, Matthias Kuhn wrote:
> The question is, where and when to communicate it to the developer:
> * The MessageLog (why not)
Already done in f2029b4ec.
Python 2.7 disabled the deprecation warnings by default. But the would have
gone to stderr any
Hi,
Communicating deprecation in a way, the developer will see it sounds
like a good idea and I agree, that a concept to handle this (starting
from 2.0) would make sense.
The question is, where and when to communicate it to the developer:
* The MessageLog (why not)
* stdout/stderr (sounds g
Hi!
I am not sure but I think what Pirmin meant here was that there was no
warning _message_.
We all know that a lot of functions have been declared deprecated since a
very long time. But without knowing or getting a warning message that THIS
function is deprecated, I agree with Pirmin that noone
Hi,
please note that most of this methods were marked as deprecated for
a long time. Some of them are deprecated since QGIS 1.6 or even
earlier.
On Thu, 24 Jan 2013 00:57:26 +0100
Pirmin Kalberer wrote:
> Hi all,
>
> I found the time for an OpenLayers plugin release with merged pull requests
Hi all,
I found the time for an OpenLayers plugin release with merged pull requests
for Stamen map support and fixes for Python API breaks in master branch (See
https://twitter.com/PirminKalberer/status/294226472707715072 for credits).
The second point was quite annoying for many users and mysel
21 matches
Mail list logo
