Hi,
in GRASS 6, I currently get in
Help -> "About GRASS"
Traceback (most recent call last):
File "/home/neteler/grass64/dist.x86_64-unknown-linux-
gnu/etc/wxpython/lmgr/frame.py", line 741, in OnAboutGRASS
win = AboutWindow(self)
File "/home/neteler/grass64/dist.x86_64-unknown-linux-
gnu/etc/wxpython/gui_core/ghelp.py", line 483, in __init__
lang = '.'.join(locale.getdefaultlocale())
TypeError
:
sequence item 0: expected string, NoneType found
Markus
Hello,
I changed code a bit to not fail so hard in r53238 (6.4) and r53239
(7). Added one extra string 'unknown'
Still sometimes it will report wrong data, as Python's
getdefaultlocale is broken (by design?). On my system it sometimes
returns ('lv_LV', 'ISO8859-13') (as somewhere ISO encoding is set to
be default for lv_LV), still my system doesn't support provided ISO
encoding and attempt to use it in i.e. setlocale would cause only a
failure.
Maris.
2012/9/20 Markus Neteler <neteler@osgeo.org>:
Hi,
in GRASS 6, I currently get in
Help -> "About GRASS"
Traceback (most recent call last):
File "/home/neteler/grass64/dist.x86_64-unknown-linux-
gnu/etc/wxpython/lmgr/frame.py", line 741, in OnAboutGRASSwin = AboutWindow(self)
File "/home/neteler/grass64/dist.x86_64-unknown-linux-
gnu/etc/wxpython/gui_core/ghelp.py", line 483, in __init__lang = '.'.join(locale.getdefaultlocale())
TypeError
:
sequence item 0: expected string, NoneType foundMarkus
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Hi,
2012/9/20 Maris Nartiss <maris.gis@gmail.com>:
I changed code a bit to not fail so hard in r53238 (6.4) and r53239
(7). Added one extra string 'unknown'
is there any reason why you skipped 6.5? It's strange to fix it in
release branch and not in dev branch... It source of problems we have
with inconsistency between relbr64 and devbr6. Too many branches...
(my opinion is still the same, to kill devb6).
Martin
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
Hamish,
do you still need devbr6 (6.5)?
I thought that there was a broad consensus that devb6 (65) is not needed and can be retired
so that we have only 6.4.3 relbr64 and trunk 7.
Helena
On Sep 20, 2012, at 4:12 AM, Martin Landa wrote:
Hi,
2012/9/20 Maris Nartiss <maris.gis@gmail.com>:
I changed code a bit to not fail so hard in r53238 (6.4) and r53239
(7). Added one extra string 'unknown'is there any reason why you skipped 6.5? It's strange to fix it in
release branch and not in dev branch... It source of problems we have
with inconsistency between relbr64 and devbr6. Too many branches...
(my opinion is still the same, to kill devb6).Martin
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Yes, there is. Lack of disk space for 6.5 checkout and lack of time to make one.
Maris.
is there any reason why you skipped 6.5?
Martin
2012/9/21 Maris Nartiss <maris.gis@gmail.com>:
Yes, there is. Lack of disk space for 6.5 checkout and lack of time to make one.
hm, done in r53260 to avoid that this fix will be lost in the future.
Martin
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
Helena wrote:
Hamish,
do you still need devbr6 (6.5)?
Yes, I do. To me it is very important and serves an invaluable role in
the maintenance of the old stable branch. (which I volunteer to maintain
in the long (long) term, even if lately I've been pulled away by other
responsibilities and a bit slack about keeping up with it)
thanks,
Hamish
On Mon, Oct 1, 2012 at 12:14 PM, Hamish <hamish_b@yahoo.com> wrote:
Helena wrote:
Hamish,
do you still need devbr6 (6.5)?
Yes, I do. To me it is very important and serves an invaluable role in
the maintenance of the old stable branch.
This is not clear to me.
(which I volunteer to maintain
in the long (long) term, even if lately I've been pulled away by other
responsibilities and a bit slack about keeping up with it)
.. this is exactly the problem - we don't have the resources to keep
6.5.svn in sync. As of today, there are major (!) differences due to
incomplete back- or forward porting. I did the cleanup job for a few
years, but I am getting tired of maintaining 6.5 for nothing.
Markus
2012/10/1 Hamish <hamish_b@yahoo.com>:
the maintenance of the old stable branch. (which I volunteer to maintain
in the long (long) term, even if lately I've been pulled away by other
responsibilities and a bit slack about keeping up with it)
you are probably only one who wants to keep devbr6 alive (please
correct me if needed). To maintain - it means that you will backport
all commits from relbr64 to devbr6? Well, I am not serious, it will
not work. Probably we should vote about devbr6, you can always keep it
as your private branch somewhere...
Martin
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa