Hi,
I'm planning on moving my site to Google App Engine.
Pylons is the Framework I choose for this.
I learned Pylons works on app engine by using appenginemonkey
so I tried by following the following doc.
http://code.google.com/p/appengine-monkey/wiki/Pylons
Ian Bicking's explanation is so clea
I've read a few threads about the state of pylons on google app engine, and
that parts of it work and parts don't. Doing a quick google on the subject
reveals a few tutorials that use appengine-monkey to accomplish setting up
the framework, however it appears as if that is no longer nec
Hi Michael,
I read the comment you mentioned and tried to do the same thing
but there's no "module_directory" in my config/environment.py.
The comment is also suggesting to install the latest Pylons 0.9.7 so I tried
but it again failed with the following error
NameError: name 'egg_plugins' is n
On Sun, Jul 20, 2008 at 9:55 AM, js <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I'm planning on moving my site to Google App Engine.
> Pylons is the Framework I choose for this.
>
> I learned Pylons works on app engine by using appenginemonkey
> so I tried by following the following doc.
> http://code.
Mike Orr wrote:
> On Mon, Jul 21, 2008 at 12:02 AM, Wichert Akkerman <[EMAIL PROTECTED]> wrote:
>> Previously Mike Orr wrote:
>>> Of course, that will diminish Mako's amazing speed. It remains to be
>>> seen how much of a difference it makes. Perhaps down the road Mako
>>> can be patched to put
El lun, 21-07-2008 a las 11:11 +0200, Wichert Akkerman escribió:
> Mike Orr wrote:
> > On Mon, Jul 21, 2008 at 12:02 AM, Wichert Akkerman <[EMAIL PROTECTED]>
> > wrote:
> >> Previously Mike Orr wrote:
> >>> Of course, that will diminish Mako's amazing speed. It remains to be
> >>> seen how much
php is a templating language. all that stuff is written in c and is
optimized. php is WAY faster at variable interpolation than python,
perl, everything else.
templates are a small fraction of your 'business logic'. 95% of what
you do in pylons, php, and everythign else will have the database
On Sun, Jul 20, 2008 at 6:14 PM, Mike Orr <[EMAIL PROTECTED]> wrote:
> Hi JS, I'm writing a book on Python on App Engine
> (http://www.manning.com/gift/) and am just now sorting out what issues
> Pylons has on it. So any tips from others who are using Pylons on App
> Engine would be greatly appr
Hello Jonathan,
2008/7/21 Jonathan Vanasco <[EMAIL PROTECTED]>:
>
> php is a templating language. all that stuff is written in c and is
> optimized. php is WAY faster at variable interpolation than python,
> perl, everything else.
>
> templates are a small fraction of your 'business logic'. 95
is that test from the spitfire suite ? I haven't looked at it, but
their Mako numbers look a whole lot like Myghty, not Mako (Mako is
roughly the same speed as Cheetah in reality, a tad slower usually).
I haven't had the time to deal with spitfire, which will involve
verifying that they are test
On Mon, Jul 21, 2008 at 12:52 PM, Michael Bayer <[EMAIL PROTECTED]> wrote:
>
> is that test from the spitfire suite ? I haven't looked at it, but
> their Mako numbers look a whole lot like Myghty, not Mako (Mako is
> roughly the same speed as Cheetah in reality, a tad slower usually).
>
> I haven
Hi.
I'm sitting in a room with Wichert right now and he told me, that he
posted about my blog post in here, so that's where I think Michael
have seen it :)
Michael posted some comments on
http://hannosch.blogspot.com/2008/07/project-messerschmidt-vs-nkotb.html
which I'd like to follow up on in
On Jul 21, 4:56 pm, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
>
> def render(table, _context=None, target_language=None):
> global generation
>
> (_out, _write) = generation.initialize_stream()
> (_attributes, repeat) = generation.initialize_tal()
> (_domain, _negotiate, _tr
On Jul 21, 11:57 am, "Jens Hoffrichter" <[EMAIL PROTECTED]>
wrote:
> I don't want to start a "religious discussion" about programming
> languages here, especially about speed and ease of use.
I don't either, but I need to clarify something. I think in context
of the question and the response, i
Why is there so much different in response time?
On Jul 21, 5:48 pm, Antonio Beamud Montero <[EMAIL PROTECTED]>
wrote:
> El lun, 21-07-2008 a las 11:11 +0200, Wichert Akkerman escribió:
>
>
>
> > Mike Orr wrote:
> > > On Mon, Jul 21, 2008 at 12:02 AM, Wichert Akkerman <[EMAIL PROTECTED]>
> > > w
Hi.
I'm sitting in a room with Wichert right now and he told me, that he
posted about my blog post in here, so that's where I think Michael
have seen it :)
Michael posted some comments on
http://hannosch.blogspot.com/2008/07/project-messerschmidt-vs-nkotb.html
which I'd like to follow up on in
Hi.
Sorry, for the double post, the incredibly bad Google Groups UI didn't
seem to accept my post and wasn't giving a hint at the moderation for
first time posters.
Michael Bayer wrote:
> Yeah, so here is the mako render() method for that template:
>
> def render_body(context,**pageargs):
>
Mako uses beaker for caching so it should support any of those
backends. There's a little bit of hardcoding to particular Beaker
backends in 0.2.2 which is removed in the current trunk (also in prep
for the new release of Beaker), but even with 0.2.2 that can be worked
around by adding the desir
Hi.
On Tue, Jul 22, 2008 at 5:41 AM, Michael Bayer <[EMAIL PROTECTED]> wrote:
> On Jul 21, 6:29 pm, "Hanno Schlichting" <[EMAIL PROTECTED]>
> wrote:
>>
>> Hhm, somewhat obfuscated code ;)
>
> well we did the cheetah thing and made sure we used names that would
> never conflict with end-user varia
On Tue, Jul 22, 2008 at 12:05 PM, Walter Cruz <[EMAIL PROTECTED]> wrote:
> Guido Van Rossum has published a zipimport for appengine, this could
> shirnk the package a lot ;)
The problem is that Pylons is not zip safe according to Ben because it
uses __file_. I've also heard Mako can't load templ
On Mon, Aug 10, 2009 at 1:55 PM, Brian O'Connor wrote:
> I've read a few threads about the state of pylons on google app engine, and
> that parts of it work and parts don't. Doing a quick google on the subject
> reveals a few tutorials that use appengine-monkey to acc
On Mon, Aug 10, 2009 at 9:32 PM, Mike Orr wrote:
> The best advice now is to use the appengine_homedir script. The howto
> is still useful but you'll have to make allowances for the differences
> between appengine_boot and appengine_homedir. You can disable the
>
I found this exchange in my ar
On Tue, Oct 6, 2009 at 9:40 PM, Matt Feifarek wrote:
> On Mon, Aug 10, 2009 at 9:32 PM, Mike Orr wrote:
>>
>> The best advice now is to use the appengine_homedir script. The howto
>> is still useful but you'll have to make allowances for the differences
>> between appengine_boot and appengine_h
On Wed, Oct 7, 2009 at 1:27 AM, Mike Orr wrote:
>
> None has been mentioned on the list. The thread you found is the
> latest. If you have time to figure out the easiest install procedure
> for Pylons on App Engine and to update the howto, it would be a
> contribution to Pylons. There's a redi
For what it's worth, I ended up using Django with app-engine-patch on GAE.
I got frustrated even looking to try and remotely implement Pylons on it.
On Wed, Oct 7, 2009 at 2:54 PM, Matt Feifarek wrote:
> On Wed, Oct 7, 2009 at 1:27 AM, Mike Orr wrote:
>
>>
>> None has been mentioned on the list
On Wed, Oct 7, 2009 at 1:27 AM, Mike Orr wrote:
> None has been mentioned on the list. The thread you found is the
> latest. If you have time to figure out the easiest install procedure
> for Pylons on App Engine and to update the howto, it would be a
> contribution to Pylons. There's a redire
On Wed, Oct 7, 2009 at 9:26 PM, Matt Feifarek wrote:
> On Wed, Oct 7, 2009 at 1:27 AM, Mike Orr wrote:
>>
>> None has been mentioned on the list. The thread you found is the
>> latest. If you have time to figure out the easiest install procedure
>> for Pylons on App Engine and to update the ho
On Wed, Oct 7, 2009 at 9:26 PM, Matt Feifarek wrote:
> Also, I probably have some terminology wrong: I'm not sure what the meta
> files like MANIFEST.in and ez_setup.py actually are... are they egg files?
> Paster files? Setuptools? I don't know what to properly call them when I
> talk about dele
Thanks for the answers and clarifications... more below.
On Thu, Oct 8, 2009 at 3:03 AM, Mike Orr wrote:
>
> Feel free to link to it on the other page, or to paste the whole thing into
> that page.
Will-do. And I'll fix the error you pointed out, change the thanks
attribution, etc.
> Pylons
On Thu, Oct 8, 2009 at 3:35 AM, Mike Orr wrote:
>
> An egg is a Python package accompanied by its metadata. An egg can
> contain more than one package, but always one metadata. There are two
> file formats for eggs:
>
...
Thanks for all of that. It helps. A lot. I'll look at the link to Ian's
On Thu, Oct 8, 2009 at 3:03 AM, Mike Orr wrote:
>
> > Also, I probably have some terminology wrong: I'm not sure what the meta
> > files like MANIFEST.in and ez_setup.py actually are... are they egg
> files?
> > Paster files? Setuptools? I don't know what to properly call them when I
> > talk abo
On Thu, Oct 8, 2009 at 11:32 AM, Matt Feifarek wrote:
> I'm not sure I'm up to that task (I use Pylons a lot, but kindof "tune-out"
> the parts about PasteDeply/Script, SetupTools, etc.
Even if you can just keep testing the process and adding advice to the
howto, that would be a big help. What
On Oct 8, 12:26 am, Matt Feifarek wrote:
> (Wikis suck. It totally roasted all my formatting from rst/html. Editing
> yet-another-markup in a textarea is painful. Argh.)
Some wikis -- like trac -- support rst formatting.
in trac you just format it like this:
{{{
#!rst
RST HERE
}}}
I'm not
On Thu, Oct 8, 2009 at 2:45 PM, Jonathan Vanasco wrote:
>
>
> On Oct 8, 12:26 am, Matt Feifarek wrote:
>> (Wikis suck. It totally roasted all my formatting from rst/html. Editing
>> yet-another-markup in a textarea is painful. Argh.)
>
> Some wikis -- like trac -- support rst formatting.
>
> in
On Thu, Oct 8, 2009 at 12:08 PM, Ian Bicking wrote:
> Correct; I have in the past basically flattened things for appengine.
> Unfortunately that doesn't work well with paster create -t pylons. It might
> however be more productive to have an appengine template, since you already
> know what the
On Thu, Oct 8, 2009 at 3:29 PM, Mike Orr wrote:
> > This leads to two questions:
> > 1. Can we simply delete that stuff ? It would make it harder to manage
> the
> > app going forward.
>
> Can we delete what?
>
Sorry; I edited out the part that would have made that more clear. What I
was asking
On Thu, Oct 8, 2009 at 3:29 PM, Mike Orr wrote:
>
> On Thu, Oct 8, 2009 at 11:32 AM, Matt Feifarek
> wrote:
> > I'm not sure I'm up to that task (I use Pylons a lot, but kindof
> "tune-out"
> > the parts about PasteDeply/Script, SetupTools, etc.
>
> Even if you can just keep testing the process
On Thu, Oct 8, 2009 at 3:46 PM, Matt Feifarek wrote:
>> What we need is somebody who
>> regularly uses Pylons on App Engine to maintain the howto.
>
> I don't know how long my commitment to use GAE will continue. I'm basically
> evaluating it now with a project. If I can help out the general com
I just got a hello-world Pylons app running on GAE without using the
appengine-monkey/homedir scripts and using the stock paster template
(and an INI file). I'm not sure if I'm going to use GAE seriously, but
it's an interesting problem to work on. If I am, then personally, I
would rather not use
This sound really promising.
On Sat, Oct 10, 2009 at 9:15 PM, Jason S. wrote:
>
> I just got a hello-world Pylons app running on GAE without using the
> appengine-monkey/homedir scripts and using the stock paster template
> (and an INI file). I'm not sure if I'm going to use GAE seriously, but
>
On Sat, Oct 10, 2009 at 10:38 PM, Matt Feifarek wrote:
>> 2. Patch Paste Deploy with a new loader class, to load a function spec
>> instead of an egg spec, without changing anything else about the INI
>> file format. In other words, my app:main looks like this:
>>
>> [app:main]
>> use = func:myhe
On Oct 11, 12:38 am, Matt Feifarek wrote:
> I think that you can simply delete the speedups file from the simplejson
> module.
Works, thanks.
> > [app:main]
> > use = func:myhello.config.middleware:make_app
> > full_stack = true
>
> I'm not following completely. Does this make the GAE SDK http/
Hi, all,
I've just finished (the first draft of) an article on getting Pylons
running on GAE with a mostly "stock" setup. I've focused on using a
typical virtualenv and stock paster template and attempted to find the
minimum number of changes required to get things running, rather than
creating a
Very nice.
This seems much better than my own recent work... I think it's a mistake to
start with "appengine-homedir"... better to just start from stock Pylons and
hack it till it works on GAE. That's been my discovery over the last few
days, but I haven't patched my Pylons Wiki article yet.
I'll
These new approaches are encouraging. The purpose of
appengine-homedir was to make it easy to get started, by handling the
virtualenv and directory structure for you. But if it turns out that
another way is easier, we can deprecate it. I do like the idea of a
pylons-appengine template for Paste
On Wed, Oct 14, 2009 at 4:35 PM, Matt Feifarek wrote:
> This seems much better than my own recent work... I think it's a mistake to
> start with "appengine-homedir"... better to just start from stock Pylons and
> hack it till it works on GAE. That's been my discovery over the last few
> days, but
On Thu, Oct 15, 2009 at 12:10 AM, Ian Bicking wrote:
>
> I personally got too annoyed with testing and general interactivity
> (there's a nose extension though, which I cribbed from -- but I never
> actually got it to work myself).
>
This process has been EXTREMELY annoying. I've spent many hour
On Oct 15, 11:59 am, Matt Feifarek wrote:
> On Thu, Oct 15, 2009 at 12:10 AM, Ian Bicking wrote:
>
> > I personally got too annoyed with testing and general interactivity
> > (there's a nose extension though, which I cribbed from -- but I never
> > actually got it to work myself).
>
> This proce
On Thu, Oct 15, 2009 at 12:41 PM, Jason S. wrote:
> > I still don't get setuptools. I don't understand namespace packages, or
> > rather their deployment. I don't get why I can't move (for example)
> paste,
> > and the Paste* items to another directory that is ON sys.path and have it
> be
> > imp
On Thu, Oct 15, 2009 at 9:59 AM, Matt Feifarek wrote:
> This process has been EXTREMELY annoying. I've spent many hours trying to
> get things to work that I should have been spending working on my project.
> Mostly, its my own ignorance of current magical techniques:
All of us have been annoyed
> > unless it's added to the path somehow. BTW, I don't think GAE
> > uses .pth files, which is why sys.path manipulation is necessary.
>
> It *seems *like this isn't true. If I omit pth files when uploading to GAE,
> my app is failing with a 500 error. But I wouldn't trust that yet... can you
> d
On Thu, Oct 15, 2009 at 2:21 PM, Mike Orr wrote:
>
> On Thu, Oct 15, 2009 at 9:59 AM, Matt Feifarek
> wrote:
> > This process has been EXTREMELY annoying. I've spent many hours trying to
> > get things to work that I should have been spending working on my
> project.
> > Mostly, its my own ignor
Quick version: If you are working with Google App Engine or
considering it, please visit and "star" this bug report. More below.
http://code.google.com/p/googleappengine/issues/detail?id=2272
On Oct 15, 2:01 pm, Matt Feifarek wrote:
> > When you install them with pip, I think they overlap (i.e.
On Fri, Oct 16, 2009 at 9:07 AM, Jason S. wrote:
> I just did a fresh pip install of Pylons and looked over the Paste
> stuff, and it looks like there is a .pth file that comes with each
> Paste package (ending with the string "nspkg.pth") that contains
> executable Python (!) (I didn't know pth
On Thu, Oct 15, 2009 at 2:01 PM, Matt Feifarek wrote:
> On Thu, Oct 15, 2009 at 12:41 PM, Jason S. wrote:
>>
>> > I still don't get setuptools. I don't understand namespace packages, or
>> > rather their deployment. I don't get why I can't move (for example)
>> > paste,
>> > and the Paste* items
On Fri, Oct 16, 2009 at 1:04 PM, Ian Bicking wrote:
>
> I remember at some point having a problem with pip installing the
> Paste packages, and paste/__init__.py was missing. I think I was
> working on an actual app so I punted and created the file manually,
> and didn't try to reproduce and fix
On Fri, Oct 16, 2009 at 3:57 PM, Matt Feifarek wrote:
> On Fri, Oct 16, 2009 at 1:04 PM, Ian Bicking wrote:
>> I don't use paster serve, and wouldn't recommend it. You can/should
>> use paste.deploy.loadapp('development.ini') in your main.py or
>> runner.py or whatever script, and then use dev_
On Fri, Oct 16, 2009 at 5:57 PM, Matt Feifarek wrote:
>> I don't use paster serve, and wouldn't recommend it. You can/should
>> use paste.deploy.loadapp('development.ini') in your main.py or
>> runner.py or whatever script, and then use dev_appserver.
>
> Would you mind expanding on that a littl
58 matches
Mail list logo
