[web2py] Re: web2py 2.15.1 is OUT

Alex please create an issue in github, that's a genuine python 3 bug, exactly the kind we want to find during this experimental python 3 support phase. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.googl

Re: [web2py] Re: web2py 2.15.1 is OUT

I tested the latest version 2.15.2 and I've got a problem when accessing ajax post parameters with web2py under Python 3. The client sends a PUT request using jquery like this: $.ajax('', { data: JSON.stringify({ report: report outputFormat: 'pdf' }), type: "PUT", cont

Re: [web2py] Re: web2py 2.15.1 is OUT

On Wednesday, August 2, 2017 at 11:26:31 PM UTC-4, Richard wrote: > > I recall having conversation about that, I am not sure, I think it > language file or pickle objects that get modify in a no way back manner... > I think only the sessions and error tickets should be affected, as they are pick

Re: [web2py] Re: web2py 2.15.1 is OUT

I recall having conversation about that, I am not sure, I think it language file or pickle objects that get modify in a no way back manner... But, sure the app code it not affected... I should retrieve this exchange... will try tomorrow. Richard On Wed, Aug 2, 2017 at 9:53 PM, Anthony wrote: >

Re: [web2py] Re: web2py 2.15.1 is OUT

On Wednesday, August 2, 2017 at 12:26:45 PM UTC-4, Richard wrote: > > Don't forget to copy/paste (backup) you app before you try Python 3, > because there is no way back with the app once you use it under python 3 as > certain stuff are modify by python 3 that let your app unusable with python >

Re: [web2py] Re: web2py 2.15.1 is OUT

Don't forget to copy/paste (backup) you app before you try Python 3, because there is no way back with the app once you use it under python 3 as certain stuff are modify by python 3 that let your app unusable with python 2 after. Richard On Wed, Aug 2, 2017 at 9:24 AM, Anthony wrote: > On Wedne

[web2py] Re: web2py 2.15.1 is OUT

On Wednesday, August 2, 2017 at 9:13:31 AM UTC-4, bonbe wrote: > > The same thing happened to me. > > Are you saying that has happened with the latest release (2.15.2), or only with 2.15.0b1? Please use Python3. > > web2py should continue to work with Python 2, so there is no need to move to Pyt

[web2py] Re: web2py 2.15.1 is OUT

The same thing happened to me. Please use Python3. 2017年7月17日月曜日 21時11分58秒 UTC+9 vince: > > i download from > https://mdipierro.pythonanywhere.com/examples/static/web2py_src.zip > > on first line of changelog it's 2.15.0b1 > > and when i run web2py.py error as below > > Traceback (most recent

[web2py] Re: web2py 2.15.1 is OUT

Carlos your problem was already reported: https://github.com/web2py/web2py/issues/1672 Before the next release which will have the fix the workaround is: form = SQLFORM.factory(db.tabela.campo.clone()) -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.c

[web2py] Re: web2py 2.15.1 is OUT

I have a problem with this version. This does not work anymore: db.define_table('tabela', Field('campo')) form = SQLFORM.factory(db.tabela.campo) I throws this: Traceback (most recent call last): File "C:\Users\carlos.costa\Downloads\web2py\gluon\restricted.py", line 219, in restrict

[web2py] Re: web2py 2.15.1 is OUT

Vince that seems like a bug in the way you updated web2py you seem to be using the old DAL. -- 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

[web2py] Re: web2py 2.15.1 is OUT

i download from https://mdipierro.pythonanywhere.com/examples/static/web2py_src.zip on first line of changelog it's 2.15.0b1 and when i run web2py.py error as below Traceback (most recent call last): File "./web2py.py", line 21, in import gluon.widget File "/home/web2py/gluon/__init__.

[web2py] Re: web2py 2.15.1 is OUT

On Friday, July 14, 2017 at 1:12:39 AM UTC-7, Dave S wrote: > > > > On Thursday, July 13, 2017 at 6:20:21 PM UTC-7, Dave S wrote: >> >> >> >> On Thursday, July 13, 2017 at 2:43:57 PM UTC-7, Anthony wrote: >>> >>> Are you saying that used to work but doesn't any longer? >>> >>> >> There are 3 exam

[web2py] Re: web2py 2.15.1 is OUT

On Thursday, July 13, 2017 at 5:17:11 PM UTC-7, Leonel Câmara wrote: > > Note this is deprecated: > > row = db().select(max) > > Calling db() like that without a query will break common filters for > instance. > Do we need another pull request on the book, since the examples are there? (They

[web2py] Re: web2py 2.15.1 is OUT

On Thursday, July 13, 2017 at 6:20:21 PM UTC-7, Dave S wrote: > > > > On Thursday, July 13, 2017 at 2:43:57 PM UTC-7, Anthony wrote: >> >> Are you saying that used to work but doesn't any longer? >> >> > There are 3 examples in the book at the link. They work in 2.14.6 using > -S (and I did cut

[web2py] Re: web2py 2.15.1 is OUT

Anthony, pls see https://groups.google.com/d/msg/web2py/h4b4xz2NzNM/QHSoRfrcCAAJ If we put double quotes on the table name, which happens to not be there for *aggregates* and *distinct* then the sql query will work. On Friday, July 14, 2017 at 5:43:57 AM UTC+8, Anthony wrote: > > Are you saying

[web2py] Re: web2py 2.15.1 is OUT

Thank you Anthony. I always appreciate your input. I recall using the aggregates max() and count() before and they worked fine following the book. That was quite long ago. However, this time, I did not try on the "old" web2py version. I upgraded to 2.15.1 and continued to code in it. Using db(

[web2py] Re: web2py 2.15.1 is OUT

On Thursday, July 13, 2017 at 2:43:57 PM UTC-7, Anthony wrote: > > Are you saying that used to work but doesn't any longer? > > There are 3 examples in the book at the link. They work in 2.14.6 using -S (and I did cut-n-paste to check). > How about db(db.table).select(max)? > > Anthony >

[web2py] Re: web2py 2.15.1 is OUT

Thank you Leonel, I actually have a very complex query, and it ran into the error I mentioned. In my query I have: db(query).select(other_fields, aggregate, groupby=...etc..., orderby=...etc ...) and I ran into the error. So I tried to identify if it was my complex query throwing the error, my

Re: [web2py] Re: web2py 2.15.1 is OUT

No I am not using the rname feature On Friday, July 14, 2017 at 2:26:57 AM UTC+8, Richard wrote: > > Are you using rname feature? > > If so, the issue may need to be further investigate as why SELECT DISTINCT > ON (TABLE_of_sites.title) is not double quoted and all the other table_name > and fie

[web2py] Re: web2py 2.15.1 is OUT

Note this is deprecated: row = db().select(max) Calling db() like that without a query will break common filters for instance. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/li

[web2py] Re: web2py 2.15.1 is OUT

Are you saying that used to work but doesn't any longer? How about db(db.table).select(max)? Anthony On Thursday, July 13, 2017 at 1:16:31 PM UTC-4, lyn2py wrote: > > I'm using a simple query to get aggregate: > > max = db.table.date.max() > row = db().select(max) > > Just following the example

Re: [web2py] Re: web2py 2.15.1 is OUT

Are you using rname feature? If so, the issue may need to be further investigate as why SELECT DISTINCT ON (TABLE_of_sites.title) is not double quoted and all the other table_name and field instance are... So maybe the flaw is somewhere in the escaping related to rname feature... Richard On Thu

[web2py] Re: web2py 2.15.1 is OUT

Following this lead https://stackoverflow.com/questions/34708963/error-missing-from-clause-entry-for-table I discovered that if we add double quotes to the tablename, for all instances of the tablename, like this: "TABLE_of_sites" Then the query will work. On Friday, July 14, 2017 at 1:48:10

[web2py] Re: web2py 2.15.1 is OUT

Table code: db.define_table('TABLE_of_sites', Field('site_id', 'reference sites'), Field('title', 'string'), Field('date','datetime'), ... Field('updated','datetime', update=request.now, writable=False), format='%(site_id)s' ) In controller: table = db['TABLE_of_sites'] rows = db(table).select(

Re: [web2py] Re: web2py 2.15.1 is OUT

Here it is... db.define_table('TABLE_of_sites', Field('site_id', 'reference sites'), Field('title', 'string'), Field('date','datetime'), ... Field('updated','datetime', update=request.now, writable=False), format='%(site_id)s' ) There are multiple entries for a particular title, so I want to ge

Re: [web2py] Re: web2py 2.15.1 is OUT

@lyn2py, seems more a issue with naming in your model than anything else... Can you show us your model? On Thu, Jul 13, 2017 at 1:16 PM, lyn2py wrote: > I'm using a simple query to get aggregate: > > max = db.table.date.max() > row = db().select(max) > > Just following the example here http://ww

[web2py] Re: web2py 2.15.1 is OUT

I'm using a simple query to get aggregate: max = db.table.date.max() row = db().select(max) Just following the example here http://www.web2py.com/books/default/chapter/29/06/the-database-abstraction-layer#sum-avg-min-max-and-len But I ran into this error: Traceback (most recent call last):

[web2py] Re: web2py 2.15.1 is OUT

On Thursday, July 13, 2017 at 1:03:31 PM UTC-4, Massimo Di Pierro wrote: > > @Anthony, > > could you provide a simple example? > model: db.define_table('mytable', Field('name'), Field('photo', 'upload')) controller: def main_page(): return dict() def form_component(): return di

[web2py] Re: web2py 2.15.1 is OUT

@Anthony, could you provide a simple example? Massimo On Tuesday, 11 July 2017 15:19:58 UTC-5, Anthony wrote: > > One new feature is that in modern browsers (that support FormData), web2py > Ajax components now support file uploads out of the box (no need for > third-party plugins). > > Anthon

[web2py] Re: web2py 2.15.1 is OUT

One new feature is that in modern browsers (that support FormData), web2py Ajax components now support file uploads out of the box (no need for third-party plugins). Anthony On Monday, July 10, 2017 at 5:40:08 PM UTC-4, Massimo Di Pierro wrote: > > It took a year. Thanks to everybody who contri

Re: [web2py] Re: web2py 2.15.1

On Monday, June 26, 2017 at 12:04:37 PM UTC-4, Richard wrote: > > http://web2py.com/books/default/chapter/29/07/forms-and-validators#IS_DATE > > I don't know if we enforce that this formatting respect any python > standard... > > I can give a try if we can pass flatpickr parameters without issue..

Re: [web2py] Re: web2py 2.15.1

http://web2py.com/books/default/chapter/29/07/forms-and-validators#IS_DATE I don't know if we enforce that this formatting respect any python standard... I can give a try if we can pass flatpickr parameters without issue... Richard On Mon, Jun 26, 2017 at 11:57 AM, Anthony wrote: > On Monday,

Re: [web2py] Re: web2py 2.15.1

On Monday, June 26, 2017 at 10:42:33 AM UTC-4, Richard wrote: > > We could certainly do that... Things would happen in web2py.js thought, or > we bringing out flatpickr from there... But it wouldn't work properly > passing parameters time/date/datetime from validators IS_TIME(), IS_DATE(), > etc

Re: [web2py] Re: web2py 2.15.1

We could certainly do that... Things would happen in web2py.js thought, or we bringing out flatpickr from there... But it wouldn't work properly passing parameters time/date/datetime from validators IS_TIME(), IS_DATE(), etc. So we will get complaints saying that it doesn't work specifying date for

Re: [web2py] Re: web2py 2.15.1

I'm not sure it would really have to support Python date formatting. Couldn't we just specify the appropriate default formats in web2py_ajax.html and then point use

Re: [web2py] Re: web2py 2.15.1

To integrate flatpickr a flatpickr plugin should be write to support python date time string formating : http://strftime.org/ That what have been suggested by flatpickr devs : https://github.com/chmln/flatpickr/issues/886 I try to integrate flatpickr here and it get muddy along the road as I lear

[web2py] Re: web2py 2.15.1

For what it's worth, I disagree with the last statement completely. I've used other frameworks and feel the documentation for web2py is far superior. Some best practices docs would be nice but that hardly qualifies as poor documentation. -Jim On Friday, June 23, 2017 at 3:04:11 PM UTC-5, Oas

[web2py] Re: web2py 2.15.1

It can be cool to have best practices documentations too; Unit testing(with auth,decorated methods...), Continuous Integration(Either travis-ci or jenkins...), because web2py may have many features but the documentation is still very poor. kr, Oasis On Monday, June 5, 2017 at 10:39:11 AM UTC

[web2py] Re: web2py 2.15.1

i think this guy is working on the flatpickr datepicker but could use some help https://github.com/web2py/web2py/issues/1646 On Monday, June 5, 2017 at 10:39:11 AM UTC+2, Karoly Kantor wrote: > > Dear Massimo, > > I saw your question in the developers group where I cannot post, therefore > i d

[web2py] Re: web2py 2.15.1

Make a PR On Friday, 16 June 2017 10:05:48 UTC-5, Oasis Agano wrote: > > I think that *flatpickr* should be the default datetime picker for the > next Web2py it looks awesome > > On Monday, June 5, 2017 at 10:39:11 AM UTC+2, Karoly Kantor wrote: >> >> Dear Massimo, >> >> I saw your question in th

Re: [web2py] Re: web2py 2.15.1

Go ahead and integrate it... We shouldn't wait for that before launch long awaiting new web2py version to me. Richard On Fri, Jun 16, 2017 at 11:05 AM, Oasis Agano wrote: > I think that *flatpickr* should be the default datetime picker for the > next Web2py it looks awesome > > On Monday, June

[web2py] Re: web2py 2.15.1

I think that *flatpickr* should be the default datetime picker for the next Web2py it looks awesome On Monday, June 5, 2017 at 10:39:11 AM UTC+2, Karoly Kantor wrote: > > Dear Massimo, > > I saw your question in the developers group where I cannot post, therefore > i do it here. > > I am current

Re: [web2py] Re: web2py 2.15.1

On Wed, Jun 14, 2017 at 6:22 PM, Anthony wrote: > On Wednesday, June 14, 2017 at 2:33:58 PM UTC-4, Richard wrote: >> >> Anthony, >> >> What are the issue with Calendar?? I know it outdated, support seems to >> shade away (http://www.dynarch.com/ -> Website down and a link to >> documentation is p

Re: [web2py] Re: web2py 2.15.1

On Wednesday, June 14, 2017 at 2:33:58 PM UTC-4, Richard wrote: > > Anthony, > > What are the issue with Calendar?? I know it outdated, support seems to > shade away (http://www.dynarch.com/ -> Website down and a link to > documentation is provide... > See OP. > I had step back from implement

Re: [web2py] Re: web2py 2.15.1

Anthony, What are the issue with Calendar?? I know it outdated, support seems to shade away (http://www.dynarch.com/ -> Website down and a link to documentation is provide... But it plays so well with python date/datetime formatting string... I had step back from implementing flatpickr, maybe we

Re: [web2py] Re: web2py 2.15.1

Hmm, I had a look at the code of flatpickr for fromatting : https://github.com/chmln/flatpickr/blob/master/src/flatpickr.js#L1461 Would require a major refactor to support python string fromatting datetime parameter '%Y-%m-%d %H:%M:%S' Also it doesn't seems to support timezone... https://chmln.

Re: [web2py] Re: web2py 2.15.1

Here : https://github.com/web2py/web2py/commit/0205594f0853680e7c548dd0c506640958e36f1b Just go to : welcome/default/test_flatpickr, a dummy form with the 3 field types date, datetime, time demo Meaningful changes are mostly at the top and the bottom of diff... Remain to manger i18n and figure o

Re: [web2py] Re: web2py 2.15.1

Ok, I figure this out, I mean it work with only change into web2py.js and web2py_ajax.html with web2py-master (up to date)... I should remove reference to web2py_ajax.js in this comment and replace it with web2py.js I guess?? Have you any input regarding the previous message about flatpickr integ

Re: [web2py] Re: web2py 2.15.1

On Monday, June 12, 2017 at 2:28:21 PM UTC-4, Richard wrote: > > Also, I am not sure what happen with web2py_ajax.*js *I found reference > to it in web2py_ajax*.html* > You must have a very old version -- web2py_ajax.js was changed to web2py.js a long time ago. Anthony -- Resources: - http://

Re: [web2py] Re: web2py 2.15.1

Also, I am not sure what happen with web2py_ajax.*js *I found reference to it in web2py_ajax*.html* quote: // These variables are used by the web2py_ajax_init function in web2py_ajax.js (which is loaded below). But it seems to have been removed?? I try to search the list and github for explanat

Re: [web2py] Re: web2py 2.15.1

I made some progress... It relatively straigh foward to replace Calendar... I am reading IS_TIME() validator which handle time with second or not... I am not sure how I could translate that with time picker from flatpicker which use enableSeconds boolean flag to determine if it requires second or

Re: [web2py] Re: web2py 2.15.1

+1 -- 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 uns

Re: [web2py] Re: web2py 2.15.1

Note, flatpickr supports dates, datetimes, and times, so it can replace both the calendar widget and the timeEntry widget. Anthony On Thursday, June 8, 2017 at 10:28:59 AM UTC-4, Richard wrote: > > Will give a try... Hope it not too difficult to do, I don't have much > time... > > Richard > > O

[web2py] Re: web2py 2.15.1

+1 to change built in date picker , I same already changed it by other in my apps . Em segunda-feira, 5 de junho de 2017 05:39:11 UTC-3, Karoly Kantor escreveu: > > Dear Massimo, > > I saw your question in the developers group where I cannot post, therefore > i do it here. > > I am currently awa

Re: [web2py] Re: web2py 2.15.1

Will give a try... Hope it not too difficult to do, I don't have much time... Richard On Wed, Jun 7, 2017 at 4:46 PM, Carlos Costa wrote: > +1 on date picker. It is totally outdated. > > Em segunda-feira, 5 de junho de 2017 05:39:11 UTC-3, Karoly Kantor > escreveu: >> >> Dear Massimo, >> >> I s

[web2py] Re: web2py 2.15.1

+1 on date picker. It is totally outdated. Em segunda-feira, 5 de junho de 2017 05:39:11 UTC-3, Karoly Kantor escreveu: > > Dear Massimo, > > I saw your question in the developers group where I cannot post, therefore > i do it here. > > I am currently aware of the following issues to be fixed: >

Re: [web2py] Re: web2py 2.15.1

+1 On Wednesday, June 7, 2017 at 2:03:09 PM UTC-5, Richard wrote: > > flatpickr seems really nice... Any reason why we don't replace the actual > "built-in" calendar that we ship web2py with? > > Richard > > On Tue, Jun 6, 2017 at 9:31 AM, Anthony > > wrote: > >> On Tuesday, June 6, 2017 at 5:02

Re: [web2py] Re: web2py 2.15.1

flatpickr seems really nice... Any reason why we don't replace the actual "built-in" calendar that we ship web2py with? Richard On Tue, Jun 6, 2017 at 9:31 AM, Anthony wrote: > On Tuesday, June 6, 2017 at 5:02:10 AM UTC-4, tim.nyb...@conted.ox.ac.uk > wrote: >> >> Re #3: I highly recommend swap

[web2py] Re: web2py 2.15.1

On Tuesday, June 6, 2017 at 5:02:10 AM UTC-4, tim.nyb...@conted.ox.ac.uk wrote: > > Re #3: I highly recommend swapping in Eonasdan's bootstrap-datetimepicker: > https://github.com/Eonasdan/bootstrap-datetimepicker > That's nice but is tied to Bootstrap and has a lot of dependencies. Something m

[web2py] Re: web2py 2.15.1

Re #3: I highly recommend swapping in Eonasdan's bootstrap-datetimepicker: https://github.com/Eonasdan/bootstrap-datetimepicker I just altered my web2py_ajax.html to swap dependencies and initialize datepickers: # response.files.insert(1,'/inc/css/calendar.css') # response.files.insert(2,'/inc/