My apologies to anyone who encountered this problem (reported
anonymously overnight):
AttributeError: 'SubMapper' object has no attribute '__exit__'.
It's fixed now in the asplake/routes repo and will be in due course in
bbangert/routes if I haven't already tested Ben's patience past
So does this mean that Marco is entirely different framework and no
relation with Pylons? I had impression that Pylons 2.0 shall be called
as meta framework.
Do we have any document or discussion to understand where the Pylons
lacks and how Marco solves the problem?
On Dec 30, 10:24 am, Graham
On Dec 30, 1:37 am, Mike Orr sluggos...@gmail.com wrote:
On Tue, Dec 29, 2009 at 11:36 PM, Mike Orr sluggos...@gmail.com wrote:
On Tue, Dec 29, 2009 at 7:17 PM, Chris fractalbynat...@gmail.com wrote:
I put the Routes-exp (formerly Routes 2) code on bitbucket. It may be
easier to follow.
Thanks Mike. More detailed post. I have gone through the Graham's
discussion list and some of the web pages. I stayed away from Zope
Plone stuffs since people scare me on learning curve.
As you mentioned, Pylons 2.0/x.y may hide the implementation details
of marco and yet provide rather more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31 Dec 2009, at 01:04, karikris...@gmail.com wrote:
Does this new architecture support running multiple applications
together to make one website? For example, say we have a blog
application, forum application, poll, feedback and cms
I can't speak for Routes 2 but I'm pleased to report that my changes
will soon make it into dev Routes. Actually delighted would be a
better word - it's my first formal contribution :-)
A nice next step would be to refactor a published example or two. A
squeaky clean tutorial example with a
That's great news!
Quick question, is setting conditions at the collection() level
supported? For example, most of my urls require a subdomain.
map.collection('events', 'event', conditions=dict(sub_domain=True))
File /Routes-1.11dev-py2.6.egg/routes/mapper.py, line 164, in
connect
if
Oops - merge error, fixed. I should add a test for that. You can add
requirements at the collection level too - it adds a tiny inefficiency
I suppose but it looks neat, e.g.:
map.collection('events', 'event', conditions=dict(sub_domain=True),
requirements=dict(id='\d+'))
On Dec 29, 9:32 am,
Sorry to deviate the topic. Do we have Pylon release before/on Jan 1,
2010 possibly? I have to upload my pylons application on Internet on
Jan 15, 2010.
On Dec 29, 2:54 pm, Mike Burrows (asplake) m...@asplake.co.uk
wrote:
Oops - merge error, fixed. I should add a test for that. You can add
On Tue, Dec 29, 2009 at 10:06 AM, karikris...@gmail.com
karikris...@gmail.com wrote:
Sorry to deviate the topic. Do we have Pylon release before/on Jan 1,
2010 possibly? I have to upload my pylons application on Internet on
Jan 15, 2010.
Ben said he's aiming for a release at the end of the
On Tue, Dec 29, 2009 at 12:51 AM, Mike Burrows (asplake)
m...@asplake.co.uk wrote:
I can't speak for Routes 2 but I'm pleased to report that my changes
will soon make it into dev Routes. Actually delighted would be a
better word - it's my first formal contribution :-)
Routes 2 is cancelled.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30 Dec 2009, at 03:17, Chris wrote:
In the Pylons roadmap wiki page, it mentions a mysterious ;) new meta
framework called Marco. Is this hosted anywhere? I'd like to just
poke around and see where it is headed.
It's early days yet but ...
On Tue, Dec 29, 2009 at 7:17 PM, Chris fractalbynat...@gmail.com wrote:
In the Pylons roadmap wiki page, it mentions a mysterious ;) new meta
framework called Marco. Is this hosted anywhere? I'd like to just
poke around and see where it is headed.
Regarding routes in general, the public
On Tue, Dec 29, 2009 at 11:36 PM, Mike Orr sluggos...@gmail.com wrote:
On Tue, Dec 29, 2009 at 7:17 PM, Chris fractalbynat...@gmail.com wrote:
I put the Routes-exp (formerly Routes 2) code on bitbucket. It may be
easier to follow. The Routes internal structure will eventually be
made closer
This looks pretty cool, and the pretty printer is very helpful!
Again, thx for the blog post.
I'm just a little hesitant to move forward with adopting it in my app
at the moment because if routes 2 comes up with something completely
new/different, then I'll be depending on this new branch or
I'll add a comment to issue 21 with the small fix to connect() that
makes submapper nesting work correctly (so that requirements dicts get
merged, for example).
Then there's the routes prettyprinter - there's no command for it but
even in the paster shell I have found it useful.
That leaves
Sorry, couldn't resist...
with mapper.collection(
'myresources',
'myresource',
collection_actions = ['index', 'new'],
member_actions = ['show', 'update']) as c:
c.link('new', name='create_resource', method='POST')
On Mon, Dec 21, 2009 at 3:31 AM, Mike Burrows (asplake)
m...@asplake.co.uk wrote:
I was intrigued by the mention of resource()
The Atom-REST syntax for resources is mainly beneficial to
non-interactive user agents (robots and front ends), and cases where
the resource is isolated from a web site
On Dec 21, 3:54 pm, Mike Orr sluggos...@gmail.com wrote:
def resource2(self, name, path, new=True, edit=True, delete=True):
GET /myresource : view index
GET /myresource/new : new form
POST /myresource/new : new action
GET /myresource/1
19 matches
Mail list logo
