Hi,
yes, I'd really appreciate such a modification. Then I could delete
the regarding code in my rod.recipe.appengine, which provides a dummy
implementation of imp.load_dynamic.
Tim, do you have a list of the concerning packages? I could help
making these changes. A good reason to file an
Tim Hoffman wrote:
gae/1.333250465889549129/zope/i18nmessageid/_zope_i18nmessageid_message.py,
line 6, in __bootstrap__
imp.load_dynamic(__name__,__file__)
File /base/python_dist/lib/python2.5/py_imp.py, line 116, in load_dynamic
raise NotImplementedError('This function is not
I suppose that depends on your point of view.
They exception is actually saying that imp.load_dynamic is not
implemented, not that it can't load the dynamic module so I would say
in my opinion that it isn't a bug.
Rgds
Tim
On Fri, Jul 3, 2009 at 4:38 PM, Chris Withersch...@simplistix.co.uk
On 03.07.2009, at 10:38, Chris Withers wrote:
Tim Hoffman wrote:
gae/1.333250465889549129/zope/i18nmessageid/
_zope_i18nmessageid_message.py,
line 6, in __bootstrap__
imp.load_dynamic(__name__,__file__)
File /base/python_dist/lib/python2.5/py_imp.py, line 116, in
load_dynamic
Tobias Rodäbel wrote:
Sorry, I don't agree. We assume an imp.load_dynamic function from what
we read in the python documentation. But the implementation in GAE
does not provide the expected api. So the NotImplementedError seems
absolutely correct to me (see
On Jul 2, 2009, at 8:39 PM, Tim Hoffman wrote:
Hi all
Can I make a suggestion that would make a couple of modules more gae
friendly ;-)
zope.interface and zope.i18nmessageid have 'c' optimisations which
obviously don't work under app engine.
When these modules are imported you get the
Hi Jim
That is what I am doing now, the problem I see though is when someone
upates (via buildout etc a) module they need to remember to
remove the recreated file before redeploying the app, unfortunately I
am not sure I see a way reliable way of specifying that these files
should be
On Jul 3, 2009, at 6:25 AM, Tim Hoffman wrote:
Hi Jim
That is what I am doing now, the problem I see though is when someone
upates (via buildout etc a) module they need to remember to
remove the recreated file before redeploying the app, unfortunately I
am not sure I see a way
On 03.07.2009, at 12:33, Jim Fulton wrote:
On Jul 3, 2009, at 6:25 AM, Tim Hoffman wrote:
Hi Jim
That is what I am doing now, the problem I see though is when someone
upates (via buildout etc a) module they need to remember to
remove the recreated file before redeploying the app,
Hi Tobias
Cool
Just something to note google recently upped the file limit to 3000 so
don't be too agressive
generating those zips ;-)
T
Great idea to examine EGG-INFO/SOURCES.txt, Jim! I just added this to
my recipe (http://pypi.python.org/pypi/rod.recipe.appengine) and got
rid of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
On Jul 2, 2009, at 8:39 PM, Tim Hoffman wrote:
Hi all
Can I make a suggestion that would make a couple of modules more gae
friendly ;-)
zope.interface and zope.i18nmessageid have 'c' optimisations which
obviously don't work
On 7/3/09 1:29 PM, Tres Seaver wrote:
In general, I find deploying as zip files to be an anti-feature. In
seems especially insane when extension modules are involved.
The only way to deploy *any* non-toy app on GAE is via zip file(s) (I
would think a single big one would be best), due to
Hi all
Can I make a suggestion that would make a couple of modules more gae
friendly ;-)
zope.interface and zope.i18nmessageid have 'c' optimisations which
obviously don't work under app engine.
When these modules are imported you get the following exception.
13 matches
Mail list logo
