Wichert Akkerman wrote:
The only problem is that distributing grok-0.11.cfg is a bit tedious.
How about if buildout could get it from the web?
How about making it available from an egg, through a hook in egg-info
perhaps?
This is a very good point. So good in fact that I thought of it myself
Martin Aspeli wrote:
- It only works through buildout. Ideally it would be supported at the
setuptools level, imho.
I'm not really convinced that that's necessary. From a practical
perspective, zc.buildout is the defacto deployment tool in the Zope
community. Also, working sets have "deploym
Martin Aspeli wrote:
- It only works through buildout. Ideally it would be supported at
the setuptools level, imho.
I'm not really convinced that that's necessary. From a practical
perspective, zc.buildout is the defacto deployment tool in the Zope
community.
Alas, not so for all Plone peo
Dieter Maurer wrote:
Therefore, it might be helpful, if the known working set would not
need to be a singleton (consists of just one element).
Assume the following use case:
I use grok to build one of my applications.
I need a another component as well which conflicts with grok.
I overrid
On 4 Sep 2007, at 01:21 , Tres Seaver wrote:
Philipp von Weitershausen wrote:
Wichert Akkerman wrote:
The only problem is that distributing grok-0.11.cfg is a bit
tedious.
How about if buildout could get it from the web?
How about making it available from an egg, through a hook in egg-
info
On 4 Sep 2007, at 10:15 , Chris Withers wrote:
Philipp von Weitershausen wrote:
As far as I understand your use case, i twould already be covered
by my original proposal: you always have the option to locally
override what's specified in the working set.
I think Dieter may have
On 4 Sep 2007, at 20:07 , Tres Seaver wrote:
Dieter Maurer wrote:
Wichert Akkerman wrote at 2007-9-4 09:12 +0200:
...
Linux distros take an approach that does not fit in the python world
though: their meta-set is a release with its own package
database. In
other words every distribution/meta-
On 4 Sep 2007, at 16:13 , Jim Fulton wrote:
How would the "known_working_versions" be used? You haven't
specified that.
You're right, I forgot that. In buildout.cfg, you'd then say:
[buildout]
versions = egg:grok==0.11
which would load the grok 0.11 egg before doing anything else,
ins
On 4 Sep 2007, at 19:15 , Dieter Maurer wrote:
Chris Withers wrote at 2007-9-4 09:15 +0100:
Philipp von Weitershausen wrote:
As far as I understand your use case, i twould already be covered
by my
original proposal: you always have the option to locally override
what's
specified i
Tres Seaver wrote:
Benji York wrote:
Jim Fulton wrote:
I like distribution as a place to put packages that aren't ready for
PyPI. Unfortunately, we've put a lot of packages in PyPI that aren't
ready IMO.
I suggest we put them in PyPI earlier and use "Development Status :: 2 -
Pre-Alpha". O
Martijn Faassen wrote:
Martin Aspeli wrote:
Paul Winkler wrote:
On Sun, Sep 09, 2007 at 05:39:45PM +0100, Martin Aspeli wrote:
Has there been a strong statement that there won't be a Python 2.7
and beyond? Will Python 2.x be actively killed off?
Quite the opposite, Guido proposed last year t
Benji York wrote:
zope.testrowser 3.4.1 generates non-backward-compatible tracebacks for
HTTP errors. 3.4.2 will be released soon(-ish) to fix this, in the mean
time please continue to use 3.4.0. Thanks.
I guess I'm to blame here since I released 3.4.1. In my defence, it
seems that the new
Christian Theune wrote:
Let me propose a change:
1. We revert the change.
Any news on this?
--
http://worldcookery.com -- Professional Zope documentation and training
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman
Benji York wrote:
I have a small issue with zope.testbrowser packaging I'd like to get
some input on. If I were to have started the project today, it would
likely have been zc.testbrowser, which would have no Zope 3 dependencies
(or functionality) and zc.testbrowser.zope, which would have, and
zopeproject makes it easy to get started with a web application based on
Zope eggs, zc.buildout and WSGI/Paste. If you're not familiar with this
world yet, zopeproject is your easy entry to it. If you are, zopeproject
will save you lots of typing up the boilerplate.
Why eggs?
-
Because t
On 16 Sep 2007, at 21:36 , Lorenzo Gil Sanchez wrote:
thanks a lot for adding a debug script to the bin directory. It's
one of
the few things I missed from this great package!
I may suggest you could add the changes of the 0.4 version to this
announce email. Just a minor issue :-)
Since I wa
Jodok Batlogg wrote:
the current practice (at least here at lovely systems, and presumably a
lot of other developers) is to add download.zope.org/distribution (or a
mirror of it) to your find-links.
recently some people started registering packages (and uploading eggs )
to cheeseshop. this make
Tres Seaver wrote:
Stefan H. Holek wrote:
On 19. Sep 2007, at 00:46, Jodok Batlogg wrote:
i'm wondering why i couldn't fine zope.app.wsgi =
3.4.0b1dev_r75415 after 3.4.0 was released a few days ago.
probably someone in [philikon, ctheune, J1m, baijum] removed the egg?
we nailed the version
Short follow-up:
The first zopeproject-0.4-py2.4.egg that I released to PyPI was faulty.
I forgot to clean stuff from older builds, so it contained traces of
older versions of zopeproject. zopeproject's functionality isn't
affected in any way, it just generates some old, no longer applicable
Roger Ineichen wrote:
Please review this proposal. I'll implement it
shortly if nobody has objections. We need it for
our work here at the Foliage sprint.
If you have objections, please tell me what
you think is not well done and tell me your
ideas to solve the problem in another way.
http://w
Roger Ineichen wrote:
This proposal describes a way to make the usage of such
built in views optional.
"Such built in views" means what? "Optional" how? And why?
I mean with built in views just views which comes within a
package. Such view component are located in the browser folder
and bui
(Also CCing zope3-dev where the first known working set discussion
started a while ago)
Tres Seaver wrote:
This is the "known good" problem. I'm pretty convinced that adding some
kind of "PyPI subset", where gardeners for a given "package set" keep
the list of packages / versions known to work
On 25 Sep 2007, at 18:41 , Brian Sutherland wrote:
On Mon, Sep 24, 2007 at 01:13:00AM +0200, Roger Ineichen wrote:
I think we will split packages in its base parts.
For exapmle this means we will create a package zope.session
that contains the python api and degrade zope.app.session
to contain t
Stephan Richter wrote:
On Wednesday 26 September 2007 04:49, Christian Theune wrote:
The issue is that the eggs were released as ZIP files and for some
reason those don't work correctly with the data files.
I can reproduce the problem by creating the packages myself as ZIP files
(doesn't work)
Stephan Richter wrote:
On Wednesday 26 September 2007 09:36, Martijn Faassen wrote:
I think tagging things in svn is a minimal requirement, though. I
understood that some of this stuff wasn't tagged?
I agree. And Roger simply forgot. As Marius pointed out, as we do more
releases, problems lik
Jim Fulton wrote:
I'm not too keen on trying to automate this with a Python script. I
suggest we start with a human script.
I agree.
I think Philipp has a start at this. Philipp, could you remind
us where this is?
http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/maintaining-soft
Stephan Richter wrote:
On Wednesday 26 September 2007 05:02, Christian Theune wrote:
Hmm. While doing that I also noticed that we were at 3.4.0a1 yesterday
evening. The stable release was made from that without making a
maintenance branch and bumping the trunk to 3.5.
There is conflicting info
Martijn Faassen wrote:
And where is an agreed-upon document that you have to list the next
version in the setup.py file after the release? Because I disagree
with that, since you cannot know the next version.
I disagree with too, for the same reason.
I'm not saying you should foresee the fut
On 26 Sep 2007, at 16:49 , Martijn Faassen wrote:
On 9/26/07, Philipp von Weitershausen <[EMAIL PROTECTED]>
wrote:
Martijn Faassen wrote:
[snip]
What about using CHANGES.txt, which we should be maintaining anyway?
[snip]
These are very good points. My guide [1] already recommend
Jim Fulton wrote:
On Sep 26, 2007, at 1:18 PM, Fred Drake wrote:
On 9/26/07, Martijn Faassen <[EMAIL PROTECTED]> wrote:
What does one need to tell setup.py to make sure CHANGES.txt is
available? I understand it isn't by default, then? Hm, it does appear to
be there by default. I checked grok 0
On 26 Sep 2007, at 23:18 , Jim Fulton wrote:
On Sep 26, 2007, at 4:34 PM, Benji York wrote:
Philipp von Weitershausen wrote:
Stephan Richter wrote:
Because I disagree with that, since you cannot know the next
version.
You can always know the minimum version. If you just released
3.4.2, I
On 26 Sep 2007, at 22:34 , Benji York wrote:
Philipp von Weitershausen wrote:
Stephan Richter wrote:
Because I disagree with that, since you cannot know the next
version.
You can always know the minimum version. If you just released
3.4.2, I think it's sensible to point the next re
On 26 Sep 2007, at 23:41 , Stephan Richter wrote:
On Wednesday 26 September 2007 17:34, Jim Fulton wrote:
On Sep 26, 2007, at 5:28 PM, Stephan Richter wrote:
On Wednesday 26 September 2007 17:18, Jim Fulton wrote:
- Update changes.txt, adding a heading for the new # and date
- Create a tag
-
Marius Gedminas wrote:
Log message for revision 80145:
Make the test pass on both Python 2.4 and 2.5.
...
-=-
Modified: z3c.form/trunk/src/z3c/form/action.txt
===
--- z3c.form/trunk/src/z3c/form/action.txt 2007-09-26 21:2
On 27 Sep 2007, at 00:14 , Jim Fulton wrote:
Let's say X depends on Y and I'm developing them simultaneously as
development eggs in one sandbox (e.g. buildout). I add a feature
to Y that I'd like to use in X. That means I'll have to change X's
version dependency regarding Y so that it now de
On 27 Sep 2007, at 02:29 , Tres Seaver wrote:
Further, anybody who finds the effort of creating a "fresh' checkout
bevore making a release too burdensome should consider themselves
self-selected out of the "release manager" pool.
I'm *not* kidding about that: taking shortcuts durng the release
On 27 Sep 2007, at 04:52 , Stephan Richter wrote:
On Wednesday 26 September 2007 20:35, Tres Seaver wrote:
So I usually create the release first and upload it and after
that create
the tag.
-100. Get it right, check it in, *then* upload the distribution.
We do not have the tools. There is
On 27 Sep 2007, at 13:07 , Martijn Faassen wrote:
On 9/27/07, Tres Seaver <[EMAIL PROTECTED]> wrote:
[snip]
Further, anybody who finds the effort of creating a "fresh' checkout
bevore making a release too burdensome should consider themselves
self-selected out of the "release manager" pool.
I'm
On 27 Sep 2007, at 12:20 , Stephan Richter wrote:
egg_info does not validate the trove classifiers, for example. I
tried this
last night before writing this mail.
Well, to be honest, I wonder how you can mess up with the
classifiers. I just always copy them from http://pypi.python.org/pypi?
On 27 Sep 2007, at 13:47 , Stephan Richter wrote:
On Thursday 27 September 2007 07:18, Philipp von Weitershausen wrote:
These are four separate cases where I've actually witnessed myself or
other people mess up. We're forgetful, we can't do anything about
that. We can, howev
Benji York wrote:
Testbrowser Real
zc.testbrowser.real lets you use the testbrowser API to drive
a real web browser; at the moment Firefox (but we may add support for
others in the future). This lets you do testing of JavaScript heavy
web applications with testbrowser (and doct
Christian Theune wrote:
Zagy and I are trying to make z3c.form compatible with sources.
Shrug... Why wouldn't it be compatible already? Shouldn't the widget
abstract everything away?
We had to investigate zope.schema for that and found the mess of vocabularies
and sources that is still arou
Martijn Faassen wrote:
A release of zope.dottedname was made apparently today that refers to a
CHANGES.txt but doesn't have one. Probable scenario: someone forgot to
svn add a CHANGES.txt, then didn't check out before the tag before
releasing...
Right. This is actually a *common* mistake. Not
Roger Ineichen wrote:
On 02.10.2007, at 14:25, Jim Fulton wrote:
On Oct 2, 2007, at 5:25 AM, Martijn Faassen wrote:
Hi there,
Besides causing us a lot of problems here at the Grok
sprint, I also
wonder why in the world are we doing major packaging
reorganizations
and releasing them as mi
Jim Fulton wrote:
On Oct 2, 2007, at 3:29 AM, Martijn Faassen wrote:
Jim Fulton wrote:
[snip]
Maybe grok was already trimmed down. In my case, I basically
eliminated all ZMI support (since I didn't need it). I got about 40%,
Grok is trimmed down in the sense that it doesn't depend on all
Baiju M wrote:
Should we create separate message factory in 'zope' domain for
each packages ? If so, can anyone explain why it should be like that.
No. I think each package that has translations should actually use its
*own* domain and ship with the translations. In an eggified world it
doesn
Jim Fulton wrote:
I'd really like to get to closure on the current approved release
process. Philipp, would you mind separating the release process into a
separate file? Or do you mind if I do it?
Done:
http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/releasing-software.txt
WRT
On 4 Oct 2007, at 00:59 , Jim Fulton wrote:
On Oct 3, 2007, at 3:44 PM, Philipp von Weitershausen wrote:
Jim Fulton wrote:
I'd really like to get to closure on the current approved release
process. Philipp, would you mind separating the release process
into a separate file? Or do you
Jim Fulton wrote:
This would basically involve retiring the zope3-dev list and moving
zope3 developers to the zope-dev list.
+100
--
http://worldcookery.com -- Professional Zope documentation and training
___
Zope3-dev mailing list
Zope3-dev@zope.or
Stephan Richter wrote:
On Thursday 04 October 2007 09:57, Jim Fulton wrote:
This would basically involve retiring the zope3-dev list and moving
zope3 developers to the zope-dev list.
-1. I do not follow zope-dev at all and the traffic is pretty high there.
If you "do not follow it at all",
Martin Aspeli wrote:
Stephan Richter wrote:
On Thursday 04 October 2007 09:57, Jim Fulton wrote:
This would basically involve retiring the zope3-dev list and moving
zope3 developers to the zope-dev list.
-1. I do not follow zope-dev at all and the traffic is pretty high there.
But pretty l
Marius Gedminas wrote:
On Wed, Oct 03, 2007 at 09:44:21PM +0200, Philipp von Weitershausen wrote:
Jim Fulton wrote:
I'd really like to get to closure on the current approved release process.
Philipp, would you mind separating the release process into a separate
file? Or do you mind if
Jim Fulton wrote:
I have no idea about this specific move. If there was a zope.app.error
before, then distributions of it should still exist and new
distributions should be backward compatible.
zope.error 3.5 is needed by:
required by zope.app.applicationcontrol 3.4.1.
required by zop
Stephan Richter wrote:
On Saturday 06 October 2007 13:14, Andreas Jung wrote:
You are using 7 times the term "Zope2" and 9 times "Zope 3"
and also "Plone 3.0" in this small text. Can you try to describe
this without "2 or 3" in "Zope *"? I guess not, right?
s/Zope 2/Zope application server
s/Zo
Martijn Faassen wrote:
Anyway, I think the rule should be:
"When you do a final or bugfix release of a package, you can't start
requiring a new feature release of another package."
+1
Translated to version numbers:
"If X.Y.x has been relying on A.B.x, X.Y.x + 1 cannot start relying
on A.B
Martijn Faassen wrote:
Zope 3 is a bunch of technologies for building (web) applications in the
form of an integrate set of Python libraries.
Let's call those the "Zope Libraries". Because by now we have far more
than just the ones that came from exploding Zope 3 (e.g. all the ones
from the '
Oliver Marx wrote:
Here is what I told my mother:
Zope 3 is a web development technology that focuses on code reuse,
automated testing and security.
- Code reuse: we can do more in less time.
- Automated testing: Code reuse makes it a much have.
- And with automated testing we can actually pro
On 8 Oct 2007, at 13:30 , Oliver Marx wrote:
Yup. Now let's drop the "3" in that sentence, because all of this
applies to Zope software as a whole. This is, in fact, one way to
sum up the way the Zope project as a whole works.
I have no problem with that. The simpler the better. As long as the
On 8 Oct 2007, at 15:14 , David Pratt wrote:
Hi Uwe. I have been thinking of something similar and posted on the
list a couple of weeks back:
http://mail.zope.org/pipermail/zope3-dev/2007-September/023653.html
I want the zcml to be generated with a switch on zc.buildout so all
configuration
On 8 Oct 2007, at 15:52 , Roger Ineichen wrote:
Betreff: Re: [Zope3-dev] Re: The elevator speech for Zope 3
[...]
Soon, we will change Grok so that it emits configuration
actions, rather than doing the registrations right away. That
way, you will still be able to inspect what exactly Grok is
Martijn Faassen wrote:
Does grok support a component architecture where I can use some
components from or is grok a "use it all or nothing
concept"?
Grok *aims* to support reusing bits of it. It hasn't reached this goal
yet as we focused on making it work first, but has been an explicit
seoc
Since it has come up a few times on the checkins list recently, I'd like
to reiterate an important point:
When you split files or packages, you should always use 'svn cp' and not
simply copy the bare files. Because if you simply copy the files from a
checkout to another one, version history is
Dieter Maurer wrote:
David Pratt wrote at 2007-10-8 00:21 -0300:
Zope 2 is one application among many dependent upon zope 3.
Zope 3 is different software than zope 2.
I do not argue with you that Zope3 is "different software than Zope 2".
What I argue about is "Zope 2 is an application".
I ha
Christian Zagrodnick wrote:
I constantly run into the fact that the default namechooser in Zope 3 is
too dumb.
Does anybody object in making it a little more smart? That is:
* replace all non us-ascii and otherwise harmful chars by something
useful (base-form or alike)
Why would you want
Christian Zagrodnick wrote:
Actually you cannot make sources more straightforward as
zc.sourcefactory made it.
I agree. It's very nice.
So, when the contract is ISource, a widget would need to adapt
choice.vocabulary to IIterableSource to get the values. For terms it
should multiadapt (choic
Kapil Thangavelu wrote:
I've been using zope3 as a wsgi app, without a zodb. it bypasses the
zodb publishing traversal via replacement of the published application,
all of which can be managed in zcml.
One issue I've run into is configuring an app through zope.conf forces
you to have an open
Hello all,
I've discovered a problem in the way zope.publisher chooses the
request's locale object (accessible via request.locale).
In an ideal circumstance, the number of languages that a user client
prefers (in order) is retrieved by adapting the request to
IUserPreferredLanguages. The langua
Philipp von Weitershausen wrote:
Hello all,
I've discovered a problem in the way zope.publisher chooses the
request's locale object (accessible via request.locale).
In an ideal circumstance, the number of languages that a user client
prefers (in order) is retrieved by adapting the
Albertas Agejevas wrote:
Hi,
I discovered a problem with Zope 3 while developing ReSTive interfaces
for schoolbell, which utilize the HTTPPublication and the
HTTPRequestFactory.
When the user sends a request for a method that is not supported by
the object, the HTTP spec (RFC 2616) mandates respons
Albertas Agejevas wrote:
On Thu, Apr 07, 2005 at 10:06:38PM +0200, Philipp von Weitershausen wrote:
Albertas Agejevas wrote:
Currently, in the generic case, Zope 3 raises a ComponentLookupError
in zope.app.publication.http line 74, and a 500 response is served.
I can't find that particular li
Martijn Faassen wrote:
Is the Twisted integration based on WSGI? I'd be interested in seeing
Apache mod_python integration using WSGI as well, though I think
mod_python WSGI support is still behind...
I'm planning to evolve modzope to glue Apache and Zope X3.1 together
using WSGI. As far as I kn
Gary Poster wrote:
Wanted to alert folks, if they are interested and also if they want to
check what I've done, that I have checked in code to make Philipp's
i18nmessageid.Message usable in Zope 3 (i.e., it works with i18n
translate, it's a security "brick", it works in page templates, it's
ext
Gary Poster wrote:
Let me know (or fix it yourself :-) if you see any problems. I'm not
sure if this belongs in CHANGES.txt or not; if someone wants it
there, I'll probably see if Philipp is willing to add it...
Well, the whole reimplementation of Messages were added after X3.0
anyway, so I th
Hi everyone,
just letting you guys know that my article for the May issue of the U.K.
LinuxMag is available as a PDF download at:
http://www.linux-magazine.com/issue/54/Zope_X30_Review.pdf
It is a translation of an article published in the German LinuxMag in
January this year.
Philipp
_
Jim Fulton wrote:
I was hoping to stay out of this discussion, but ...
1. There will be many more releases of Zope 2, including
2-digit releases like 2.10, 2.11, etc.
This is good and very much necessary. (Though by the current rate of
release, Zope 2.11 will be released by 2012. ;))
2. The X
Christian Theune wrote:
Hi,
* Stephan Richter <[EMAIL PROTECTED]> [050420 15:59]:
On Wednesday 20 April 2005 09:42, Florent Guillaume wrote:
Gh Why oh why ? The document is now totally unreadable, except
by reading a generated .ps or .pdf. That's not the way to go for
documentation :(
Ok.
Martijn Faassen wrote:
Philipp von Weitershausen wrote:
[snip]
I would like to settle for a consistent naming convention. I'm ok with
keeping the X (under the premasis of an alternate interpretation) and
I also agree with Martijn that "Zope X3 3.1.0" is quite long, but I
can
Philipp von Weitershausen wrote:
Hello all,
I'm proud to announce that a second book on Zope 3, "Web Component
Development with Zope 3", is officially out now. It is the ideal
companion to Stephan Richter's expert "Developer Handbook", serving as a
general in
Dmitry Vasiliev wrote:
Recently Stephan and me have a discussion on the IRC about purpose of
i18n:translate attribute for tags with dynamic content through
tal:content attribute. Stephan pointed out that i18n:translate in this
case is just a marker for call translate() later. But later I discove
Godefroid Chapelle wrote:
Jim, some other people and I argued that this kind of automation is
bad anyway and instead of introducing more translation magic, TAL
shouldn't do any automatic translation at all.
So, in my opinion, do_insertText_tal() should raise a
DeprecationWarning if it encounter
Jim Fulton wrote:
Martijn Faassen wrote:
...
If someone that is not interested in Zope 3 in the first place wrote a
Python library we'd like to include, the relicensing hurdle will be
larger, though. What's to be done with Twisted integration, for instance?
Relying on new external libraries with
Dmitry Vasiliev wrote:
Log message for revision 30249:
Removed all cases of bogus use 'i18n:translate'
I think most of these cases are not at all bogus. See below.
Changed:
U Zope3/trunk/src/zope/app/apidoc/ifacemodule/iface_macros.pt
U Zope3/trunk/src/zope/app/cache/browser/cacheableedit
Stephan Richter wrote:
On Saturday 07 May 2005 14:39, Philipp von Weitershausen wrote:
Removed all cases of bogus use 'i18n:translate'
I think most of these cases are not at all bogus. See below.
I already told Dimitry, which triggered his recent mail. He will fix this,
once the dis
Tres Seaver wrote:
Achim Domma (Procoders) wrote:
can somebody explain me, what would be the recomended way to import
external data into Zope? Let say I have developed a product which stores
his data in the ZODB. How can I fill the DB with data via a script and
not via the Web interface?
$ bin/z
Dmitry Vasiliev wrote:
Philipp von Weitershausen wrote:
Godefroid Chapelle wrote:
Jim, some other people and I argued that this kind of automation is
bad anyway and instead of introducing more translation magic, TAL
shouldn't do any automatic translation at all.
So, in my op
Dmitry Vasiliev wrote:
Stephan Richter wrote:
On Friday 06 May 2005 12:11, Godefroid Chapelle wrote:
Stephan also have pointed that automatic translation doesn't allow
somebody to disable translation on purpose for some piece of content.
Right. That's one reason why it's bad.
Can someone explain
Stephan Richter wrote:
On Friday 06 May 2005 10:11, Dmitry Vasiliev wrote:
Opinions?
Dimitry, I am sorry. There was already a papal's edict on the issue:
http://mail.zope.org/pipermail/zope3-dev/2004-September/012186.html
That means, message ids must be translated explicitely using i18n:translate.
Stephan Richter wrote:
On Sunday 08 May 2005 10:01, Philipp von Weitershausen wrote:
Thoughts?
I don't mind the two semantics. I just think that if tal:content and an
explicit message id in i18n:translate is specified, an error should be
raised. I bet you it does already.
Nope. I ad
Stephan Richter wrote:
On Monday 23 May 2005 21:30, Julien Anguenot wrote:
According to TODO.txt within the doc sub-folder it's written :
"Bugs starting with * represent bugs that must be fixed for the 3.0.x
branch as well ."
Is it still something that needs to be done ?
Yeah, but noone do
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp von Weitershausen wrote:
Stephan Richter wrote:
On Monday 23 May 2005 21:30, Julien Anguenot wrote:
According to TODO.txt within the doc sub-folder it's written :
"Bugs starting with * represent bugs th
Ivo van der Wijk wrote:
Hi,
I'm currently writing a transform utility (somewhat like
portal_transforms in Plone) for my Zope3 project. I think this will be
a usable component to others - would something like this be
interesting to include in the Zope3 core?
The utility converts a mimetype to a
Chris Withers wrote:
Hi All,
Zope 2 has the nice ability to allow you to override Products.
For example, I just found a bug in ZCTextIndex which will need fixing,
so between now and 2.7.7, I can just run with a patched ZCTextIndex
product in my instance home without having to worry about wheth
Stephan Richter wrote:
On Thursday 26 May 2005 12:53, Jim Washington wrote:
I would rather not alter and maintain the foundation-level code in
zope.app.pub*. Would it be possible to do this as a product? Presuming
it is bad form to monkey-patch zope.app.publication.httpfactory, is
there a mor
Five 1.0.1 released!
The Five team is happy to release Five 1.0.1, a bugfix release for
Five 1.0. The most important news is unicode support for add and edit
forms; other minor fixes are included as well. Please consult the
CHANGES_ for more details.
.. _CHANGES: http://co
Roger Ineichen wrote:
See our implementation of nested source directories at:
http://svn.tiks.org/viewcvs/Tiks/trunk/src/tiks/publisher/browser/
This implementation doesn't support a boolean, because perhaps you won't use
all
subfolders of your resource. e.g. use some external javascript
librar
Stephan Richter wrote:
On Sunday 05 June 2005 09:35, Jim Fulton wrote:
- What's the deadline for this?
Well, um, Stephan was hoping to make the beta today. :)
I don't know if we can treat the absense of DAV locking as a bug and
get it in after the beta.
No, that would be a feature. So we
Jim Fulton wrote:
Philipp von Weitershausen wrote:
Stephan Richter wrote:
On Sunday 05 June 2005 09:35, Jim Fulton wrote:
- What's the deadline for this?
Well, um, Stephan was hoping to make the beta today. :)
I don't know if we can treat the absense of DAV locking as a bug
Hi there,
I just came across a couple of places where the IView interface is used,
e.g. IWidget and IAdding. IView was moved from zope.component.interfaces
to zope.component.bbb.interfaces which contains a couple of other
interfaces, such as IViewFactory, which is used throughout the Zope3
so
Dominik Huber wrote:
Florent Guillaume wrote:
Log message for revision 30706:
Revert changes to IIntIdsSet interface.
Could you expand a bit in the checkin message on the motivations behind
your changes?
I discussed with Jim a problem raised by the intid utility during
registration of
Hi there,
it's quite confusing that sequence widgets and items widgets (such as
SelectWidget, DropdownWidget, etc.) cannot be specified in the /> subdirective of the addform and editform directives. I actually
consider it a bug because documentation and implementation are saying
something diff
501 - 600 of 766 matches
Mail list logo
