I was getting the same thing when I was trying to reference "h.url()" which no
longer exists.
I was getting a non-helpful backtrace like above.
-jack
P.S.: Time to update the docs here as well since h.url() is now incorrect.
On Apr 15, 2010, at 6:07 PM, kazin wrote:
>> Ah, yes, there was a T
On Thu, Apr 15, 2010 at 6:07 PM, kazin wrote:
> This is a new project on 1.0rc1, I have AuthKit in the middleware (and
> am using FormAlchemy).
Could you try commenting out AuthKit and seeing if the error changes?
I doubt it will, but that would rule out AuthKit as a contributor.
--
Mike Orr
> Ah, yes, there was a ToscaWidgets bug which masked the proper error handling.
> I mean in my existing projects I've moved to 1.0rc1, I haven't seen this
> issue. Were you saying that this was happening with a non-toscawidgets
> project using 0.10/1.0?
Yes. Sorry for the imprecision. In 1.0rc
On Apr 15, 7:36 pm, Ben Bangert wrote:
> Ah, yes, there was a ToscaWidgets bug which masked the proper error handling.
> I mean in my existing projects I've moved to 1.0rc1, I haven't seen this
> issue. Were you saying that this was happening with a non-toscawidgets
> project using 0.10/1.0?
I
On Apr 15, 2010, at 3:56 PM, cd34 wrote:
> On Apr 15, 5:02 pm, Ben Bangert wrote:
>> Using a name that's not defined in a Mako template should *always* throw an
>> error. What is happening when you use an undefined variable, and what are
>> you expecting?
>
> 0.9.7 returned a mako template err
On Apr 15, 5:02 pm, Ben Bangert wrote:
> Using a name that's not defined in a Mako template should *always* throw an
> error. What is happening when you use an undefined variable, and what are you
> expecting?
0.9.7 returned a mako template error in the browser which allowed you
to see the cont
On Apr 15, 2010, at 1:58 PM, kazin wrote:
> Just chiming in, I too have the same issue with ${asdf} giving me an
> internal server error, even after removing ToscaWidgets (and
> AuthKit). I backed out most of the changes I have made from my fresh
> install of 1.0rc1 but still cant find the culpri
Just chiming in, I too have the same issue with ${asdf} giving me an
internal server error, even after removing ToscaWidgets (and
AuthKit). I backed out most of the changes I have made from my fresh
install of 1.0rc1 but still cant find the culprit that introduced this
issue
--
You received this
On Thursday 15 April 2010 09:13 PM, eneely wrote:
I do something similar with engineering data where I separate the data
into tabs for different temperatures and data types and send the
spreadsheets back to the client. I use a module called xlwt to do all
of the spreadsheet formatting in Pylons
I do something similar with engineering data where I separate the data
into tabs for different temperatures and data types and send the
spreadsheets back to the client. I use a module called xlwt to do all
of the spreadsheet formatting in Pylons before I send the data back
using a CStringIO output
Am 15.04.2010 um 11:18 schrieb Krishnakant Mane:
> Good, so now I am left to just hack out the ods related problem.
> It will be great if I can send the spreadsheet across to browser. The
> browser may inturn open calc and display the spreadsheet.
For spreadsheets the python standard library i
Good, so now I am left to just hack out the ods related problem.
It will be great if I can send the spreadsheet across to browser. The
browser may inturn open calc and display the spreadsheet.
Happy hacking.
Krishnakant.
On Thursday 15 April 2010 02:14 PM, Michael Brickenstein wrote:
We als
We also use reportlab in RUM to generate pdf's
with landscape tables of data.
No complaints.
It is a general pdf framework, so not always "supereasy" (was a little
bit difficult to
find out, how to register a specific font for bold text), but it also
seems quite mature.
Cheers,
Michael
On 15 Apr.,
13 matches
Mail list logo
