My steps: 1. Notice bug.
2. Put the /pydal folder from my 2.12.2 version of web2py into my current project. Restart server. It works. 3. Download a .zip of the gluon/packages/DAL directory from github. Replace my 2.12.2 pydal with the new version. Restart server. It fails. Not a lot of room for mistakes. And I've actually tested it a couple different ways since it was easy. New pydal is fscked for GAE unicode support. On Tuesday, March 22, 2016 at 6:07:38 PM UTC-7, Richard wrote: > > pyDAL should be R-2.13.3 : > https://github.com/web2py/web2py/tree/R-2.13.4/gluon/packages > > On Tue, Mar 22, 2016 at 9:05 PM, Richard Vézina <ml.richa...@gmail.com > <javascript:>> wrote: > >> How do you manage your web2py update? Could it happen that you get it >> from github and upgrade pydal package with a version different from the one >> used by web2py 2.13.4? >> >> Can you check you version of pyDAL? >> >> On Tue, Mar 22, 2016 at 8:12 PM, <webm...@trytha.com <javascript:>> >> wrote: >> >>> You think this is a game? >>> >>> So... I just ran into another UNFATHOMABLY, INCONCEIVABLY MASSIVE BUG >>> in the newer PyDAL (i.e. 2.13.4 AND 2.14.1b vs my trusted 2.12.2 version). >>> It doesn't remember how to write unicode to the DB now: >>> >>> ERROR 2016-03-22 23:04:47,468 restricted.py:174] Traceback (most >>> recent call last): >>> >>> ... >>> >>> UnicodeEncodeError: 'latin-1' codec can't encode characters in position >>> 129-132: ordinal not in range(256) >>> >>> It's trying to add Japanese characters to my DB in a row defined simply >>> as 'string'. Worked fine in 2.12.2... >>> >>> Let me be clear, this was using 2.13.4 cloned from the git repo just a >>> few days ago. I then tried the latest 2.14.1b version with identical >>> failure. Then swapped in my trusted 2.12.2 /pydal directory and everything >>> works fine again. >>> >>> Quit messing with my emotions! Time for another version upgrade!!! >>> >>> (And maybe someone can write a test for DAL that confirms it accepts >>> unicode before anything is committed to master? That's a pretty low-level >>> test, right there... I was amazed when I found Cloud SQL broken >>> (admittedly only on the homepage version of the source (not that it's good >>> to have variation in SAME-VERSION code)), but this makes me worry about the >>> framework at a very basic level. I mean, I got the impression Web2py was >>> big in Europe, where ASCII is not the standard.) >>> >>> DISCLAIMER: Normally I would make a new test app to confirm it's not >>> something in my code, but I'm trying to code features, not debug >>> frameworks, and since 2.12.2's PyDAL works fine, I'm able to defeat my OCD >>> and talk shit without being absolutely 100% certain I've properly >>> identified the problem. I apologize if I've made some mistake and am >>> getting worked up over nothing. >>> >>> -- >>> Resources: >>> - http://web2py.com >>> - http://web2py.com/book (Documentation) >>> - http://github.com/web2py/web2py (Source code) >>> - https://code.google.com/p/web2py/issues/list (Report Issues) >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "web2py-users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to web2py+un...@googlegroups.com <javascript:>. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
