On 5/5/08, Philip Jenvey <[EMAIL PROTECTED]> wrote:
>
>
> No, it was a bug. It's been fixed in 0.9.7: http://pylonshq.com/
> project/pylonshq/ticket/363
Btw, any timeline for next public stable release?
--~--~-~--~~~---~--~~
You received this message because you a
On 3/24/08, Ben Bangert <[EMAIL PROTECTED]> wrote:
>
> I've been reading carefully through the docs for Sphinx (
> http://sphinx.pocoo.org/
> ) the past few days, and am quite sold on it at this point. As such,
> I'd like to assemble a group of other people who are interested in
> working on the do
On Jan 17, 2008 1:01 AM, Mike Orr <[EMAIL PROTECTED]> wrote:
>
> I'm looking into pkg_resources.require as a possible solution to the
> old/new problem of Routes and WebHelpers, to avoid having to release
> Routes1 and WebhelpersOriginal packages. Pylons doesn't have a
> top-level script unless p
Hello Mike,
On Jan 16, 2008 12:57 AM, Mike Orr <[EMAIL PROTECTED]> wrote:
>
> > 2. url_for -object certainly ain't simpler or more explicit either.
> Again, I
> > don't see how url_for().foobar is better then url_for("foobar").
>
> That was Ben's idea to make the name and path more distinct.
> Cu
Hello,
On Jan 16, 2008 3:53 AM, Ben Bangert <[EMAIL PROTECTED]> wrote:
> On Jan 15, 2008, at 7:38 AM, Max Ischenko wrote:
>
> > 1. Mapper.connect('foobar') looks both simpler and more explicit
> > than RouteMap.foobar. Why this "magic"?
>
> I g
On Jan 14, 2008 9:52 AM, Mike Orr <[EMAIL PROTECTED]> wrote:
>
> I've finished my Routes 2 spec.
>
> http://wiki.pylonshq.com/display/routes/Routes+2+Spec
>
> It defines a minimum functional spec, and optional features that can
> be added. This is to guide the
> implementation to make sure the co
Mike,
My main question is: will Route 2 remain compatible (API) with Routes 1?
On Jan 14, 2008 9:52 AM, Mike Orr <[EMAIL PROTECTED]> wrote:
>
> I've finished my Routes 2 spec.
>
> http://wiki.pylonshq.com/display/routes/Routes+2+Spec
>
> It defines a minimum functional spec, and optional featu
Hello,
What did you settled on for 0.9.7/1.0? Will the pylons.c be available
somewhere under request var?
IMO, this should make unit testing easier (simpler to mock the request).
--
Max
http://maxischenko.in.ua // http://www.linkedin.com/in/maksim
--~--~-~--~~~---~--
Ben,
On 12/19/07, Ben Bangert <[EMAIL PROTECTED]> wrote:
>
>
> So for the new controller template:
>
> import pylons.tmpl_context as c
> from pylons import render, request, response, session
> # from pylons.controllers.util import abort, redirect_to, url_for
>
> from yourproj.lib.base import BaseC
On 12/18/07, Jonathan LaCour <[EMAIL PROTECTED]> wrote:
>
> I hadn't thought of any of this before, but I really like the concept.
> It seems to me that `context` is certainly better than `c` but you
> are right that it doesn't really convey the fact that its essentially
> request local state. My
On 12/18/07, Ben Bangert <[EMAIL PROTECTED]> wrote:
>
> After talking with Ian Bicking a bit tonight, I'm finally fully sold
> on retiring the one-letter variable names from Pylons. The most likely
> replacement names:
> c -> context
> g -> ??? (as globals/global is already taken)
> h -> GONE (impo
On 12/18/07, Mike Orr <[EMAIL PROTECTED]> wrote:
>
> I've found two rare cases for it. One was for a reference object
> that's built on application startup, which I could just have easily
> put into a module global. The other was for the SQLAlchemy engine,
> which also worked better as a module g
On 12/15/07, Philip Jenvey <[EMAIL PROTECTED]> wrote:
>
> Our PasteScript template doesn't generate any .mako files, but it's
> easy enough to add a mako.input_encoding = 'utf-8' template option to
> enable utf-8 coding for all mako files.
Where should I put this? environment.py?
I'm not sure I
Hello,
Would it be OK to add default file encoding declaration (utf8) to .py/.mako
files that PasteScript generates? It won't hurt anyone but help those who
doesn't code in ascii and may be even catch a few unicode errors.
Should I submit a patch?
--
Max
http://maxischenko.in.ua // http://www.l
On 12/13/07, Ben Bangert <[EMAIL PROTECTED]> wrote:
Currently, Phil Jenvey, Clark Evans, and myself all have direct commit
> access to Paste, PasteScript, and PasteDeploy. We've made quite a few
> contributions, especially ones that of course benefitted Pylons.
...
>
> So I think after Pylons 0.
On 12/13/07, Mike Orr <[EMAIL PROTECTED]> wrote:
>
>
> As for infrequent releases, does it have serious bugs that necessitate
> new releases? Ian wrote right on the home page, "Paste is an actively
> maintained project. As of 1.0 (and actually before) we'll make a
> strong effort to maintain backw
Hello,
I wanted to share my concerns regarding using Paste code in Pylons. I
want to apologize in advance; I do not want to sound harsh or
anything, just to discuss a topic which seems important to me. I also
cannot talk on behalf on Pylons devteam, I'm just one of the users.
I think there is a
Hello Mark,
On 10/3/07, Mark Ramm <[EMAIL PROTECTED]> wrote:
>
>
> I hadn't seen JJ's code, but migrate is a pre-existing, project which
> attempted to solve the same problem in a similar way. Migrate lets
> you use SQLALchemy to create your migration scripts in python, and
> adds a couple state
Hi Mark,
I haven't heard about it yet but I presume it's about automatic database
schema updates?
I do not believe database schema changes should or could be automated but
good luck with the project.
For a start, I would be delighted to see something akin to jj's helpers to
be available for TG/P
19 matches
Mail list logo
