Re: Upgrading from 1.4.20 to 2.0 gives error with values stored as long in database
Ganesh Sittampalam <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.user |
|---|---|
| Message-ID | <[email protected]> |
On 10/11/2021 15:19, Martin Östlund wrote: > I googled and found out that in python2 long integer literals were > indicated with an l or L suffix. In Python 3, ints and longs have been > merged into just int, which functions pretty much like long used to. > > I can see in postgresql that I indeed have values stored with L suffix. I ran into this in a migration a few months ago and just switched to Python2 for the migration. I think in my case the main issue was that the text files produced by export had the "bad" literals, so I was hoping to re-try with Python3 post-migration, but I haven't done it yet. Ganesh _______________________________________________ Roundup-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/roundup-users