patch submitted here: https://code.google.com/p/web2py/issues/detail?id=1546
note that i had been using cache.ram.flush_all() for clearing GAE
memcache, but that changed to using cache.ram.clear() in this version.
i just updated my source. :)
i also had to tweak my path configs for unit testing, and rename a
module that i had called "utils.py" to work with the new
custom_import.py (my utils module was clashing with gluon/utils.py with
the updated importer).
christian
On 6/18/13 6:36 , Massimo DiPierro wrote:
I did see two problems addressed in a commit today.
gql imports drivers from dal.py but drivers was renamed DRIVERS. If people did
not notice this it means they are not importing gql. This is great. It means
this backward compatibility file can be removed. So I just did.
The second issue is that gae_memcache has an increment method instead of incr,
as expected by memdb. This is now fixed too.
Please submit any patch you may have, even if partial.
massimo
On Jun 18, 2013, at 8:20 AM, Christian Foster Howes wrote:
Carl,
i have been working through my web2py upgrade to 2.5.1 + GAE SDK 1.8.1 upgrade
and am not seeing any problems with DAL or GQL. i did have to change some
cache.ram.flush_all() to cache.ram.clear() to work with the latest web2py, and
am making adjustments to work with the updated custom_import code.
cfh
On 6/18/13 1:57 , Massimo Di Pierro wrote:
None except that some very old web2py GAE applications may be doing "import
gql". It is there only for backward compatibility.
On Tuesday, 18 June 2013 03:21:00 UTC-5, Carl wrote:
hi Massimo,
What would be the implications of removing the gql modulefrom Web2py?
On 12 April 2013 16:17, Massimo Di Pierro <massimo....@gmail.com<javascript:>
wrote:
I proposed in web2py 2.5 we remove the gql module.
On Friday, 12 April 2013 05:21:10 UTC-5, Carl wrote:
Removing the line "from gluon.contrib.gql import *" removed the error
and allows my app to launch.
I next run into this error:
File "F:\wp\TestEnvoy\web2py\gluon\**main.py", line 555, in wsgibase
session._try_store_in_db(**request, response)
File "F:\wp\TestEnvoy\web2py\gluon\**globals.py", line 747, in
_try_store_in_db
record_id = table.insert(**dd)
File "F:\wp\TestEnvoy\web2py\gluon\**contrib\memdb.py", line 256, in
insert
id = self._create_id()
File "F:\wp\TestEnvoy\web2py\gluon\**contrib\memdb.py", line 291, in
_create_id
id = self._tableobj.incr(shard_id)
AttributeError: 'MemcacheClient' object has no attribute 'incr'
One for me to investigate.
On Friday, 12 April 2013 11:06:38 UTC+1, Carl wrote:
has my db.py content fallen out of date?
it includes:
from gluon.sql import SQLCustomType
if request.env.web2py_runtime_**gae: # if running on Google App Engine
from gluon.contrib.gql import *
db = DAL('gae')
On Friday, 12 April 2013 11:00:09 UTC+1, Carl wrote:
actually.. while getting an unknown ticket if I request the url a
second time I get this:
File "F:\wp\TestEnvoy\web2py\**applications\init\models\db.**py",
line 13, in <module>
from gluon.contrib.gql import *
File "F:\wp\TestEnvoy\web2py\gluon\**custom_import.py", line 100,
in custom_importer
return NATIVE_IMPORTER(name, globals, locals, fromlist, level)
ImportError: No module named gql
That's fairly obvious because I've just delete gql.py! :)
On Friday, 12 April 2013 07:48:27 UTC+1, Carl wrote:
If I remove the file (and its .pyc) then I get a web2py "Ticket
issued: unknown"
I'll try upgrading again.
On Friday, 12 April 2013 02:58:27 UTC+1, Massimo Di Pierro wrote:
What if you delete that file?
On Thursday, 11 April 2013 12:31:15 UTC-5, Carl wrote:
With an update to appengine, all is still fine when running web2py
locally.
but if I run dev_appserver then on start-up I get the following
kicked out at the console...
File "F:\wp\TestEnvoy\web2py\gluon\**contrib\gql.py", line 5, in
<module>
from gluon.dal import DAL, Field, Table, Query, Set,
Expression, Row, Rows, *drivers*, BaseAdapter, SQLField, SQLTable,
SQLXorable, SQLQuery, SQLSet, SQLRows, SQLStorage, SQLDB, GQLDB, SQLALL,
SQLCustomType, gae
ImportError: cannot import name *drivers*
*
*
\contrib\gql.py exists for backward compatibility.
This looks like I've tripped up somewhere really simple. Can anyone
point me in the right direction?
--
---
You received this message because you are subscribed to a topic in the
Google Groups "web2py-users" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/web2py/0XH6l1394mA/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to
web2py+un...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
--
---
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/groups/opt_out.
