sqlalchemy / sqlalchemy/mako

need to not call imp.load_source to work with GAE

Open
#85 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug low priority runtime
Dominant language
Python
Stars
459
Forks
90
PR merge metrics
No merged PRs in 30d

Description

Migrated issue, originally created by Anonymous

Per a comment here: http://code.google.com/p/appengine-monkey/wiki/Pylons

I was briefly confused by the following error:

Error - <type 'exceptions.AttributeError'>: 'module' object has no attribute 'load_source'

I had pointed my development.ini to the default one created by Pylons - which has caching turned on. This makes Mako attemp to call imp.load_source, which isnt part of GAE. Turned off caching and it works like a charm.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the error with Mako caching enabled, using the development.ini setup described in the issue and the Google App Engine environment. Trace the caching path that reaches imp.load_source; done means the template workflow no longer requires that unavailable function while caching remains usable.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.