Awesome work! Thanks so much for all the effort you guys are putting in.
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to
pylons-de
Congratulations on your final release and the rapid beta release cycle
leading up to it!
— Alice.
On 2011-01-30 16:26:07 -0800, Chris McDonough said:
Pyramid 1.0 (final) has been released to PyPI.
It may be installed via:
easy_install pyramid
Existing installs can be updated via:
Awesome work, thanks!
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+unsubscr...@googlegroups.com.
For more options,
Very nice !!! Great work..
We already started working on an application using pyramid... expecting the
community to grow more..
--
Raviteja
On Mon, Jan 31, 2011 at 11:53 AM, adam wrote:
> Congratulations !! I was waiting for this since last one month .. :)
>
> --
> You received this message be
Congratulations !! I was waiting for this since last one month .. :)
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+
I'm still working on a Pylons-Pyramid migration guide. I should have a
draft out by next weekend.
--
Mike Orr
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe f
Congratulation for such a milestone! The work done so far is amazing,
specially the documentation. This will help grow a community around
the Pylons project. I envision a grand future for it.
You may want to post that announcement to the non-devel mailing list as well.
Cheers,
2011/1/30 Chris Mc
Hi,
I've been tinkering with Pyramid code as I learn the framework and I'd
appreciate some feedback on a possible enhancement, even if it's just
to tell me it's a bad idea.
One nit that bothered me was the way rendered views require you to set
attributes in the request object in order to change t
Pyramid 1.0 (final) has been released to PyPI.
It may be installed via:
easy_install pyramid
Existing installs can be updated via:
easy_install -U pyramid
The 1.0 release documentation exists at
http://docs.pylonsproject.org/projects/pyramid/1.0/
See http://docs.pylonsproject.org/projects
On Jan 30, 3:56 pm, oO wrote:
> Thanks for the info. I'm following up on the idea of using
> request.subpath, but at what point does this property get created?
> This is my understanding of the call stack:
>
> 1. the RootFactory is called, with the request object as a parameter
> 2. the RootFactor
Thanks for the info. I'm following up on the idea of using
request.subpath, but at what point does this property get created?
This is my understanding of the call stack:
1. the RootFactory is called, with the request object as a parameter
2. the RootFactory returns the root resource
3. Pyramid rec
On Jan 30, 1:21 pm, Mike Orr wrote:
> Are you traversing each level of the date here, or using a subpath from
> archive?
Traversing each level -- the same pattern Tres described this morning
as "transient" context classes.
>It seems like extra overhead to create a temporary Year class and
>Mon
On Sun, Jan 30, 2011 at 8:25 AM, Wade Leftwich wrote:
> Actually a bit more in keeping with the spirit of Traversal, and again
> keeping your calls to Mongo to a mininum, would be something like
> this:
>
> /blog/month/2011/01/29/my-post-about-pyramid would do this:
>
> archive = Blog['archive']
>
> This would handle shorter paths in a natural way -- e.g. '/blog/month/
> 2011/01' would map to the default view for Month(y=2011, m=1), which
> would call Post.list_posts_for_month() .
>
Er, make that "the default view for Month(y=2011, m=1), which would
call Month.list_posts_for_month() which w
Actually a bit more in keeping with the spirit of Traversal, and again
keeping your calls to Mongo to a mininum, would be something like
this:
/blog/month/2011/01/29/my-post-about-pyramid would do this:
archive = Blog['archive']
year = archive['2011'] = archive.__getitem__('2011') = Year(y=2011)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/30/2011 09:04 AM, Wade Leftwich wrote:
> If you want to stick with Traversal, don't forget that you have
> request.subpath available to you. For the path "/blog/archive/
> 2011/01/29/my-post-about-pyramid", you could have an Archive context
> who
If you want to stick with Traversal, don't forget that you have
request.subpath available to you. For the path "/blog/archive/
2011/01/29/my-post-about-pyramid", you could have an Archive context
whose default (unnamed) view would be called with a request that
included request.subpath = ['2011', '
17 matches
Mail list logo
