Thanks to both of you.
I saw that line in the error ticket but dismissed it since the web2py
access worked, the driver "must be there". Dumb :(
installed pymysql and reran my little test and it did indeed connect but
generated the following:
cursors.py:166:
Warning: (3090, u"Changing sql
Looks like you don't have a Python MySQL driver installed on your system.
It works in web2py because web2py includes pymysql in /gluon/contrib (but
/gluon/contrib is not part of sys.path when running a Python program
outside of the web2py context).
Anthony
On Tuesday, August 8, 2017 at
seen the error you provide seems that there is no mysql driver python
module installed
RuntimeError: No driver of supported ones (\'MySQLdb\', \'pymysql\',
\'mysqlconnector\') is available\n'
perhaps installed mysql python module (using pip or etc) can solve the
problem.
best regards,
stifan
I would have thought so, but it fails !!! What am I missing?
about as basic as can be -
a plain 2-line vanilla python app (with a running mysql db, created with
the same "db = DAL('mysql://root:password@localhost/mfm_curr_lib',
pool_size = 10) " and accessed happily by the web2py app)
On Monday, August 7, 2017 at 4:29:30 PM UTC-7, jim kaubisch wrote:
>
> Hi,
>
> The following failure suddenly started in a piece of code thats been
> running error free for months. I can think of nothing I’ve changed that
> would cause this to happen (famous last words, I know).
> I've tried
Sure, you can access the same database from multiple applications (web2py
or not).
On Tuesday, August 8, 2017 at 6:29:30 PM UTC-4, jim kaubisch wrote:
>
> Thanks, I think you're right. But its working now, so I'll revisit it once
> the delivery heat is off.
>
> Please, on the related topic of
Thanks, I think you're right. But its working now, so I'll revisit it once
the delivery heat is off.
Please, on the related topic of my other post, I'm I missing something by
thinking I should be able to access the SAME mysql db both from web2py as
well as a standard Python program, assuming
>
> As I was developing the app, I realized that I was writing basically the
> same code over and over and over, just with slight differences, e.g. the
> table name, the criteria, the fields I wanted to return and their display
> order...
> so a couple of dictionaries to define (1) the
Anthony,
uninstalled pydal 17.07, installed 16.11 instead (seemed the most likely
candidate for being the right version) -
things now work normally!
Thanks for the pointer to the problem
On Monday, August 7, 2017 at 4:29:30 PM UTC-7, jim kaubisch wrote:
>
> Hi,
>
> The following failure
Thanks, Anthony!!
That's good news. Please, what IS the right version number and where do I
get it it? GitHub I would guess. Haven't had a chance to investigate yet
As for the eval choice, firstly I realize it may not be truly the best
solution and I realize there are risks involved (eval),
Yes, going back to the correct version of pydal should fix this issue.
Why are you eval'ing DAL code rather than building the query using DAL
objects?
On Monday, August 7, 2017 at 9:01:31 PM UTC-4, jim kaubisch wrote:
>
> Hi Anthony,
>
> Yes, indeed :(
> In connection with my other post, I
Hi Anthony,
Yes, indeed :(
In connection with my other post, I updated pydal in case my problem there
could be fixed by updating pydal to the latest version. Didn't realize :(
I'm at a critical stage of my project so don't really want to upgrade to
the new web2py version right now.
I assume
Did you somehow update pydal without updating web2py? The version of pydal
you are running is not the one associated with web2py 2.14.6 (you have a
more recent version of pydal).
Anthony
On Monday, August 7, 2017 at 7:29:30 PM UTC-4, jim kaubisch wrote:
>
> Hi,
>
> The following failure
13 matches
Mail list logo
