test
find-links = http://download.zope.org/distribution/
newest = false
eggs-directory = C:\Zope\buildout-eggs
You are missing a line here:
versions = versions
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard
which are
incredibly practical to validate your templates require this as well.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev
can always use the additional-fake-eggs =
transaction if it's a problem.
transaction is also used by repoze.tm in non-Zope environments such as
TurboGears 2 and Pylons. Those tend to not use buildout and certainly
don't want to see all of zope.* pulled in.
Wichert.
--
Wichert Akkerman [EMAIL
when one of the many packages in your project
sees a new release increases reapidly
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev
?
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross
Previously Hanno Schlichting wrote:
Wichert Akkerman wrote:
I was wondering why a non-zope project was pulling in zope.publisher and
ended up finding this chain:
chameleon.core - zope.i18n - zope.component[zcml] - zope.security -
zope.location - zope.traversing - zope.publisher
script type=text/javascript src=jquery-1.2.6.js
tal:attributes=src
context/++resource++tatr_js/jquery-1.2.6.js
/script
/head
body
This is a test :)
/body
/html*
Try adding a trailing ; after your TALES expression.
Wichert.
--
Wichert Akkerman
to
integrate
z3c.pt, which also needs those traversal APIs?
Yup. Actually, this wants to be in zope.tales. Does z3c.pt use
zope.tales?
No.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
that will
prevent ongoing work on trunk from breaking the tag.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev maillist - Zope-Dev
On 11/11/08 4:10 PM, Izak Burger wrote:
Jim Fulton wrote:
I'm going to restore svn from a backup and see where that leaves us.
I'm going to disable svn access while I work on this.
Good luck :-) I know a little something about the hard work involved in
recovering subversion repos,
this discussion
as notice to copy the egg to such a location *now*.
download.zope.org/distribution/ appears to be the only location for the
PILwoTK egg. Is there another place where one can get that?
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net
then?
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
of an EXTERNALS.txt file was
that it could be inspected in the web view of a directory, which isn't
true for the svn:externals property itself.
If only svn.zope.org had a trac-based browser, which does show those
properties properly...
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple
it provides.
I don't. EXTERNALS.txt is only useful if your tools suck. There are
perfectly capable svn commit mailers and web browsers that show
property changes correctly.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net
greatly without ZCML
configuration, but getting ZCML-reqired dependencies should be easy.
+1
Those zcml dependencies make it a lot more painful to use zope.*
packages in other environments.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net
it make things more secure?
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman
for the second hash is a lot smaller and very
predictable (you know the exact string length and that is only consists
of digits and lowercase letters), making an attack simpler.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net
setup tool.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope
of interest in a Zope 3 big tree release, and
observing that Zope 2 is going down a similar eggification path I see no
reason to keep a big tree for Zope 2 long term.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard
=zope.sqlalchemy-dev
And in the past I have had the trunk setup.py instal_requires include:
'SQLAlchemy=0.5.0beta3dev-r4954', or 'SQLAlchemy=0.4.7dev',
Which also shows that using a setup.cfg to put revision numbers in dev
versions is extremely useful :)
Wichert.
--
Wichert Akkerman wich
zope.configuration. So, we extract the bits of
zope.component into a new package, but we don't extract bits from
zope.security.
+0.1
This introduces inconsistencies that might be confusing.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net
. This can easily be done with ZPT:
Very often you don't need to do that though, and it actively breaks the
ability to do prototyping with your html and css outside of the
application.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net
or LDAP for shared member properties. It has the
advantage of being very widely supported as well as bwing very simple.
CAS appears to be a common SSO system used for Plone sites and should
work as well.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http
. Is that correct?
That would make the end result inconsistent. I seem to remember
camel case being declared 'the zope standard'.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
hostname for the machine that run/ran
new.zope.org.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev maillist - Zope-Dev@zope.org
http
out since August 2007, so it's hardly the first
OpenID auth implementation for Zope..
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev
.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts
Previously Sidnei da Silva wrote:
On Thu, Mar 5, 2009 at 5:20 PM, Wichert Akkerman wich...@wiggy.net wrote:
I would like to see a move away from zope testing frameworks to a more
standard testing infrastructure: setup.py test, possibly combined with
using nose.
Wichert.
Be aware
it to the trunk?
What's the use case for this?
Martin
By nesting groups I can define fiedlsets inside tab inside fieldset
inside tab
+1
Nested fieldsets are very useful when designing forms.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http
imho that version restriction *has* to be in setup.py.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev maillist - Zope-Dev@zope.org
Previously Stephan Richter wrote:
On Sunday 15 March 2009, Wichert Akkerman wrote:
If the package does not work with an older version of zope.publisher
than imho that version restriction *has* to be in setup.py.
And what if I backport the fix?
We have done version specification like
= x.y, and never zope.foo = x.y.z.
What do people think?
-1 still
If I install a package I want to have a guarantee all aspects of that
package work correctly. With this compromise that is not possible.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http
Previously Jacob Holm wrote:
Wichert Akkerman wrote:
Previously Martijn Faassen wrote:
Hey,
Stephan Richter wrote:
[snip]
There is a compromise I am willing to take. If package zope.bar depends
on a
*new feature* or *feature change* in zope.foo 1.3.x, then it should
Previously Martijn Faassen wrote:
Wichert Akkerman wrote:
[snip]
I see no useful different between x.y and x.y.z here. All I want is if
someone installs one of our packages that package will work as expected.
If a package will only work with a certain revisions of a dependent
package
On 3/23/09 12:57 PM, Chris Withers wrote:
Christian Theune wrote:
Wichert.
Be aware of nose issue #102:
http://code.google.com/p/python-nose/issues/detail?id=102
Is there a particular reason to keep using the test_suite convention?
Personally I much prefer nose's habit of automatically
acceptance outside of the Zope community, and imho
effort is better spent on improving the packaging tools.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
Previously Andreas Jung wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23.03.2009 14:26 Uhr, Wichert Akkerman wrote:
This is an important point. As I see it the KGS is a Zope-only thing,
and is just a workaround for the mindless behaviour of setuptools. I do
not see
never been able to understand
what blueprints do from browsing the launchpad docs.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev
-by-package instead of
trying to figure out what the final target working set should look like.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope
a pure
installation tool (a subset of easy_install) as well as higher level
tools such as zc.buildout which have all the logic necessary to find
packages to install and figure out a strategy to get to a target working
set.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things
On 3/30/09 4:04 PM, Jim Fulton wrote:
On Mar 29, 2009, at 4:10 PM, Wichert Akkerman wrote:
...
You can compare this with dpkg and apt on Debian and Ubuntu systems:
dpkg is the lower level install that installs one or more packages. It
only checks if the packages you install break any package
Previously Marius Gedminas wrote:
BTW I've yet to see a firewall that blocks SSH. Am I lucky?
Yes. Blocking ssh is very common in larger companies in me experience.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net
.)
This looks like a poor man's enum. I'ld prefer to have a proper enum
like thing.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev maillist
this, and is preventing people from upgrading
to the 1.5 client, and thus from using checkouts using relative paths.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
the tarballs, serve the resulting directory. I
have not seen a need to run a script.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev maillist
Previously Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
Previously Chris Withers wrote:
Tres Seaver wrote:
KGS the
concept is very easy to implement; you just make available on some URL
a
buildout versions.cfg, or you run your own
Previously Chris Withers wrote:
Wichert Akkerman wrote:
What we do is: collect the tarballs, serve the resulting directory. I
have not seen a need to run a script.
How do you collect the tarballs?
buildout download cache
How do you serve the resulting directory?
standard apache
do not think that is desired here: Zope 2 is just as hip and modern as
Zope 3 and deserves just as much attention.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
to suggest renumbering the next Zope 2
release to Zope 4. That reflects the large refactoring that is being
done to clean up the codebase and fully eggify Zope. There are enough
changes to warrant a new major version bump.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things
Version 11
X Window System, Version 11
X11
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
Previously Martin Aspeli wrote:
Wichert Akkerman wrote:
To stir things up: I would like to suggest renumbering the next Zope 2
release to Zope 4. That reflects the large refactoring that is being
done to clean up the codebase and fully eggify Zope. There are enough
changes to warrant
, along with some pure libraries.
Zope Toolkit, perhaps? (No relationship to Portal Toolkit. :-] )
+1
Cute.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
it is convenient to our goal of having clearer definitions about
what we're working with.
We can effectively not maintain it anymore and stop making release.
Which would not be a major change from Zope 3 releases the last few
years :)
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make
in setup.py. This breaks on systems
which do not have setuptools installed globally but rely on a
(zc.buildout-created) wrapper script. __file__ will point
to the wrapper script in those instances, which breaks setup.py.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple
Previously Benji York wrote:
On Wed, Apr 22, 2009 at 10:06 AM, Wichert Akkerman wich...@wiggy.net wrote:
I want to suggest two changes to the standard release process:
1. use sdist --formats=zip. This works around a nasty bug in the
python 2.4 tarfile module which makes it skip files
On 4/22/09 4:57 PM, Jim Fulton wrote:
Perhaps you could provide (or point to) an example that illustrates
this problem.
I want to keep my python install clean, so I do not have setuptools
installed system-wide. Instead I have a small bin-directory managed by
buildout which creates a python
Previously Benji York wrote:
On Wed, Apr 22, 2009 at 10:55 AM, Wichert Akkerman wich...@wiggy.net wrote:
Previously Benji York wrote:
On Wed, Apr 22, 2009 at 10:06 AM, Wichert Akkerman wich...@wiggy.net
wrote:
I want to suggest two changes to the standard release process:
1. use
Previously Martijn Faassen wrote:
Wichert Akkerman wrote:
2. forbid the use of __file__ in setup.py. This breaks on systems
which do not have setuptools installed globally but rely on a
(zc.buildout-created) wrapper script. __file__ will point
to the wrapper script in those
/*checkout*/Zope/tags/2.12.0a4/versions.cfg
This works just as well:
http://svn.zope.org/repos/main/Zope/tags/2.12.0a4/versions.cfg
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
track so we make sure we don't
forget about it? (if it wasn't already fixed?)
There is now: https://bugs.launchpad.net/zc.buildout/+bug/368447
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things
of the things people
want to do with Plone would not be possible.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev maillist - Zope-Dev@zope.org
runs on Zope 2.10
while we want to be able to use ZTK components in order to be productive
and have a modern environment. Just like Hanno almost all my Plone
projects over the last year have had to do this.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http
. setuptools changes its
behaviour based looking at internal datastructures for a specific source
control system. You can't blame that on svn.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
Previously Lennart Regebro wrote:
On Tue, May 5, 2009 at 13:27, Wichert Akkerman wich...@wiggy.net wrote:
But you can use a lot of the Zope Toolkit with Zope 2.10, which is an
enormous benefit. If that was not possible a lot of the things people
want to do with Plone would not be possible
.
Can you document for the post-traversal-pre-publication event if that
happens before or after validation?
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
or something like that.
It could be an extra ;)
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev maillist - Zope-Dev@zope.org
http
are handled right now, so no reason to
change a working system.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev maillist - Zope-Dev
it was grandfathered in.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
don't see short as a very important quality here. It is not a name you
have to type in often, so I would prefer something more descriptive. How
about componentroot or componentcontainer..
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net
Previously Martijn Faassen wrote:
Wichert Akkerman wrote:
Previously Martijn Faassen wrote:
I propose we use the word 'Locus' instead of 'Site'. This word doesn't
have a lot of connotations in the web programming world, and people can
guess by simply looking at the word it might have
solution for this, even
if there is just a single application installed.
That sounds like a complicated workaround for not having a mutable
global configuration.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard
.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
Previously Chris McDonough wrote:
On 6/4/09 11:59 AM, Martijn Faassen wrote:
Wichert Akkerman wrote:
Previously Martijn Faassen wrote:
* often it is nice to have application configuration to have a user
interface, so that end users can configure aspects of the application.
This may
it's so important with svn to
note in the commit message, which revisions from which branch you merged.
Otherwise you would not know at all what has been merged.
Subversion 1.5 and later do store that data in a svn:mergeinfo property.
Wichert.
--
Wichert Akkerman wich...@wiggy.net
On 6/19/09 2:25 PM, Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
This is a last reminder for those current contributors to the Zope
software repositories on svn.zope.org who have not sent in the new
contributor agreement as outlined below. Please do so before
On 6/30/09 7:03 PM, Stephan Richter wrote:
It is needed for the latest-versions script as this parses XML. I consider
lxml pretty much the standard tool to do XML in Python these days. Who is not
using lxml?
I suspect the majority of people who use OSX as their main platform try
to stay as
On 7/23/09 12:10 PM, yuppie wrote:
Hi!
SOFTWARE_HOME no longer exist in Zope 2.12, all the software is now
somewhere on sys.path.
So this no longer works in zopectl:
ZDCTL=$SOFTWARE_HOME/Zope2/Startup/zopectl.py
exec $PYTHON $ZDCTL -C $CONFIG_FILE $@
Therefore mkzopeinstance now
On 8/6/09 11:35 , Fabio Tranchitella wrote:
I propose a (very) simple policy, which we can use to improve the current
situation:
* a package is part of the ZTK if the following criteria are met:
- It has at least N zope developers (with commit rights) who
explicitly expressed
On 8/6/09 17:44 , Fred Drake wrote:
2009/8/6 Fabio Tranchitellakob...@kobold.it:
Am I correct saying that your idea is to restrict the ZTK to the packages
defined as the intersection of the dependencies of zope2, zope3 and grok?
ZTK = intersection ( zope2-dependencies , zope3-dependencies,
there have
been no complaints by anyone. And as Robert noted you can use a
Subversion 1.4 client with a 1.5 server just fine.
I think doing the server upgrade very soon (tm) shouldn't be a problem.
Relative externals are handled on the svn client, not the svn server.
Wichert.
--
Wichert Akkerman
On 9/10/09 11:40 , Chris Withers wrote:
Hi All,
I'm doing some development of zc.buildout, and I'm down to a couple of
test failures. The test suite takes quite a long time to run.
Using zc.recipe.testrunner, how can I limt the run to just one file?
eg:
File
The latest zc.recipe.cmmi release started using the zc.buildout download
API but does not depend on zc.buildout 1.4 or later, which broke several
buildouts for me. I've fixed the dependency in r103703. Can someone make
a new release?
Wichert.
___
z3c.form uses zope.schema.interfaces.IDecimal, which is not present in
early versions of zope.schema as used by Zope 2.10. As far as I can tell
z3c.form must have a versioned dependency on zope.schema = 3.3.0.
Regards,
Wichert.
___
Zope-Dev maillist
on PyPI instead of the newest,
Doesn't it break all versioned dependencies on that package?
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev
for A to do some work on it things break with
this policy because it will have version 0 and can no longer satisfy the
= 2.1 requirement.
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
On 9/15/09 10:33 , Reinout van Rees wrote:
On 2009-09-11, Sebastien Douchesdou...@gmail.com wrote:
Caution with the actual workflow, 2 differences between SVN and Hg :
- you cannot check out partial repository
- external does not exist
Missing externals has been a pain point for me.
On 9/15/09 13:56 , Gary Poster wrote:
On Sep 15, 2009, at 4:56 AM, Wichert Akkerman wrote:
In my experience distributed SCMs add bottlenecks to development that we
currently do not have in the Zope community: with both our shared svn
repository and distributed SCMs everyone can branch
anything other than port 80 or https over something
other than port 443.
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev maillist - Zope
documentation. We should actively
work to create such narrative documentation.
How do you define narrative documentation? Do you consider z3c.form to
have narrative documentation for example?
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net
in those databases. The hash is not a unicode string
but a bytestring.
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-Dev maillist - Zope-Dev
')
That generates something entirely differently than standard SSHA1
implementations, which will break interop.
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
On 10/12/09 01:22 , Fabio Tranchitella wrote:
Hello,
* 2009-10-09 15:37, Martijn Faassen wrote:
I'm okay with *not* doing the split up and going with your idea, but I
think eventually such a split up would simplify things. One advantage
would be that someone could examine repoze.zcml and not
On 10/25/09 15:08 , Adam GROSZER wrote:
Hello,
Custom schema properties proposal
=
The problem
is that we have a baseline project. This baseline project gets
customized for each client. Each client has different (usually just a
little bit)
On 11/5/09 14:18 , Jonathan Ballet wrote:
Hi Adam,
On Wed, Nov 4, 2009 at 7:11 PM, Adam GROSZERagros...@gmail.com wrote:
Hello Jonathan,
bin/buildout -N does not fit you?
In fact, we have very strong constraints where our buildout's results
are ran : most of our customers deploy this
'. It
uses the ZCA (and zope.i18n currently), but that's about it. The ZTK as
it currently is implies a whole lot of Zopisms that BFG does not
subscribe to.
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net/ It is hard to make things
On 2009-11-24 17:26, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
On 2009-11-24 05:57, Martin Aspeli wrote:
I whole-heartedly agree, and I think it's important that we use the
momentum behind BFG (and other consumers of the ZTK) to drive the ZTK
yesterday.
That's not a fix, it just replaced one problem with another one: it is
now impossible to get your full list of packages.
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
On 11/30/09 13:43 , Hanno Schlichting wrote:
On Mon, Nov 30, 2009 at 1:21 PM, Martin Aspelioptilude+li...@gmail.com
wrote:
Martijn Faassen wrote:
This implies we don't want to release zope.component 4.0 for a long time
yet.
I think the answer should be never. :)
I think never is a
On 11/30/09 14:45 , Hanno Schlichting wrote:
On Mon, Nov 30, 2009 at 2:39 PM, Wichert Akkermanwich...@wiggy.net wrote:
We could also say that we will clean up the API when we move to Python
3. That is a natural breaking point anyway, so it will not any extra
pain for users of the ZCA.
101 - 200 of 343 matches
Mail list logo
