I would like to add a link on this topic:
http://www.catb.org/esr/faqs/practical-python-porting/
that provide an extensive overview of possible issues an solutions.
Best regards
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.
Maris Nartiss wrote:
> as you might already have noticed, there is a constant stream of
> issues containing keywords "encoding" or more often
> "UnicodeDecodeError". The main reason behind this is Python 2.x two
> types of text strings - byte sequence (one you get with str()) and
> Unicode (unico
Hi,
2016-02-13 12:13 GMT+01:00 Markus Neteler :
> Agreed. We could change this in trunk (current 7.1.svn) and then
> release it as stable 7.2.
I am confused, I thought that the next stable release will be 7.1. and
not 7.2., in other words some months (let's say two) before planned
release of 7.1.
On Sat, Feb 13, 2016 at 11:30 AM, Maris Nartiss wrote:
...
> Depends on how far is 7.1. I would prefer to have GRASS releases more
> often, then it should go to 7.2.
Agreed. We could change this in trunk (current 7.1.svn) and then
release it as stable 7.2.
Markus
2016-02-10 17:03 GMT+02:00 Anna Petrášová :
>
>
> On Wed, Feb 10, 2016 at 9:42 AM, Moritz Lennert
> wrote:
>>
>> Hi Maris,
>>
>> I would be very happy if we could find a structural solution to this which
>> would avoid having to deal with so many individual errors all the time.
That is my proposal
On Wed, Feb 10, 2016 at 9:42 AM, Moritz Lennert <
mlenn...@club.worldonline.be> wrote:
> Hi Maris,
>
> On 07/02/16 11:56, Maris Nartiss wrote:
>
>> Hello devs,
>> as you might already have noticed, there is a constant stream of
>> issues containing keywords "encoding" or more often
>> "UnicodeDeco
Hi Maris,
On 07/02/16 11:56, Maris Nartiss wrote:
Hello devs,
as you might already have noticed, there is a constant stream of
issues containing keywords "encoding" or more often
"UnicodeDecodeError". The main reason behind this is Python 2.x two
types of text strings - byte sequence (one you ge
Hello devs,
as you might already have noticed, there is a constant stream of
issues containing keywords "encoding" or more often
"UnicodeDecodeError". The main reason behind this is Python 2.x two
types of text strings - byte sequence (one you get with str()) and
Unicode (unicode()). Python 3.x wil
