Hi Cliff,

Not a real breakage, rather an issue with eval() itself.

I hacked a quick and dirty prototype based on Buffet-0.4 and TurboStan-0.7.

eval() was crying on the CRs in the template file but:

- The exact same template data coming from heredoc string rather than
read() from file() works fine

- The exact same line of code works when used in a class (like TurboStan
code or my simple cherrypy example)

(See attachement are the 3 modified files.)

Due to more urgent issues I lacked time to dig further...

And today I saw new versions of TurboStan incoming... Then the
ueber-cool announcement of the collaborative attitude between
TurboGears+TurboStan  and CherryPy+Buffet :-)


Olivier.


Cliff Wells wrote:
>
> Olivier Favre-Simon wrote:
>> I somehow hacked a bit on extending Buffet with Stan but it choked on a
>> eval() call (seems eval() doesn't work the same inside a simple def
>> method as inside a class method...)
>>   
> Olivier,
>
> Was this breakage in TurboStan or Buffet?  TurboStan uses eval() but
> it should be self-contained (it's only used to evaluate the Stan
> expression, and then within its own namespace).
>
> If you do use TurboStan with Buffet/CP, I'd like to hear about your
> experiences and any issues you may run into.  I'd also be interested
> in feedback and suggestions/criticisms from people actually using Stan
> to help steer development on it.  Some of the things I'm going to be
> considering next are caching of compiled templates, using widgets from
> Stan, and maybe even implementing a widget or two in Stan, just as a
> proof-of-concept if nothing else.
>
> Cliff
>
>
>

Attachment: Buffet-0.4-Stan-tmp.tar.bz2
Description: application/bzip

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to