Last April I downloaded the latest official stable release (2017-11-14) and
adjusted all my code for Python 3. Unfortunately, two serious bugs in the
streamer and scheduler made return to Python 2.
Both bugs are fixed in Github, but I'm wary of trying it again until it's
better tested on Python
On Thursday, July 19, 2018 at 11:25:28 AM UTC-4, Lisandro wrote:
>
> That was my first thought: in some cases, another request deletes the
> record right in the instant between the execution of the first and second
> line.
> But I thought it wasn't possible because the function runs inside a db
Hi,
I'm trying to run a scheduler process but it fails on:
# python web2py.py -K appname
web2py Web Framework
Created by Massimo Di Pierro, Copyright 2007-2018
Version 2.16.1-stable+timestamp.2017.11.13.23.50.07
Database drivers available: sqlite3, imaplib, pyodbc, pg8000
starting single-schedule
That's awesome.
Em quarta-feira, 18 de julho de 2018 23:37:29 UTC-3, Anthony escreveu:
>
> Do you have tested python3?
>>
>
> Note, we do have passing tests, at least through Python 3.6:
> https://travis-ci.org/web2py/web2py
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Document
Thanks Leonel.
I'm using PostgreSQL, so if that case isn't possible, then I think the
problem could be in the second line, where the code retrieves the record
using row.id:
row.update_record(**data)
row = db.content[row.id] # the problem could be here
row.update_tsv()
Remember yesterday I rea
It should not be possible if your database has proper transactions like
postgresql. If you're using something like mongodb then you're SOL.
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2p
That was my first thought: in some cases, another request deletes the
record right in the instant between the execution of the first and second
line.
But I thought it wasn't possible because the function runs inside a db
transaction. Or could it still happen?
Another thought is that the row.id
Googling that error message, it looks like it could have something to do
with concurrency and the .pyc file for the module. Maybe confirm the module
isn't corrupted, and remove its .pyc file.
Anthony
On Thursday, July 19, 2018 at 2:04:00 AM UTC-4, Dave S wrote:
>
>
>
> On Monday, July 16, 2018
>
> row = db(db.post.author== auth.user.id).select(db.post.ALL,
> orderby=~db.post.created_on, limitby=(0,1)).first()
> reports = row.message if row else None
>
If you are only returning the "message" field, just select the
db.post.message field, no need to use db.post.ALL.
> def sea
On Thursday, July 19, 2018 at 4:26:09 AM UTC-4, Lisandro wrote:
>
> Well, I owe you an apology, because I got confused regarding which app was
> throwing the error and which web2py version was running.
>
> Until recently, I was using a very old web2py version (2.10). This problem
> was happening
Thanks very much - really appreciative.
Lesson: It helps to calmly work through things, regardless of external
pressure
On Wednesday, July 18, 2018 at 9:21:36 PM UTC-5, Anthony wrote:
>
> You're view has this line:
>
> if host_name in myconf.take('domain.name'):
>
> But as the traceback indicate
On Thursday, July 19, 2018 at 12:56:37 AM UTC-7, Maurice Waka wrote:
>
> Team, Anthony, thanks so much for the help.
> Anthony, I believe, I've mentioned this before, in previous questions
> about the other apps. You've helped me a lot and I appreciate very much.
> The current issue is that, I
Some more info, this is the module code:
Post = db.define_table('post',
Field('author', 'reference auth_user',
default=auth.user_id, writable=False, readable=False),
Field('message', 'text', requires=IS_NOT_EMPTY(),
notnull=
Team, Anthony, thanks so much for the help.
Anthony, I believe, I've mentioned this before, in previous questions about
the other apps. You've helped me a lot and I appreciate very much. The
current issue is that, I am developing a system of q&a with the aim of
storing the questions for future mach
14 matches
Mail list logo
