...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
--Guido van Rossum (python.org/~guido)
--
You received
can't run!
Hope this helps. It is important to get this. (Also that no future
runs until you yield something. Futures are buffered in the app's
memory until a yield forces all buffered futures out to the servers.)
--
--Guido van Rossum (python.org/~guido)
--
You received this message because
the other operation.
--
--Guido van Rossum (python.org/~guido)
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-appengine+unsubscr...@googlegroups.com
/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
--Guido van Rossum (python.org/~guido)
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine
, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
--
--Guido van Rossum (python.org/~guido)
--
You received
://groups.google.com/group/google-appengine?hl=en.
--
--Guido van Rossum (python.org/~guido)
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send
:
Hello,
Recursive imports means libraries inside libraries? I have lib as library,
and inside it i have another library called userLib. That's a problem...?
I will try to move to different folders...
El jueves, 17 de enero de 2013 21:43:07 UTC+1, Guido van Rossum escribió:
Recursive imports
-appengine/-/EIhPvR7Q2IUJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
--
--Guido van
(it's in the builtins section). If that does
work, you must configure the appstats shell in your
appengine_config.py for it to work in production, but it should be on
by default in the dev server. (Python only.)
--
--Guido van Rossum (python.org/~guido)
--
You received this message because you
, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
--
--Guido van Rossum (python.org/~guido)
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
--
--Guido van Rossum
.
--
--Guido van Rossum (python.org/~guido)
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr
fine -- however if you were to call much_stuff()
from a tasklet, you'd be in trouble again.
Thanks so much taking the time to answer these questions;
extremely helpful and greatly appreciated.
You're welcome.
--
--Guido van Rossum (python.org/~guido)
--
You received this message because you
Hi ckhan,
I have debugged a similar problem for an internal app once. The root cause
was that they were mixing synchronous and async API calls. In particular,
inside a tasklet they were making a synchronous call. The synchronous call
is run by invoking the event loop recursively; what may
. The best thing to
do is to only ever use it with simple global functions that only takes
simple types (e.g. ints and strings, maybe lists of those) as
arguments.
Thanks again!
-ckhan
On Tuesday, October 30, 2012 12:07:42 PM UTC-7, Guido van Rossum wrote:
Hi ckhan,
I have debugged a similar
No need for threads. Use the async urlfetch API instead.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/Z9Fl1QmJs0YJ.
To post to this group, send
I don't think this has anything to do with the previous thread that had the
same subject.
The problem must be that your ComputedProperty is trying returning a Model
instance. That's unfortunately not supported; ComputedProperty as it is
currently implemented can only support the basic data
On Monday, October 8, 2012 1:28:57 PM UTC-7, Guido van Rossum wrote:
I don't think this has anything to do with the previous thread that had
the same subject.
Apologies, I think you had the same issue, you just got there a different
way.
The problem must be that your ComputedProperty
it possible to do the right thing, not necessarily
the most convenient thing (which would depend on the needs of a
particular app).
Thanks for your time and for heard me.
Regards.
Moisés Belchín.
2012/9/24 Guido van Rossum gu...@google.com
Hi Moises,
I think you may be able to solve
Sorry, the underlying Datastore does not (yet) support nested transactions,
so you cannot nest them at all.
On Monday, September 24, 2012 1:53:43 AM UTC-7, Moises Belchin wrote:
Hi,
In NDB we can use @ndb.transactional(xg=True).
@ndb.transactional(xg=True) can be nested? If yes, how many
property must be indexed if
you want to order by MaqHistMov.idsm desc. If you use limit, offset query
fetch this requirement doesn't exist.
--
--Guido van Rossum (python.org/~guido)
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post
FWIW, this behavior appears to be a bug in NDB. I've filed
http://code.google.com/p/appengine-ndb-experiment/issues/detail?id=210
I'll investigate.
On Wed, Sep 19, 2012 at 4:22 PM, Guido van Rossum gu...@google.com wrote:
On Wednesday, September 19, 2012 8:51:48 AM UTC-7, Moises Belchin wrote
.
Moisés Belchín.
2012/9/20 Guido van Rossum gu...@google.com
On Wednesday, September 19, 2012 8:51:48 AM UTC-7, Moises Belchin wrote:
Hi guys,
I have this query:
q = MyKind.query()
regs = q.fetch(offset = 990, limit = 10) // Returns 10 entities.
If I press next button on my UI:
q
On Wednesday, September 19, 2012 8:51:48 AM UTC-7, Moises Belchin wrote:
Hi guys,
I have this query:
q = MyKind.query()
regs = q.fetch(offset = 990, limit = 10) // *Returns 10 entities.*
If I press next button on my UI:
q = MyKind.query()
regs = q.fetch(offset = 1000, limit = 10) //
You'll probably get more help from StackOverflow.com. You'll need to
provide more info, nobody can help you debug this with just that traceback
information unless they're psychic.
On Sunday, September 9, 2012 10:06:33 AM UTC-7, Richard Arrano wrote:
Hello,
I've been using webtest to unit
I'll just fix this. (If you already filed a bug tell me the URL.)
On Sunday, August 26, 2012 4:30:33 PM UTC-7, Anand Mistry wrote:
Yes. Please file a bug.
On Monday, 27 August 2012 04:05:52 UTC+10, Attila-Mihaly Balazs wrote:
I believe that the following example is incorrect in the
The default=[] is causing this. All instances share the same list object
this way. You'll have to find some other way of initializing the value.
Maybe you cna just use a repeated string property?
On Saturday, July 28, 2012 11:56:46 AM UTC-7, Robert Fischer wrote:
Hi,
I'm creating a new
support for Firepython in appstats?
--
--Guido van Rossum (python.org/~guido)
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email
On Monday, July 9, 2012 4:28:30 PM UTC+2, pdknsk wrote:
I don't know if it's documented, but it was mentioned in the release
notes.
The Datastore API now includes a NonTransactional decorator to ensure
that a function is run outside of a transaction. Existing transactions
are paused
On Wednesday, July 4, 2012 1:59:49 AM UTC+2, mma wrote:
Hi there.
I get the following error only on production: BadRequestError: BLOB,
ENITY_PROTO or TEXT properties must be in a raw_property field
It happens when I put() a instance of the Receipt class (extends ndb.Model)
Below, I
I'm sorry, I don't understand. What function do you believe is missing in
NDB?
On Monday, July 2, 2012 11:51:37 AM UTC+2, saintthor wrote:
thank you.
and, don't you think ndb need this function too?
在 2012年7月2日星期一UTC+8上午3时14分36秒，Guido van Rossum写道：
That has nothing to do with ndb; none
That has nothing to do with ndb; none of those would work with db either.
The correct query has WHERE __key__ = KEY().
On Sunday, July 1, 2012 5:38:00 PM UTC+2, saintthor wrote:
ndbModel( id = 'KeyName' ).put()
SELECT * FROM ndbModel where key_name=KEY( 'dbModel', 'KeyName' )
SELECT
On Sunday, June 24, 2012 5:40:15 AM UTC-7, saintthor wrote:
are there a more ops for the StructuredProperty?
StructuredProperty is essentially just a bunch of properties with funny
names. The cost depends on how many indexed properties you have in total in
an entity (including in structured
/1AefylbadN456_Z7BZOpZEXDq8cR8LYu7QgI7bt5V0Iw/edit
--Guido van Rossum
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/bJ7f0jQC9WAJ.
To post to this group, send email to google
This seems a repeat from a post made yesterday. The solution was a bug in
user code that wasn't detected by NDB before; the user write SELECT var
instead of SELECT *.
On Tuesday, June 19, 2012 2:27:16 PM UTC-7, erineg1 wrote:
NDB Team--
It appears something happened today as I had some code
you please submit this to stackoverflow, with more details
about what your code looks like and so on, so someone can help you?
--Guido van Rossum
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
='zzz').put()
--Guido van Rossum
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/8alD7GxEKV4J.
To post to this group, send email to google-appengine
On Tuesday, April 24, 2012 3:07:35 PM UTC-7, Richard Arrano wrote:
Thank you for the quick and very informative reply. I wasn't even
aware this was possible with NDB. How would those x.yref.get() calls
show up in AppStats? Or would they at all if it's just pulling it from
memory?
If
On Monday, April 23, 2012 10:21:26 PM UTC-7, Richard Arrano wrote:
I'm switching from db to ndb and I have a question regarding caching:
In the old db, I would have a class X that contains a reference to a
class Y. The Y type would be accessed most frequently and rarely
change. So when I
and ent.key.id():
# It has a complete key.
else:
# Hasn't been written, ever.
However this can be fooled if you explicitly set the key or the id when you
create an entity, e.g.
ent = Employee(id='joe')
or
ent = Employee(key=ndb.Key(Employee, 'joe'))
(These two are equivalent.)
--Guido van Rossum
again (or at least trying to put them again)
On Mar 27, 2012, at 3:38 PM, Guido van Rossum wrote:
On Tuesday, March 27, 2012 6:41:25 AM UTC-7, aschmid wrote:
is there an equivalent of the db.Model function is_saved() with ndb.Model?
No; what are you trying to do? You might be able to check
you
need is the parent *key*, it doesn't need to have an entity.
--Guido
On Tue, Mar 27, 2012 at 14:47, Andreas a.schmi...@gmail.com wrote:
not a good option in my case.
On Mar 27, 2012, at 5:23 PM, Guido van Rossum wrote:
You might be able to use get_or_insert() and benefit from the in-memory
like is_dirty() which is
True if the entity has never been saved or has changed since it was loaded.
On Tue, Mar 27, 2012 at 3:19 PM, Guido van Rossum gu...@google.com wrote:
Sorry to hear that. I guess you could manually set a flag on the
parent entity that indicates that you haven't written
but the datastore contains a Key
object, which is a structured thing that will never match any string.
--Guido van Rossum
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google
, but an approximation is available in the
sandbox branch of the repo.
--
--Guido van Rossum (python.org/~guido)
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from
?pli=1
Check out the repo: hg clone https://code.google.com/p/appengine-ndb
-experiment/
--
--Guido van Rossum (python.org/~guido)
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine
) these
incompatibilities will hit production when the 1.6.4 SDK goes out
(actually production will see them a few days earlier) so please
review your code, and if possible test with NDB 0.9.9. I also hope
that 1.6.4 will see NDB's experimental label removed -- but no
guarantees!
--
--Guido van Rossum (python.org/~guido
/7b5bb6c8bac1a6b5
--
--Guido van Rossum (python.org/~guido)
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine
On Feb 22, 9:51 pm, Robert Kluin robert.kl...@gmail.com wrote:
On Wed, Feb 22, 2012 at 12:18, Guido van Rossum gu...@google.com wrote:
On Mon, Feb 20, 2012 at 22:46, Robert Kluin robert.kl...@gmail.com wrote:
Some current items on the project list:
- An ext.db mock for unit tests
at
http://groups.google.com/group/google-appengine-python?hl=en.
--
--Guido van Rossum (python.org/~guido)
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
On Jan 25, 9:39 am, someone1 someo...@gmail.com wrote:
On a side note, will
google.appengine.ext.ndb.utils.DEBUG be set to True or False in
production?
It will stay True. However feel free to set it to False in your app
after you've debugged it (your app, that is :-). This will reduce the
tracker: http://code.google.com/p/appengine-ndb-experiment/issues/list
Mailing list / group:
https://groups.google.com/group/appengine-ndb-discuss?pli=1
Check out the repo: hg clone https://code.google.com/p/appengine-ndb-experiment/
--
--Guido van Rossum (python.org/~guido)
--
You received
, this might be how it is
intended to work? I know that normally (without caching), queries
made in a transaction do access the pre-transaction state.
--Amy
--
--Guido van Rossum (python.org/~guido)
--
You received this message because you are subscribed to the Google Groups
Google App
variable
argument list feature which generates a separate argument for each
item in the list.
Good luck with your query!
--Guido van Rossum
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine
at alarming levels.
- Issue 126: Improve repr() of Futures.
- Issue 127: Fix Deadlock error in code that doesn't use @context.toplevel.
--
--Guido van Rossum (python.org/~guido)
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group
.
To unsubscribe from this group, send email to
google-appengine-python+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-python?hl=en.
--
--Guido van Rossum (python.org/~guido)
--
You received this message because you are subscribed
On Tue, Nov 1, 2011 at 12:18, Дмитрий Лисовский lisov...@gmail.com wrote:
And what about threadsafe: true?
You can put it in your app.yaml, but the dev_appserver.py will not handle
multiple requests in parallel, sorry.
--
--Guido van Rossum (python.org/~guido)
--
You received this message
.
For more options, visit this group at
http://groups.google.com/group/google-appengine-python?hl=en.
--
--Guido van Rossum (python.org/~guido)
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google
hits.append(entity)
# Don't do this!
--Guido van Rossum
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr
/datastore/async.html
--Guido van Rossum (not Alfred, but Datastore Plus' author :-)
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email
of tzinfo that has a
reference to a Model instance?
--Guido van Rossum
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google
problems and glad you found a fix already!
--Guido van Rossum
-Joshua
On May 4, 2011, at 10:10 AM, Joshua Smith wrote:
I have some code that has been working for a really long time, that
suddenly started throwing an exception.
In my app, I have to keep some different time zones
...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
--
--Guido van Rossum (python.org/~guido)
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email
One question -- are you defining a main() function? If not, your
entire app may be reloaded each time. Try putting logging statements
(or prints to sys.stderr) at the top-level of your module, and check
in the logs for these -- they should only be logged for the first
request. If they are logged
64 matches
Mail list logo
