Re: GAE select all does not iterate

I am not sure where you are printing to (console, logs, html page) but
one problem may be that if you view the output into an HTML document
rows are displayed as <Row {...}> and your browser thinks this is a
tag, does not understand it and makes it invisible.

On Aug 31, 11:19 am, Arbie Samong <phek...@...> wrote:
> Update: Following christian's example, it seems that looping over the
> Rows object in controller does nothing, but looping over it on the
> view is working.
>
> My controllers and models are almost exactly the same, at least the
> fields that are affected. I am testing on localhost:8080 first,
> although same results in GAE production. I print out stuff on
> localhost:8080, it works although it breaks the page and displays
> withing <pre> tags (ala php die ;-P), so I can see variables. I can
> see the Rows object and the fetched records, but when I iterate over
> them nothing happens.
>
> # controller
> profiles =
> db(db.userprofile.created).select(orderby=~db.userprofile.created,
> limitby=(0,20))
> print profiles # no problem, I see the profiles object
> print len(profiles) # still OK
>
> for profile in profiles:
>   print profile # here nothing happens
>
> # view
> <h1>profiles</h1>

Re: How can i create my own CAS provider?

def user(): return dict(form=auth())

exposes the CAS provider. There is nothing special to do as long as
the consumer run on the same domain.

On Aug 31, 1:38 pm, nekrox <nek...@...> wrote:
> I have some apps and use the same database for share a auth system. I
> prefer to use CAS and have my own provider for my apps, but do not
> quite understand how to do as the documentation says, someone will
> have an example?
>
> Regards

Re: testing scheduler in windows

Trying to isolate the problem... can any windows user run the
following test for me?

get trunk
cd web2py/gluon
python2.6 meta_scheduler.py

(python 2.7 should be ok too)
you should get the following text repeated ...
--- begin ----
starting task
task started
thum
thum
thum
thum
thum
reporting task
--- end ---
after a few cycles press [ctrl+c]. Do you get a traceback? Do all new
task - reporting task pair up in the output?

Massimo

On Aug 31, 8:45 am, António Ramos <ramstei...@...> wrote:
> the -K option is only for 2.6 but with python  2.6 i have that screenshot
> with error until i break it with ctrl c
> after that the task runs only the first time and not the other 2 as your
> demo on Vimeo
>

Bug in TR when rendering an array

To reproduce, create a view with the ff contents:

<style type="text/css">
td {
border-width: 5px;
border-color: #000080;
border-style: solid;
}
</style>

{{arr=['second','third']}}
{{=TABLE(TR(TD('first'),[TD(x) for x in arr]))}}

HTML result:

<table>
<tbody>
<tr>
<td>first</td>
<td></td>       <-- This extra td should not be here
<td>second</td>
<td>third</td>
</tr>
</tbody>
</table>

Remarks:

The bug does not show if there is no TD before the TD array. Thus, the
following is OK.

Re: testing scheduler in windows

Re: Bug in TR when rendering an array

Re: Bug in TR when rendering an array

Just when I thought I have helped find a bug, I am faced with the
revelation that I need to hone my python some more. He he he.

Thanks Anthony.

On Sep 1, 12:18 pm, Anthony <abasta...@...> wrote:
> The problem is you are passing a list of TD's to TR instead of individual
> TD's. Instead, try this:
>
> {{=TABLE(TR(TD('first'),*[TD(x) for x in arr]))}}
>
> Notice the "*" before the list comprehension -- that converts the list to a
> set of positional arguments.
>
> Anthony
>
>
>
>
>
>
>
> On Wednesday, August 31, 2011 8:03:48 PM UTC-4, Noel Villamor wrote:
>
> > To reproduce, create a view with the ff contents:
>
> > <style type="text/css">
> > td {
> > border-width: 5px;
> > border-color: #000080;
> > border-style: solid;
> > }
> > </style>
>
> > {{arr=['second','third']}}
> > {{=TABLE(TR(TD('first'),[TD(x) for x in arr]))}}
>
> > HTML result:
>
> > <table>
> > <tbody>
> > <tr>
> > <td>first</td>
> > <td></td>       <-- This extra td should not be here
> > <td>second</td>
> > <td>third</td>
> > </tr>
> > </tbody>
> > </table>
>
> > Remarks:
>
> > The bug does not show if there is no TD before the TD array. Thus, the
> > following is OK.
> > {{=TABLE(TR([TD(x) for x in arr]))}}

Re: Bug in TR when rendering an array

By the way, the reason why I stumbled on this is because I wanted to
add a fourth TD to my test case.

{{=TABLE(TR(TD('first'),*[TD(x) for x in arr],TD('fourth')))}}
or more simply
{{=TABLE(TR(TD('first'),*arr,TD('fourth')))}}

But, this results to
SyntaxError: only named arguments may follow *expression

The syntax appears reasonable to me. Perhaps in the future, developers
would consider allowing this.

On Sep 1, 12:31 pm, Noel Villamor <noe...@...> wrote:
> Just when I thought I have helped find a bug, I am faced with the
> revelation that I need to hone my python some more. He he he.
>
> Thanks Anthony.
>
> On Sep 1, 12:18 pm, Anthony <abasta...@...> wrote:
>
>
>
>
>
>
>
> > The problem is you are passing a list of TD's to TR instead of individual
> > TD's. Instead, try this:
>
> > {{=TABLE(TR(TD('first'),*[TD(x) for x in arr]))}}
>
> > Notice the "*" before the list comprehension -- that converts the list to a
> > set of positional arguments.
>
> > Anthony
>
> > On Wednesday, August 31, 2011 8:03:48 PM UTC-4, Noel Villamor wrote:
>
> > > To reproduce, create a view with the ff contents:
>
> > > <style type="text/css">
> > > td {
> > > border-width: 5px;
> > > border-color: #000080;
> > > border-style: solid;
> > > }
> > > </style>
>
> > > {{arr=['second','third']}}
> > > {{=TABLE(TR(TD('first'),[TD(x) for x in arr]))}}
>
> > > HTML result:
>
> > > <table>
> > > <tbody>
> > > <tr>
> > > <td>first</td>
> > > <td></td>       <-- This extra td should not be here
> > > <td>second</td>
> > > <td>third</td>
> > > </tr>
> > > </tbody>
> > > </table>
>
> > > Remarks:
>
> > > The bug does not show if there is no TD before the TD array. Thus, the
> > > following is OK.
> > > {{=TABLE(TR([TD(x) for x in arr]))}}

Re: Bug in TR when rendering an array

Re: Re: Bug in TR when rendering an array

On Aug 31, 2011, at 5:50 PM, Noel Villamor wrote:

> 
> By the way, the reason why I stumbled on this is because I wanted to
> add a fourth TD to my test case.
> 
> {{=TABLE(TR(TD('first'),*[TD(x) for x in arr],TD('fourth')))}}
> or more simply
> {{=TABLE(TR(TD('first'),*arr,TD('fourth')))}}
> 
> But, this results to
> SyntaxError: only named arguments may follow *expression
> 
> The syntax appears reasonable to me. Perhaps in the future, developers
> would consider allowing this.

You can, I think, supply a list of TDs to TR. The problem in your example is that you had a bare TD followed by a
list of TDs.

Instead of 

{{=TABLE(TR(TD('first'),[TD(x) for x in arr]))}}

you could probably have said this:

{{=TABLE(TR([TD('first')] + [TD(x) for x in arr]))}}

> 
> On Sep 1, 12:31 pm, Noel Villamor <noe...@...> wrote:
>> Just when I thought I have helped find a bug, I am faced with the
>> revelation that I need to hone my python some more. He he he.
>> 
>> Thanks Anthony.
>> 
>> On Sep 1, 12:18 pm, Anthony <abasta...@...> wrote:
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> The problem is you are passing a list of TD's to TR instead of individual
>>> TD's. Instead, try this:
>> 
>>> {{=TABLE(TR(TD('first'),*[TD(x) for x in arr]))}}
>> 
>>> Notice the "*" before the list comprehension -- that converts the list to a
>>> set of positional arguments.
>> 
>>> Anthony
>> 
>>> On Wednesday, August 31, 2011 8:03:48 PM UTC-4, Noel Villamor wrote:
>> 
>>>> To reproduce, create a view with the ff contents:
>> 
>>>> <style type="text/css">
>>>> td {
>>>> border-width: 5px;
>>>> border-color: #000080;
>>>> border-style: solid;
>>>> }
>>>> </style>
>> 
>>>> {{arr=['second','third']}}
>>>> {{=TABLE(TR(TD('first'),[TD(x) for x in arr]))}}
>> 
>>>> HTML result:
>> 
>>>> <table>
>>>> <tbody>
>>>> <tr>
>>>> <td>first</td>
>>>> <td></td>       <-- This extra td should not be here
>>>> <td>second</td>
>>>> <td>third</td>
>>>> </tr>
>>>> </tbody>
>>>> </table>
>> 
>>>> Remarks:
>> 
>>>> The bug does not show if there is no TD before the TD array. Thus, the
>>>> following is OK.
>>>> {{=TABLE(TR([TD(x) for x in arr]))}}