I cannot find a complete example of updating a record with factory
can someone please write it out?
record =
db(db.auth_group.id==request.get_vars.specificRoleID).select().first()
form = SQLFORM.factory('record',default = record)
if form.process().accepted:
record.update_reco
I recommend you the debugger pudb:
https://pypi.python.org/pypi/pudb
Just write:
from pudb import set_trace; set_trace()
*anywhere* in your code, and you can print whatever you want, move back and
forth, and run code just at the precise spot that you want to understand
better. I think it's ea
Hello everybody. I am testing my products on web2py v2.11.2 base and have
error. I want to ask is it new feature that virtual fields no more exist in
Row after select? It means if I have Field.Virtual('x', ...) in my model,
after doing db(db.tablename).select() I had this 'x' in results (with
w
in windiws
print s
rise error
127.0.0.1.2015-06-06.15-31-01.ad5a7b20-4ee7-4c91-a9df-8e015fd609e0
'charmap' codec can't encode
characters in position 0-4: character maps to Версияweb2py™Version
2.9.12-stable+timestamp.2015.01.17.06.11.03PythonPython 2.7.6:
C:\Python27\python.exe (prefix: C:\Py
Wing IDE myfriend. Can't go wrong with it: -)
On Saturday, June 6, 2015 at 5:15:44 AM UTC-4, Niphlod wrote:
>
> I'd go with "print vars" simply. You'0ll be able to see in the console
> where web2py was started. in production however the safest thing to do for
> those kind of things is to use the
I consider myself newbie too. I been on it for few months. I am okay with
it, but still learning...
On Saturday, June 6, 2015 at 5:53:19 AM UTC-4, Ivica Kralj wrote:
>
> At the moment users can mark examples as depreciated since which web2py
> version. I will just need to enable tested_on field
I figured out what you did with the layout. You basically copied the
{{block right_sidebar}} content few times in index.html and on the top
before the {{ entend layout.html}} you defined them for example:
{{left_sidebar_enabled=False,right_sidebar_enabled=False,middle_sidebar_enable=False,('mess
That is fine Niphlod. I created this project, primary for personal reason
to have quick resource to examples when I 'm working on my small projects,.
I think people, specially newbies, might find it useful. Comparing myself
to allot of members here, I do consider myself a newbie, although I have
At the moment users can mark examples as depreciated since which web2py
version. I will just need to enable tested_on field. This will all be shown
on example page.
On Friday, 5 June 2015 22:17:36 UTC+2, Rufus wrote:
>
> On Friday, June 5, 2015 at 3:35:08 PM UTC-4, Niphlod wrote:
>
>> BTW: unt
Ok, I will create this example in the next few days...read Monday :)
On Friday, 5 June 2015 19:30:04 UTC+2, Ron Chatterjee wrote:
>
> Can you post the example of div element about recent examples, top rated
> examples...etc and show how you create the box element? I believe that's
> what you me
Ha ha, goodone! Thanks for that.
When you look at something for too long, your learn how to ignore it :)
I have removed 2nd carousel, as it was not needed. Problem was 2nd image's
height. Image was bigger than 1st image.
On Friday, 5 June 2015 17:45:47 UTC+2, Derek wrote:
>
> The slider thing
Thanks Villas.
I have read somewhere, even with user-agent set to disallow, search
crawlers will still crawl your site. Considering site is live now, I rather
just avoid future headache.
On Friday, 5 June 2015 17:39:49 UTC+2, villas wrote:
>
> Really good +1 !
>
> If you are planing to test the
Ah OK. That would be nice design feature to have. I didn't go this far with
design considerations, as I was just eager to release it. There is always
something we can add or improve existing features and functionalities.
Right? :)
On Friday, 5 June 2015 16:10:03 UTC+2, Ron Chatterjee wrote:
>
>
I'd go with "print vars" simply. You'0ll be able to see in the console
where web2py was started. in production however the safest thing to do for
those kind of things is to use the logging module... but that's another
story: to quickly develop I find myself quite pleased with the console
opened
different controllers aren't really meant to share. if you want something
available to both controllers, put the code in models and be happy.
Or you can go the "pythonic way" and put under modules (helpers.py), and
then at the top of file_whatever.py you can use
from helpers import whatever
On
Hi, Dmitry
You've got a unicode string. So you need to convert it to a str type
with utf-8 sequence in it. Use encode() method of unicode type:
>>> s = u'\u041f\u0435\u0440\u0435\u043d\u043e\u0441 \u0441\u0440\u0435
\u0434\u0441\u0442\u0432 \u0441\u043e \u0441\u0447\u0435\u0442\u0430
\u0432 \u043
I recive answer from some site in utf8 and when I store it in db I see:
u'\u041f\u0435\u0440\u0435\u043d\u043e\u0441
\u0441\u0440\u0435\u0434\u0441\u0442\u0432 \u0441\u043e
\u0441\u0447\u0435\u0442\u0430 \u0432
\u043e\u0447\u0435\u0440\u0435\u0434\u044c'
if print it to html:in controller (by re
actually, it never did, but is easy to fix.
On Saturday, June 6, 2015 at 5:26:39 AM UTC+2, Mat Miles wrote:
>
> That seems to have fixed the date issue but I have another field that it
> did not fix. This field is populate not from a database but from a SET.
> When you try to filter on the value
18 matches
Mail list logo
