I'll take that as STFU ;-)
Got it.
- C
Marius Gedminas wrote:
On Fri, Feb 01, 2008 at 11:06:48AM -0500, Chris McDonough wrote:
I typed four more paragraphs full of markety stuff here but deleted them.
*cheers*
Marius Ged
Stephan Richter wrote:
On Friday 01 February 2008, Chris McDonough wrote:
If there will continue to be a release schedule for "Zope 3, the appserver"
It would reduce confusion to new users greatly to give the appserver
release a name other than Zope.
Well, we had to do the clas
Tom Hoffman wrote:
On Fri, Feb 1, 2008 at 9:22 AM, Chris McDonough <[EMAIL PROTECTED]> wrote:
I'll take a risk by stating the obvious.
If there will continue to be a release schedule for "Zope 3, the appserver" It
would reduce confusion to new users greatly to give th
I'll take a risk by stating the obvious.
If there will continue to be a release schedule for "Zope 3, the appserver" It
would reduce confusion to new users greatly to give the appserver release a name
other than Zope.
Eg.
Current name Proposed name
On Nov 19, 2007, at 1:26 PM, Dieter Maurer wrote:
Chris McDonough wrote at 2007-11-18 16:50 -0500:
...
Note that if the KGS really wants to be a KGS (literally "known
good",
it's a matter of semantics, not of technology):
- An invariant must be met that only one version
On Nov 19, 2007, at 2:17 AM, Stephan Richter wrote:
On Sunday 18 November 2007, Chris McDonough wrote:
I disagree. This is not what this means to me. I think a KGS can
receive bug
fix releases, which the Zope 3.4 KGS does. However, no new feature
releases
are allowed.
In the Linux world
On Nov 18, 2007, at 7:52 PM, Stephan Richter wrote:
On Sunday 18 November 2007, Chris McDonough wrote:
4. A new "minimal/" folder now contains an index just of the
controlled
packages. This minimal index can be used by compoze as one
contributing
index. (I have not tested this yet,
On Nov 17, 2007, at 10:00 PM, Stephan Richter wrote:
Hi everyone,
I just updated the Zope 3.4 KGS with some new features.
1. You only need to upload the "controlled-packages.cfg" file now;
all other
files are generated.
2. The "controlled-packages.cfg" file now supports a name and
versio
Thank you much Phillip!
On Sep 15, 2007, at 7:04 PM, Philipp von Weitershausen wrote:
Chris McDonough wrote:
I'm having a bit of trouble debugging a failed browser view
lookup. It has something to do with environment, because lookups
for the view work in one of my sandboxes, and fa
I'm having a bit of trouble debugging a failed browser view lookup.
It has something to do with environment, because lookups for the view
work in one of my sandboxes, and fail in another, even though both
seemingly has the same ZCML and code.
Does anyone have any scripts already written th
Why not just use a mutex (a recursive lock makes things easier too)?
lock = threading.RLock()
lock.acquire()
try:
...
finally:
lock.release()
On Sep 26, 2006, at 9:19 AM, Philipp von Weitershausen wrote:
Jim Washington wrote:
Hi
I need to produce PDFs with reportlab.
reportlab is not th
's time to stop thinging about this. :(
Simon
On 9/14/06, Chris McDonough <[EMAIL PROTECTED]> wrote: The right
thing to do here is probably to just use something like
http://modntlm.sourceforge.net/ and trust the REMOTE_USER environment
variable passed by Apache... let somebody else
The right thing to do here is probably to just use something like
http://modntlm.sourceforge.net/ and trust the REMOTE_USER environment
variable passed by Apache... let somebody else worry about
maintaining it. ;-) One strategy for doing this is described at
http://plone.org/documentation/
I use the Zope 2 generations machinery to manage SQL DDL for
Postgres. It works pretty good.
- C
On Jul 19, 2006, at 2:48 PM, David Pratt wrote:
I am interested in hearing from anyone who may be using generations
in conjunction with relational database storages in zope3 as a
means of mai
Just curious: instead of writing a query language implementation, why
not use a relational database to store the data that is likely to
need to be queried in an arbitrary way? You do still get most of the
good stuff in Zope if you do this and it's a lot less work.
On Apr 23, 2006, at 3:25
In z3, apparently you just return a file from your code and the
publisher knows enough to send it efficiently.
- C
On Apr 20, 2006, at 8:15 AM, David Pratt wrote:
Hi Chris. This is great! I'll check this out. It would be great
however if I could get a clearer picture of large file handling
On Apr 20, 2006, at 3:54 AM, Philipp von Weitershausen wrote:
Chris McDonough wrote:
Actually, "stream iterator" support is independent of blobs.
Right. Also, dealing with long-living requests or dribbling data piece
by piece is substantially something different than streaming la
On Apr 20, 2006, at 3:33 AM, Martin Aspeli wrote:
On Thu, 20 Apr 2006 04:35:47 +0100, Chris McDonough
<[EMAIL PROTECTED]> wrote:
The zodb code is on the blob-merge-branch of ZODB in Zope's
subversion repository. I'm not sure when it's going to land in an
actu
On Apr 19, 2006, at 10:28 PM, David Pratt wrote:
Hi Chris. This is great. I was going to ask Philipp about streaming
but thought once I had contacted you I would ask you since this is
an important part of large file handling. Can you tell me how far
along the ZODB blob support has advanced
his is not the case? Many thanks.
Christian Theune and Chris McDonough have been working on ZODB blob
support for a while. The ZODB as our persistence layer is the right
level to add blob support, not Zope 3. Once in the ZODB, blobs can be
used across both Zope versions.
Perhaps you might want to
Yes, more or less. But it depends what you want to do. There are a
bunch of storages for ZODB, some maintained better than others.
Whenever a question like this comes up, it usually turns out that
people want to use a relational database with a single well-defined
rectangular schema to s
On Mar 2, 2006, at 6:41 AM, Peter Bengtsson wrote:
I'm with Max on this one.
What's the point? To save a few megabytes of harddisk space?
If you don't want the zope.bobo part of your zope3, ignore it. You
don't have to use it if you don't want to.
...
Let's keep it simple, bundle it all in one
I think packaging efforts are really the key to being able to tell a
story like this. The efforts happen to be couched in a process of
converting z3 packages into eggs, but really the process of
identifying dependencies and eliminating the silly ones is the
valuable work here, and it seems
On Feb 23, 2006, at 4:51 PM, Stephan Richter wrote:
So, I take it that you are a second voter in favor of not requiring
all tests
to be doctests.
If the ZSCP thing takes off, I think test/doc req'ts should be
somewhat looser than mandating a particular test/doc framework
(something along
On Feb 23, 2006, at 1:57 PM, Benji York wrote:
> But it's of course a judgment call.
Perhaps this is just one of those to-each-his-own things.
My own are doctests. ;)
Sure. I actually really appreciate reading good doctests, they help
a lot, and they beat not having any docs at all any
On Feb 23, 2006, at 1:17 PM, Benji York wrote:
Chris McDonough wrote:
I dunno about sucking because they are quite good for
documentation, but I tend to write plain-old unittests instead of
doctests when I'm testing without any pretense towards writing
documentation. If you
I dunno about sucking because they are quite good for documentation,
but I tend to write plain-old unittests instead of doctests when I'm
testing without any pretense towards writing documentation. If you
test internals of a class in a doctest, the doctest body gets pretty
cluttered, which
I hate to cross-post this, but would it be possible to limit this
discussion to a single list (e.g. zope3-dev, maybe)? I'm interested
in this topic, but my mail client isn't smart enough to filter it out
to only one place and I'm sure there are a lot of other people with
the same issue.
Kudos for releasing these packages -- they all look interesting and
potentially useful.
Agreed, bravo!!
- C
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users
It will probably not comfort you that the concept of a "view" (at
least by that name) is going to disappear sometime post-3.2.
I hope I explain this properly; here goes.
A view is a registration for a "named multiadapter". The thing that
is registered ("the view") adapts two objects that im
On Dec 22, 2005, at 12:05 PM, Shane Hathaway wrote:
Time and again people fail to realize that Zope 3 wants to create
the low level framework right first, and only after that add high
level simplifications and shortcuts to have less configuration and
provide fastest developer exeperience.
O
Is this code available anywhere or are you still at a state where
you're not ready to release?
On Dec 22, 2005, at 11:01 AM, Shane Hathaway wrote:
Chris McDonough wrote:
I assume this means you've given up on the idea of creating a GUI
ZCML configuration tool, the?
No. In
I assume this means you've given up on the idea of creating a GUI
ZCML configuration tool, the?
On Dec 22, 2005, at 10:44 AM, Shane Hathaway wrote:
Wade Leftwich wrote:
If ZCML (a/k/a The Right Way) is keeping fairly smart developers from
trying Z3, then maybe we need an alternative (a/k/a W
On Nov 30, 2005, at 3:05 PM, Duncan McGreggor wrote:
On Nov 30, 2005, at 12:49 PM, Chris McDonough wrote:
As we move towards another iteration, if I need to, while I'm
writing code, I write evolution scripts that are capable of fixing
ZODB data in place between milestone revisio
On Nov 30, 2005, at 12:38 PM, Brad Allen wrote:
At 1:17 AM -0500 11/30/05, Chris McDonough wrote:
While you're developing, it's much easier because the *content* in
your ZODB doesn't typically have any value during development. If
it does have value during developm
So this style of Zope 3 development involves not using
ZODB so much for permanent storage, but instead as a
temporary scaffolding on which to hang the current version
of class instances and their content. When you refactor
your classes and interfaces, you just re-instantiate everything
into the ZO
On Nov 29, 2005, at 10:29 PM, Duncan McGreggor wrote:
Additionally, the ability to generate a new instance of a project
complete with a fresh-and-ready ZODB is of immense value when
working on a project with multiple developers or teams of
developers. Several times, we have saved literally d
On Nov 29, 2005, at 10:07 PM, Brad Allen wrote:
Chris McDonough wrote:
Here is another question. Suppose I'm working with a team of
developers. Should we each set up our own separate Zope3
instance, and do SVN checkouts into our own separate, local /lib/
python directories insid
Hi Brad,
On Nov 29, 2005, at 5:45 PM, Brad Allen wrote:
Here is another question. Suppose I'm working with a team of
developers. Should we each set up our own separate Zope3 instance,
and do SVN checkouts into our own separate, local /lib/python
directories inside the instance? How then wou
I don't know much about HPUX, but one issue that seems to plague a
lot of less-frequently-used platforms is stack sizes. For example,
for a while in FreeBSD and on MacOS, you needed to explicitly bump up
the thread stack size. See doc/PLATFORMS/BSD.txt in the Zope release
for an idea abou
I dont know of any reviews but I give a personal +1 on this book
(especially for people coming from a Zope 2 development background).
- C
On Tue, 2005-06-21 at 20:11 -0700, Corey wrote:
> Anyone know of any reviews written for this book? ( aside from the short ones
> at amazon? )
>
> I'm sure i
41 matches
Mail list logo
