of a
dedicated DAV server -- probably the right thing to do today would
be to have the DAV server config the publisher to never acquire,
then you dont have unresolvable ambiguities.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
_
+1 from me ;)
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Shane Hathaway
> Sent: Tuesday, June 14, 2005 11:17 AM
> To: An
Hi Andreas - please don't cut the release until we get the
OK from Tim Peters - he's still working on merging recent
ZODB changes, I believe.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
> -Ori
using to run the tests had a wacky default encoding
set - after I fixed that the tests all passed so I commited the
merge.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
I did a merge from the five-integration branch to the head
in a local sandbox, and got the following test failures -
anyone know anything about them?
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
Running unit tests
hiya -
Just a head's up that I going to try to merge the five-integration
branch to the trunk in a bit so Tim can get unblocked on stitching
in the newest ZODB.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zop
ng
> > everyone to drink the kool-aid at once ;)
>
> Yup... I'm still a bit skeptical but if other folks are committed to
> maintenance I'd be less so.
Skepticism is healthy, but if it's any consolation, almost everyone
involved in this effort has very real 'skin in th
e into any particular direction.
I *do* expect these (good) questions to recur in future Z2
releases, as integration and ability to use Z3 technologies
increases, but we'll have plenty of time to work those out.
For now, I think it is a huge win to make some Z3 avenues
available to people who wa
and schedule to that of Zope 3 going
forward. We don't need to decide this immediately to continue
to make progress on 2.8. I suggest an IRC meeting sometime
soon to draft a proposal.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zop
components.
Zope 2.8+ will include the essential Zope 3 packages, so it will
not be necessary to install Zope 3 separately.
If you are interested, there is now a 'five-integration' branch
in Z2 SVN where this work is going on.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 54
an
xml-rpc request.
The change I'm proposing would be to first look for a recognizable
sign of a SOAP request (SOAPAction header). If found (and *only* if
found), we would defer to the SOAP handler. Otherwise, POSTed xml
will continue to be treated as xml-rpc.
Brian Lloyd[EMA
different solutions without
everybody having to buy into a particular approach or implementation
right now.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTE
is as I can,
but its pretty likely someone out there could get this done
faster. If you can get the me the content, I promise I can
get your mods up on the site quickly ;)
To the zope-web folks and others managing zope.org content -
we should also change the 'Zope CVS' (and zop
o I expect we'll see a
marked improvement in the near future.
As to zope.org/About, it is confusing right now because the actual
docs aren't yet posted. Michael is working as we speak to get the
click-wrap alluded to in /About up and running and a place to
organize these
uld prefer to stick by our process ("*no*
> non-packaging changes between the last RC and the release.")
>
> Tres.
I agree. There is *always* "one more bug" that is important to
someone, but for sanity's sake I too want to avoid
a case we want to get away
from). I'm still tracking down what I hope is one final issue
for rc2, but you should be able to update now and your original
tests should pass.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
this before reporting
any lingering issues!**
Thanks,
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/ma
look
at :(
Alternatively, if you can make a copy of the failing script and
boil it down to the minimum possible code that demostrates something
that should be working but isn't (and that excludes app-specific or
Plone objects if possible so that we can turn it into a unit test)
I can try to l
> Brian Lloyd wrote:
> > As the person who unfailingly gets flamed no matter which way the
> > decisions leans :), I think we are probably at a point where we
> > should have an official, documented and community-agreed-to policy
> > on how these kinds of things will be
'The Rules' regarding security
reports, and working to make sure that we are all consistent in following
them.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
Zope-Dev maillist
ngs are figured out at the time the
script is called.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope
If any of the Plone folk who have been running into this issue
can try the changes from cvs, I'd appreciate it.
thx,
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
either a) the users of the scripts have the appropriate
permissions on the container or b) they remove the 'container'
binding from their scripts if it is not appropriate to give
the users access to the script container.
Sorry this was so long, but I think these kinds of ba
Thanks - I've marked these resolved. FYI I have a number of
other issues still to mark resolved - I'll be trying to work
through those today.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
> -Ori
tory of a Zope install on windows.
For 2.7.0 and above, we've moved to using InnoSetup. We haven't
worked out the best way to move that work to the public cvs yet.
If you're planning to bundle 2.7, let me know and I can at least
get you a snapshot of the install materials.
Brian Lloyd
-2_7-branch and head and let me know when its done).
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
> -Original Message-
> From: Martijn Faassen [mailto:[EMAIL PROTECTED] Behalf Of Martijn
> Faassen
>
I forward-ported these to the 2.7 branch & the head. Any testing
you can do to make sure I didn't break anything would be appreciated.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
> -Orig
://www.zope.org/Products/Zope/2.7.0b4/CHANGES.txt
- http://www.zope.org/Products/Zope/2.7.0b4/HISTORY.txt
For more information on the available Zope releases, guidance for selecting
the right distribution and installation instructions, please see:
http://www.zope.org/Documentation/Misc/In
Zope 2.6.3 Release and Security Update
Zope 2.6.3 contains a number of security related fixes for issues
resolved during a comprehensive security audit conducted in Q4
2003. You may download Zope 2.6.3 from Zope.org:
http://www.zope.org/Products/Zope/2.6.3/
**Users of the VerboseSecu
should hold our nose for now and do
it, since it's too late in the 2.7 cycle to contemplate that big a
restructuring.
Making this sane would be a good potential project for an enterprising
zopista for 2.8...
Brian Lloyd[EMAIL PROTECTED]
V.P. Engine
interface file that is used to generate some of the api docs -
ideally that can get updated too.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
Zope-Dev maillist - [EMAIL
selecting
the right distribution and installation instructions, please see:
- http://www.zope.org/Documentation/Misc/InstallingZope.html
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
I'd like to plan to tag Zope 2.7 beta 3 this coming Tuesday and
release it. Please make sure anything you may still be doing on
the Zope-2_7-branch is wrapped up by Monday evening (EST).
Thanks!
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
HUGE PROPS to everybody today! I got caught in some unplanned
things and never got there :(
I *promise* we'll get a beta 3 out in the next two weeks -
hopefully by this Friday now that I know how to drive the
win32 install machinery (thanks Chris!)
Brian Lloyd[EMAIL PROTECTED
rify :-)
Sorry - Tuesday the 4th - a.k.a October 35th ;)
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/lis
fyi, I'm ok with merging this to 2.7 if it already is on the HEAD,
has tests, and has at least some minimal docs.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
> -Original Message-
> From: [EMAI
much appreciated.
thanks!
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross
ve it.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
> Chris McDonough
> Sent: Thursday, October 23, 2003 3:51 PM
>
r code in that cvs should do a
check to make sure, but given that we caught the intrusion
almost immediately and that the attacker's methods were rather
unsophisticated, I think the risk is pretty low.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.17
fore the end of November given that there are
still some loose ends regarding config & installation and the
need for at least one more beta (more likely two).
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
Hi all -
A quick reminder that we'll be having a bug day tomorrow
10/21 to try to knock out some remaining issues in the drive
to get a Zope 2.7 final out.
Hope to see you on #zope-bugday !
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corpor
lease avoid adding new content to the site for this afternoon (EST),
as I may need to take a copy of the db to do these operations in
order to avoid impacting performance on the main site.
thanks,
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corpor
ve been out months ago.
>
> --andy.
We'll try to crank that out today.
And why haven't you raked my leaves yet - sheesh, I
thought that would have been done months ago! :^)
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
ain to everyone who has been involved in making this happen!
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailma
zope.org, you may want to
hold off on new additions until the new site goes live (expected
to be Friday).
I've put a prominent notice on the current zope.org homepage with
the same info.
Thanks, and we'll see you on Friday with a new zope.org!
Brian Lloyd[EMAIL PROTECTED]
V.P. E
Hi all -
We're planning to cut 2.6.2 b4 today, since there have been a
few fixes committed since b3.
I'd like to plan to cut the final next week with no changes
from b4.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://ww
site accessible during the transition will help with
any pain we experience.
I'll send another note when we finalize the dates for the final content
migration and go-live date. I want to keep the window between these down
to a day if possible to minimize disruptions.
Brian Lloyd
issed that still needs
to be
done (for either release), please let me know ASAP.
Thanks!
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
Zope-Dev maillist - [EMAIL PROTE
Tim says that this has been merged into the 2.6 branch (last
week).
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
> Of seb bacon
>
where are we holding bugday today? #zope-dev?
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo
y'rs,
>
> -Casey
Rats - you've foiled my plan. I guess I won't be able to
get away with scheduling the next one for Wed. the 32nd.
In the interest of the integrity of the space-time continuum,
we'll leave Tuesday where it is and do it then. ;)
Brian Lloyd[EM
the end of next week.
Thoughts?
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross pos
FYI - we plan for this to be fixed in 2.6.2, preferably by fixing
the version machinery to require the "join / leave versions"
permission (which is assigned only to managers by default.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://ww
> > How about the next Wed after that (9/4)?
>
> April 9th is ok for me.
>
> Florent
Sounds like April 9th works best for everybody, so lets go
with that.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation h
threw a date out there because someone had to :)
If there is one that would work better for the bulk of the
folks interested, pls do...
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
> It's been some time now since we last had a bug day. Should we have
> another one?
Absolutely. How about Wed the 2nd?
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://w
t;
> Sean
You won't need to set headers manually - things like that will be set
for you by virtue of using the ESI tags in a template.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
> What is the roadmap for ESI integration in zope ?
> (http://www.zope.com/News/PressReleases/OpenSourceESI)
>
> In which version of zope : 2.6, 2.7 or 3.0 ?
>
> Thanks.
We're shooting for Zope 2.7. Jim still needs to work out a
lingering issue with it.
Brian Lloyd
Hi all -
We're planning to cut 2.6.1 b2 this Friday. I wanted to give the
heads-up in case anyone was in the middle of anything that needs
to get in (I saw Toby had committed some things, and it looks
like that merge is complete).
Brian Lloyd[EMAIL PROTECTED]
V.P. Engine
ted using
ZRS (Zope Corp.'s replication / failover solution) :^)
The changes have to do with coordination of transaction commit among
multiple databases, manageability and fault-tolerance. I'll ask
Jeremy to be sure to update the CHANGES.txt with the important
changes.
Brian Lloyd
inal with
no further changes. A 2.6.2 effort could start as soon after as needed,
to add the other fixes mentioned and hopefully also include the fruit
of another bug day.
Again, sorry about the confusion...
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Co
and 2.2.2 (but the code would
contain no 2.2-isms).
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listin
rganization and artifacts (largely cribbed from
the old Z2 WS project). Please take a look and feel free to jump in an
refine, comment or refactor.
One of the first things we need to do is find someone (or a group of
someones) to spearhead the effort and "own" the project area. Any
volu
tart mapping out strategy there. A
good start might be to schedule an IRC chat so that the players
can all get together and agree on some high-level goals, so that
we have some options for concrete things to do by the time of the
conference.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering
olidays and other things going on, I don't
think b2 will actually be able to go out until at least
Monday. It looks like there might be a few left-over issues
from bug day that I'd to follow up on, but I won't be
available to do that today :(
Brian Lloyd[EMAIL PRO
> On Wednesday 10 December 2003 07:01 am PDT, Brian Lloyd wrote:
> >
> > We will be having a "bug day" next Tuesday, and the goal will
> > be that those fixes will also go into the Zope-2_6-branch to
> > be included in a 2.6.1 beta 2 to be release hopefully aro
t final a week or so after that for a late xmas present :)
This schedule should also provide enough time for the valiant
volunteers working on the 2.6.1 version of the Zope Book to
finalize things for the release.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
>
> He's in Southwestern Mississippi, which puts him closer to me than you -
> a Gulf Coast sprint? ;-)
>
> Ross
We'd also be willing to host the WS sprint here in VA if that helps -
though New Orleans sounds like a lot more fun! :^)
Brian Lloyd[EMAIL PROTECTED]
t it addresses. I'll
verify this w/Jeremy tomorrow, but last I heard ordering should only
actually be an issue for Connection objects - other objects that
play with the transaction mgr will generally not be subject to the
deadlock issue that the sorting is designed to prevent (the deadl
somewhere.
> But I agree that it's time for a bugfix release pretty soon. Most serious
> bugs should have appeared by now, and making a bug fix release
> shouldn't be
> that hard, or?
FYI I'd like to have a 2.6.1 beta out next week. Jeremy is still
looking at a few ZOD
ten the plan finalized.
Per the plan above, I'd like for there to be a (relatively short) period
for people to volunteer and add proposals to the plan, followed by a process
of prioritizing and coming to closure on what will / won't be included. I
propose in the wiki that we should probabl
o a little revamp of the dev homepage by
the end of this week to simplify a few things and hopefully make
it easier to know "what's going on", as well as posting the plans
for 2.6.1 and much-misunderstood 2.7.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.17
uot; to keep up
and manage a real-world usable Web Services package. Right now
I don't use WS in my day job, so I'm not that guy.
I've had a number of people inquire about the status of the package,
but so far no one willing to volunteer to move things forward. If
you (or anyon
allowed, but '
> 'you may have ment to use has_role.', DeprecationWarning)
> self.allowed(*args, **kw)
>
> Shouldn't that be::
>
> return self.allowed(*args, **kw)
Yes, it should. Thanks Jean. I
> Can anyone point me to the location of the configuration file for the
> Windows install in CVS? I'm sure Brian pointed it out to me once,
> but I cant
> find it at the moment...
> --
> Andy McKay
Hi Andy -
The WISE install script is in the /inst directory of the
out the issues
it addresses, you will be able to enable it explicitly using an
environment variable (without having to upgrade to 2.6).
2.7 and later releases will behave as 2.6.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
_
ixed the help system .py file and added a comment to
the book site so that this should get fixed for the next rev.
Thanks!
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
> First off, the on-line documentation description of this method is 'Append
> a value to a cookie'.
>
> Second, it breaks if you are in fact adding a second value to a header
> that already exists.
Thanks - I've checked in the fix for 2.6 and on the 2.5 branc
of us Europeans I guess.
How about _next_ Thursday (the 20th)? Things are pretty hectic here
this week, and I'd like to try to push out 2.6 a1 (which we're already
running a little behind on).
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
proposals on the 2.6 plan. For the next rev, we need to
refine the process to try to keep the scope tighter and probably
also refine the commitment process so that we know the real
status of things sooner.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http:/
ll be updating
the supported platform to Python 2.2. My best guestimate at
timing at this point is early-to-mid Q4.
Thanks all!
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
Zop
the plan. Hopefully I can run the
mbox stuff by the Zope Pope tomorrow and get back to you
then.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
Zope-Dev maillist - [EMAIL P
ting release)
actually stores the variable in REQUEST. If it were to store them
somewhere more appropriate in the DTML namespace stack, I'd be
happy to OK it.
We'd also need someone to commit to providing the extra docs
for the help system and the dtml reference section of the
VS/BugDays
Hope to see you there!
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**
>showstopper :(
>
> I agree Olivers suggestion is not a total solution, but does it have a
> showstopper problem?
Only if you happen to have an application deployed and might
ever want to upgrade your Zope installation without having to
do a total code audit :^)
Brian Lloyd[
s the textbook case for making it a Product :) We
shouldn't be putting things in the core that come with flashing
red warnings and can only be used by superusers.
What is wrong with leaving this as an add-on product? Why does
it _need_ to be a part of the core at all? Useful pro
the security
machinery or its application to domain objects (or if the security
machinery does not need to change, we need to spell out why).
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
__
o the
date (or change it yourself in the wiki).
The updated plan is at:
http://dev.zope.org/Wikis/DevSite/Projects/Zope2.6/ProposedFeatures
Once we get the commitments up to date, we can start wrangling
with the vetting...
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
en
proposed, there is not really a quick fix that doesn't have
some downside that some group somewhere considers a
showstopper :(
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
s to do this without
killing performance).
We need to find a reasonable place to document the API
addition for this before merging it.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
> > We are planning to have the inaugural bug day this
> > Friday (April 12th) from around 9 a.m. US /Eastern
> > until we've all had enough :^)
>
> Sounds good.
>
> Make it #zope-dev, as nothing ever happens there :-)
Good idea - I've change
things go well, I'd like to see this become a
regular thing (say the second Fri. each month).
Whaddya think?
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
Zope-Dev mail
27;s new traceback formatting makes the
trace information far more readable in addition to removing
filesystem path information.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
__
hard fight to get some other major change into
the same release.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mail
it's time to define a release.
Thoughts? I'll volunteer to maintain the guidelines document
on dev.zope.org if folks can send their guideline suggestions.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
_
null or valid, and code and
templates should be written to deal with the two possibilities
as a matter of course.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
___
Zope-Dev mail
always either a valid DateTime instance or None
> I'd also be interested on you take on issue #171, returning
> empty lists...
I don't have much to add to that thread. It has the same
backward-compatibility issue, but I don't perceive it to
be as big an issue as the
like optional_date. The converter handler for that type could
handle an empty field in whatever way we feel is reasonable,
without breaking existing applications. (Let the fight over
"reasonable" begin! :^)
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope
agers of security
would have to evaluate N possible security scenarios, most
of which are not readily visible to them at the time they
are setting up security).
I think that the "RedirectObject" approach could sidestep
all of these issues and provide an incremental ste
Hi all -
In an effort to better keep up with the collector, I'd like
to throw out the idea of doing periodic "bug days" (a la
the mozilla bug days), where Zope geeks and committers would
get together on IRC and spend a few hours knocking out issues.
I've drafted a preliminary bug day manifest
1 - 100 of 284 matches
Mail list logo
