Working on it. Should be out early next week.
c
On Mar 18, 2010, at 12:02 PM, René Fleschenberg wrote:
Hi,
Could we get a new PyPi release that includes the fix from r111693? That
problem keeps hitting people, and even though it is an easy one to work
around, it can be confusing to new
With apologies for cross-posting:
Announcing the release of ZopeSkel 2.16, uploaded this afternoon to pypi and
plone.org
In this release:
* improved test coverage
* fixes for a number of issues from the zopeskel tracker:
*
marcos.rom...@inter-cultura.com
www.inter-cultura.com
+54 11 4542-8299
On Wed, Jun 23, 2010 at 9:35 PM, Cristopher Ewing
cew...@u.washington.edu wrote:
On Jun 23, 2010, at 5:33 PM, Marcos Romero wrote:
Winn
Your configure.zcml file doesn't look like a ZopeSkel 2.15 generated
one
On Dec 1, 2010, at 3:48 PM, Alex Clark wrote:
I'm afraid I'm already confused :-). Is templer.core the zopeskel
package renamed?
I wish it were a bit less confusing, but let me try to explain.
zopeskel as it currently exists will eventually be replaced by an empty egg
which simply
I'm seeing a failure in the tests for the zopeskel recipe template that started
popping up when I tried testing my new templer.core package outside my regular
build environment.
It turns out that pinning zc.buildout to version 1.4.3 solves the problem, so
I'm pretty certain that whatever is
On Dec 2, 2010, at 4:51 AM, Chris Rossi wrote:
On Thu, Dec 2, 2010 at 1:34 AM, Cristopher Ewing cew...@u.washington.edu
wrote:
I'm pretty sure that pinning all our templates to a version of zc.buildout
that is now a year old isn't such a hot idea, but it did get me back to
passing
Apologies for cross-posting
I am pleased to announce that ZopeSkel 2.19 has been released on pypi and
plone.org.
In this release:
* improvements to the README documentation for the zopeskel package
itself.
* Shiny new plone4_buildout template
Thanks to
thet
