Hi,
On 05.07.2009, at 07:06, Lennart Regebro wrote:
2009/7/5 Stephan Richter srich...@cosmos.phy.tufts.edu:
To be honest, I am very disappointed by this list. It is totally
meaningless
to me since it does not represent any list with which I can build
even a
fairly simple application
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
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
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,
On 19.04.2009, at 10:52, Andreas Jung wrote:
I just released Zope 2.12.0a2:
http://pypi.python.org/pypi/Zope2/2.12.0a2
doc/CHANGES.rst is missing in the source distribution on pypi:
Getting distribution for 'Zope2'.
error: doc/CHANGES.rst: No such file or directory
An error occured when
Hi,
Shane Hathaway wrote:
Hanno Schlichting wrote:
Wichert Akkerman wrote:
I'ld rather not see a whole slew of extra packagse appear. I also
wonder
how the extra number of packages and increasing size of sys.path
influence performance and restrictions on environments like GAE.
For
Hi,
had the same issue tonight. I'm using attached versions.cfg for now.
That works quite well for me.
Cheers,
Tobias
[buildout]
versions = versions
[versions]
Acquisition = 2.12.0a1
DateTime = 2.11.2
ExtensionClass = 2.11.1
Persistence = 2.11.1
tempstorage = 2.11.1
zLOG = 2.11.1
ClientForm
On 28.03.2009, at 00:30, Chris Withers wrote:
Tobias Rodäbel wrote:
Hi,
had the same issue tonight. I'm using attached versions.cfg for now.
That works quite well for me.
Which issue is this supposed to help with?
Using zc.buildout. This is my buildut.cfg:
[buildout]
parts = zope zopepy
On 28.03.2009, at 00:36, Chris Withers wrote:
There are currently two seperate issue with specifying zope2 as an
egg in a buildout.cfg.
Which of these two issues is your solution designed to address?
My versions.cfg resolved all version conflicts mentioned within this
thread.
