Hey Jim, 

Thanks for the feedback. I was pleasantly surprised you got it working on 
pyramid 1.3. I'll have to cut another release to pypi I suppose. :)

Depending on when you pulled you may have noticed that unit tests are run 
through py.test and it takes care of bootstrapping the appengine services 
for your tests and keeps the index.yaml updated for you(see conftest.py). I 
am pretty happy with how that turned out because when I was doing my first 
appengine app, the challenge was writing/running tests under the 
devappserver environment.  

Thanks again.

now to finish the cookbook recipe. 


On Wednesday, March 21, 2012 4:59:00 PM UTC-4, Jim Washington wrote:
>
> On Wed, 2012-03-14 at 14:04 -0400, Thomas G. Willis wrote:
> > Hello, one of the tasks that was outlined as part of the sprints after
> > pycon was improving the documentation for running pyramid on
> > appengine. 
> > 
> > 
> > I've thrown some code out here with some docs in the readme
> > https://github.com/twillis/pyramid_appengine
> > 
> > 
> > 
> > 
> > if you want to give that a spin, just file an issue in github if you
> > have any issues. 
>
> It's working for me. My notes:
>
> Pyramid-1.3 works just fine with webob-1.1.1. Pyramid tests all work,
> and the buildout takes care of putting the gae-supported webob in the
> development appserver, so you should get a heads-up through testing if
> there are any edge cases in your app. You will end up with an extra
> webob egg in the eggs folder, but that doesn't matter because the stuff
> in parts/MyApp is what goes to appengine.
>
> Anytime you add a required dependency in your app's setup.py, also add
> that dependency (and sub-dependencies, if any) to the
> rod.recipe.appengine stanza in buildout.cfg. Then re-run bin/buildout.
> Note that apps can be spelled differently in the two places. E.g., it's
> "pyramid_rpc" in requires, and "pyramid-rpc" in the appengine stanza.
>
> You want pyramid installed in your system python. Don't bother with a
> virtualenv when using this buildout; the paths get duplicative and
> confusing. Installing pyramid in your system python makes
>
> > pcreate -t appengine_starter MyApp
>
> or
>
> > paster create -t appengine_starter MyApp
>
> available to you when you want it.
>
> You do not want zc.buildout installed system-wide. If you get "can't
> find it" errors, that is the most likely problem. When you do "python
> bootstrap.py", don't forget the --distribute. e.g., 
>
> python bootstrap.py --distribute
>
> To run the devappserver, point it to parts/MyApp, not src/MyApp.
>
> > bin/devappserver parts/MyApp
>
> Point "bin/appcfg update" to the same location. 
>
> Make sure you run bin/buildout before running, testing or updating your
> app! parts/MyApp is updated from src/MyApp by buildout.
>
> Tasty stuff, BTW.
>
> Proof of the pudding at http://test-app-509.appspot.com/
>
> - Jim Washington
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/pylons-discuss/-/TJfG5FygZ_cJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en.

Reply via email to