On Mar 14, 2011, at 1:10 PM, Gene Chow wrote:
>
> I'm using the basic router from router.example.py. I also use
> subversion to track changes and I have a .svn directory in
> applications directory. The load function in gluon/rewrite.py tries to
> read controllers in the .svn directory and throws
I'm using the basic router from router.example.py. I also use
subversion to track changes and I have a .svn directory in
applications directory. The load function in gluon/rewrite.py tries to
read controllers in the .svn directory and throws an exception.
I made a change in rewrite.py which fixes
On Jan 12, 2011, at 4:56 PM, Bruno Rocha wrote:
> I am trying to configure a different way of routing, may be you can help me
> or point some hint about it,
> It is a system where the user will register himself and get instant access to
> an account (just like twitter), and the system will give a
Could it be caught with a 404 and routed somewhere?
As Jonathan mentioned, to do that with old routes you will need to hardcode
a list of your controllers. Then anything what is not a controller is a
username. But this is not the best way to do it. I like better the way the
new router works, that is using predefined defaults.
So what you could d
On Jan 12, 2011, at 4:56 PM, Bruno Rocha wrote:
> I am trying to configure a different way of routing, may be you can help me
> or point some hint about it,
> It is a system where the user will register himself and get instant access to
> an account (just like twitter), and the system will give a
With one more patch pending, the new URL router is looking pretty stable. There
are some features pending, but they'll have to wait.
I thought I'd describe some of the possibilities with a few use cases.
Suppose you've written an app, named it 'myapp', and want to make it the
default, with its
7 matches
Mail list logo
