Re: using Pudge
On Sep 2, 4:47 am, Qiangning Hong [EMAIL PROTECTED] wrote: I met this too and find out that it is because of buildutils-1.2 (the official release) doesn't support highlighter option for pudge command. Upgrading buildutils to svn trunk version works. That's good news! I updated buildutils, but now python setup.py pudge gives me the following error: ... kid.template_util.TemplateExtendsError: Could not open '/usr/lib/ python2.5/site-packages/pudge-0.1.3-py2.5.egg/pudge/template/base/ common.html' Template file 'common.html' not found while processing extends='layout.html', 'common.html' But this file exists on my system, so I don't really unterstand where the error comes from. Any ideas? I'd love to find a way to use it with pylons. Frederik --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: What is the best way to write a service object with Pylons
On 9/1/07, mickolka [EMAIL PROTECTED] wrote: Hi all I want to write a FileStorage service object with following features - should be configured on the start of the application - should be accessible from the any controller - have only one instance Pylons provide a `g` namespace for your application globals: class Globals(object): def __init__(self): self.fs = MySuperService() ... controller.html: % g.fs.supermethod() % Check the docs or search through Pylons cookbook, there is probably a recipe for this. Max. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
trailing slash redirection (routes)
Hello, Anyone does a redirection to make all urls have a trailing slash? What's the simplest way to accomplish this? Max. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: EOFError in production
On Sep 2, 2007, at 5:59 AM, Max Ischenko wrote: On 8/23/07, Philip Jenvey [EMAIL PROTECTED] wrote: I assume it's a concurrency issue, but I don't see why this part of the site would have greater concurrency than elsewhere. This issue was reported recently, and Ben committed a fix for it that's included in Beaker 0.7.5. Now any potential exceptions raised by cPickle.load are caught and Beaker continues on assuming there was no data loaded. Look forward to getting this new release; today I got more than a hundred of those errors on a single page (a crawler?) Ben released 0.7.5 a couple weeks ago with the aforementioned fixes, no need to wait for Pylons 0.9.6: easy_install -U Beaker==0.7.5 -- Philip Jenvey --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: why does pylons depends on nose=0.9.9
On Sep 1, 2007, at 8:47 PM, Qiangning Hong wrote: nose-0.10.0b1 is out for dozens of days. Should pylons be adapted to compatible with it? Have you tried b1 with Pylons? Does it work well? The first alpha release was pretty buggy, and wasn't working with a fairly basic Pylons project nor the actual Pylons tests, that's why we restricted the versions to 0.10. -- Philip Jenvey --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: pyorbited tutorial error
On Aug 31, 2007, at 10:24 PM, Jose Galvez wrote: First I'll apologize for cross posting but I'm not sure if this is an orbited, pylons or paste issue so this is being put on all three lists. Ok so I was going over the orbited pylons chat tutorial and I found an interesting error. I set up my pylons app to be served with cherrypy rather then Paste#http (use = egg:PasteScript#cherrypy in the server section ). Now if I try to use the orbited proxy to serve my pylons app I get the following error when I try to serve a non-static page: 2007-08-31 22:20:02.609 ERROR type 'exceptions.AttributeError':'ProxyBuffer' object has no attribute 'chunked_body' File build\bdist.win32\egg\orbited\proxy2.py, line 213, in state_pre_body If I change my pylons serve from cherrypy to paste#http the error goes away. I've been using cherrypy because I ad read somewhere that it gave better performance compared to past#http (that may no longer be true, I've not done the benchmarks) Any thoughts? There's a bug in the pyorbited code. It should be calling self.state_chunked_body instead of self.chunked_body in that line of code. This doesn't happen on Paste httpserver because it doesn't doesn't support the chunked transfer-coding (that's why it's still HTTP 1.0). Cherrypy server is HTTP 1.1 out of the box, and does chunking. -- Philip Jenvey --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
underscores in code chunks in wiki
hi there, in the firefox browser the fonts on both windows and mac make it so that underscores in the last line of a code chunk in the wiki are obscured. could the css be changed to avoid this? i nearly typed from sqlalchemy import engine from config rather than from sqlalchemy import engine_from_config from the sqlalchemy tutorial thinking it was a funky way of importing from a submodule regards, brendan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: using Pudge
On 9/1/07, Qiangning Hong [EMAIL PROTECTED] wrote: On 7/16/07, Max Ischenko [EMAIL PROTECTED] wrote: python setup.py pudge running pudge error: error in setup.cfg: command 'pudge' has no such option 'highlighter' I met this too and find out that it is because of buildutils-1.2 (the official release) doesn't support highlighter option for pudge command. 'highlighter' was the problem I had. Regarding an alternative to Pudge, James wrote me this in August: James Gardener wrote: Mike Orr wrote: I've just been really turned off by Pudge not working. Yeah me too, I'm working on an alternative based on PyDoctor, that's much nicer. That's all I know about it. -- Mike Orr [EMAIL PROTECTED] --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
url_for() and wildcards
Hi there, I have a route that looks like this:
map.connect('/wiki/*slug',
controller=wiki,
action=view)
Later on I try to expand my wiki links with
url = h.url_for(controller=/wiki,
action=view,
slug=normalize_page(page))
return 'a href=%s%s/a' % (url, label or page)
What I get is something like:
a href=/wiki/foo/a
The problem here is that the slug is not expanded in the generated
URL; I'd like something like
a href=/wiki/Foofoo/a
I didn't find a mention in a Routes manual that wild url parts
could not be expanded by url_for() but it could be an undocumented
feature. Should I be able to expand the URLs the way I do?
Before you point out that I don't need a wild URL part, I'd like to
mention that I want various levels of namespaces and clean action
URLs:
/wiki/Cars/Sport/Mustang/edit
/wiki/Tomato
/wiki/Tomato/recent_changes
/wiki/Programming/Languages/Functional/Standardized/Common%20Lisp
and so on. It seems to me that wild URL part is the way to go but I'm
open to other suggestions.
Best regards,
--
Yannick Gingras
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this group, send email to pylons-discuss@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~--~~~~--~~--~--~---
Re: why does pylons depends on nose=0.9.9
On 9/3/07, Philip Jenvey [EMAIL PROTECTED] wrote: On Sep 1, 2007, at 8:47 PM, Qiangning Hong wrote: nose-0.10.0b1 is out for dozens of days. Should pylons be adapted to compatible with it? Have you tried b1 with Pylons? Does it work well? After removing =nose-0.9.9 from /usr/lib/python2.5/site-packages/Pylons-0.9.6rc3-py2.5.egg-info/requires.txt, nose-0.10.0b1works fine in my machine: ~/tmp/Pylons-0.9.6rc3/tests $ nosetests --version nosetests version 0.10.0b1 ~/tmp/Pylons-0.9.6rc3/tests $ nosetests -- Ran 60 tests in 23.181s OK The first alpha release was pretty buggy, and wasn't working with a fairly basic Pylons project nor the actual Pylons tests, that's why we restricted the versions to 0.10. It seems the b1 version got a big improvement then :) -- Qiangning Hong http://www.douban.com/people/hongqn/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: What is the best way to write a service object with Pylons
Thanks Max, seems like it makes sense to put it to global scope this way and configure programmaticaly. Just used to configure everything with XML, but programmatic object configuration with python seems to be less verbose than with Java. m On Sep 2, 4:01 pm, Max Ischenko [EMAIL PROTECTED] wrote: On 9/1/07, mickolka [EMAIL PROTECTED] wrote: Hi all I want to write a FileStorage service object with following features - should be configured on the start of the application - should be accessible from the any controller - have only one instance Pylons provide a `g` namespace for your application globals: class Globals(object): def __init__(self): self.fs = MySuperService() ... controller.html: % g.fs.supermethod() % Check the docs or search through Pylons cookbook, there is probably a recipe for this. Max. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
