Subject | Re: [firebird-python] Re: FDB 0.7.1 working with P2K and P3K |
---|---|
Author | Lester Caine |
Post date | 2012-03-02T08:23:30Z |
philippe makowski wrote:
handled UTF8. The only reason for mentioning it is that some other projects have
created problems when going for major version switches. A crib sheet of thing to
watch out for would be useful ... but one of the reasons Hg has given for not
moving to Python 3 is that the code will not then run on Python 2 so they would
need to maintain both. Add the BC breaks in Smarty3 and some of the
'improvements' now being pushed in PHP5.4 and the whole thing becomes a
minefield. Many of the applications I am running have not changed what they DO
since the early 90's but it is now an up hill struggle keeping them working at
all :( Oh for a simple life with just ONE development language to support ...
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
> Lester Caine [2012-03-01 21:34] :Actually the one thing that the piwik port has dictated is that everything IS
>> > Philippe Makowski wrote:
>>> >> and I "broke" P2K code by adding a default charset to utf8 instead of none
>> >
>> > I can't switch from P2.7 any time soon. None of the other projects that use
>> > Python have any time to do a rewrite for P3 and that is what is unfortunately
>> > required to get them working on P3:(
>> >
> and what is the problem ?
>
> FDB 0.7.1 official release is working with P2K
> I just announced the code is ready to merge to have next relase of FDB
> working with both Python 2 and Python 3
> the "broke" I introduced, can be fix without problem
> it is just that I consider that having "none" as default charset for
> Firebird connection is not a good idea.
handled UTF8. The only reason for mentioning it is that some other projects have
created problems when going for major version switches. A crib sheet of thing to
watch out for would be useful ... but one of the reasons Hg has given for not
moving to Python 3 is that the code will not then run on Python 2 so they would
need to maintain both. Add the BC breaks in Smarty3 and some of the
'improvements' now being pushed in PHP5.4 and the whole thing becomes a
minefield. Many of the applications I am running have not changed what they DO
since the early 90's but it is now an up hill struggle keeping them working at
all :( Oh for a simple life with just ONE development language to support ...
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php