[GRASS-dev] r57990 breaks r.colors colour selector
Maris Nartiss
maris.gis at gmail.com
Tue Oct 15 04:01:54 PDT 2013
Contrary. It's the right way to go. When 3.0 will be released, most
likely it will live for some time in parallel with 2.8 thus we can
request 2.8 even when 3.0 is present. Besides after 3.0 release some
users will have 3.1 installed and the story repeats.
I can't write code now thus I can only suggest to enforce 2.8 and
then, when we are ready, bump to 3.0. It should be made in a way to
easy enable 2.9 enforcement for testing.
Besides - my bug reports about issues with 2.9 were rejected as "it's
a development version".
Just my 0.2
Thanks again, Martin.
Maris.
2013/10/15 Martin Landa <landa.martin at gmail.com>:
> Hi,
>
> 2013/10/15 Maris Nartiss <maris.gis at gmail.com>:
>> The issue is that currently GRASS wxgui is not enforcing wxpython
>> version. On my system I have both - 2.8 and 2.9. As no specific
>> version is requested, python is loading one of them - in my case it's
>> 2.9 (my guess as 2.9>2.8). At least on my system is present wxversion,
>> that allows to select specific wxpython version on load [1].
>
> well, but it will not solve the reported bug. When wxPython 3.0 will
> be released and used across major GNU/Linux distributions, the bug
> will appear again. Martin
More information about the grass-dev
mailing list