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
breaking
-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 applica
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 plu
On Wed, Dec 30, 2009 at 1:26 AM, karikris...@gmail.com
wrote:
> 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.
The Marco core is a meta-framework, akin to Paste. It will have
severa
On Dec 30, 1:37 am, Mike Orr wrote:
> On Tue, Dec 29, 2009 at 11:36 PM, Mike Orr wrote:
> > On Tue, Dec 29, 2009 at 7:17 PM, Chris 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
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 Tue, Dec 29, 2009 at 11:36 PM, Mike Orr wrote:
> On Tue, Dec 29, 2009 at 7:17 PM, Chris 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 to this.
http://bitbucket.org/sluggo/ro
On Tue, Dec 29, 2009 at 7:17 PM, 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.
>
> Regarding routes in general, the public routes api is really n
-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 .
Thanks Mike Burrows for fixing the issue. Figured it was a typo or
something like that.
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, t
On Tue, Dec 29, 2009 at 12:51 AM, Mike Burrows (asplake)
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. Some of the f
On Tue, Dec 29, 2009 at 10:06 AM, 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 year. It may be
a few
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)"
wrote:
> Oops - merge error, fixed. I should add a test for that. You can add
> requirements at
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, C
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 isin
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 t
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 migra
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')
c.member.li
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 coll
On Dec 21, 3:54 pm, Mike Orr 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 : view re
On Mon, Dec 21, 2009 at 3:31 AM, Mike Burrows (asplake)
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" (Amazon S3).
Yes, that creates the 'app_globals' object. That's required. I'm not
sure what Pylons would do if that's not there; maybe raise an
exception when it registers the StackedObjectProxy.
I'm essentially talking about modifying the template namespace to add
more top-level variables. But the answer s
Hi Ben,
That is interesting approach. So I can get out of using app globals. I
will test and update the RUM community on this.
Can I use decorators for authorization here? I have repoze.who & what
in place.
RumController = RumApp({
...
})
Thanks,
Krish
On Dec 21,
I was intrigued by the mention of resource() - coincidentally I was
working on the post [1] below in which I refactor my way to a much
more flexible alternative that builds on the new SubMapper idea. I'd
be interested to know what people think.
[1] DRY up your routes - a Pylons routing refactori
Good question - I don't think I do anything special for that, beyond
the default in config/environment.py:
config['pylons.app_globals'] = app_globals.Globals()
I think its there by default?
Damian
On Dec 21, 3:00 am, Mike Orr wrote:
> > On Dec 20, 9:05 pm, Mike Orr wrote:
> >> How do you
> On Dec 20, 9:05 pm, Mike Orr wrote:
>> How do you add variables to the globals? I think you'd have to
>> override render_mako.
On Sun, Dec 20, 2009 at 2:51 PM, Damian wrote:
> you define them in the Global object.
>
> class Globals(object):
> myconstant = 'astring'
Ah, I meant something d
On Dec 20, 2009, at 5:49 PM, karikris...@gmail.com wrote:
> I use app_globlas to create and store the RUM based wsgi application.
Odd, I used RUM in an app, it's easier than that actually.
Make your RumApp instance inside a controller (say, called rum.py). If you make
it inside of 'rum.py' then
I use app_globlas to create and store the RUM based wsgi application.
class Globals(object):
"""Globals acts as a container for objects available throughout
the
life of the application
"""
def __init__(self):
"""One instance of Globals is created during application
you define them in the Global object.
class Globals(object):
myconstant = 'astring'
etc...
and then in the app use g.myconstant wherever you need it. These
don't, by convention, ever get modified. Generally it would be a bad
idea to do that as it would result in concurrency issues.
It see
How do you add variables to the globals? I think you'd have to
override render_mako.
On Sun, Dec 20, 2009 at 12:59 PM, Damian wrote:
> FWIW - we make quite heavy use of 'g' for defining constant strings
> that are used to generate our JSON, so the javascript knows what to
> look for in the templa
FWIW - we make quite heavy use of 'g' for defining constant strings
that are used to generate our JSON, so the javascript knows what to
look for in the template and pylons sends the right stuff back even if
we chose to change the constant string.
d
On Dec 20, 8:12 pm, Mike Orr wrote:
> On Sun, D
On Sun, Dec 20, 2009 at 10:11 AM, Ben Bangert wrote:
> On Dec 18, 2009, at 7:59 PM, Mike Orr wrote:
>
> Mike, 'c' will remain in templates in 1.0, 'g' will be app_globals, though
> one can of course add variables as desired to the Pylons globals in templates
> if 'g' is still desired.
That's fi
On Dec 18, 2009, at 7:59 PM, Mike Orr wrote:
> The Roadmap is updated.
>
> http://wiki.pylonshq.com/display/pylonscommunity/Pylons+Roadmap+to+1.0
>
> It says 0.10/1.0 will be released by the end of 2009. I don't know if
> we'll make it.
Graham has made some headway on a few of the remaining tic
On Fri, Dec 18, 2009 at 7:41 PM, Mike Orr wrote:
> There aren't any significant new features in tip from an application
> perspective, so there's little reason to use it now unless you want to
>
Thanks for the clear, useful answer.
--
You received this message because you are subscribed to the
The Roadmap is updated.
http://wiki.pylonshq.com/display/pylonscommunity/Pylons+Roadmap+to+1.0
It says 0.10/1.0 will be released by the end of 2009. I don't know if
we'll make it.
WebHelpers 1.0b2 will be out next week with the new feedgenerator
code, after I've tested it on my site. The beta sh
The Roadmap is behind because the changes have been few and minor, and
because Ben keeps some of his ideas to himself before he implements
them. I'll update it now based on the Changelog.
--
Mike Orr
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA224
ok, thanks for the explanation. looks obvious now, i was trying to
read it as 0.97 > 0.1
On Dec 18, 2009, at 7:47 PM, Mike Orr wrote:
> On Fri, Dec 18, 2009 at 5:15 PM, Mario Romero
> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA2
On Fri, Dec 18, 2009 at 5:15 PM, Mario Romero wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA224
>
> can someone explain how the version numbers work?
> why does 0.10 come after 0.9.7 ?
Because Ben feels 0.9 was allowed to go for too long, because we
thought we were closer to 1.0 than we
On Fri, Dec 18, 2009 at 4:19 PM, Matt Feifarek wrote:
> First: I SINCERELY hope that I do not start a round of whining, because I am
> definitely NOT whining. I am grateful for Pylons and for the support of my
> betters in this list. I would ask that any responders to my message NOT use
> this as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA224
can someone explain how the version numbers work?
why does 0.10 come after 0.9.7 ?
thanks.
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.12 (Darwin)
iFYEARELAAYFAkssKUYACgkQFXxYxga0LLkEPQDfeWTLxdrP6t7CTY7VRtTxuCBD
tpQf5T/v+0x/YgDfVhZrw
Out of curiosity, what are the cruft you are talking about in 0.9.7?
- Didip -
On Fri, Dec 18, 2009 at 4:19 PM, Matt Feifarek wrote:
> First: I SINCERELY hope that I do not start a round of whining, because I
> am definitely NOT whining. I am grateful for Pylons and for the support of
> my bette
First: I SINCERELY hope that I do not start a round of whining, because I am
definitely NOT whining. I am grateful for Pylons and for the support of my
betters in this list. I would ask that any responders to my message NOT use
this as a jumping-off point for whining or bullying, because it is enti
42 matches
Mail list logo
