Hi All,
Is zLOG deprecated?
If not, it should be...
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
___
Zope-Dev maillist - Zope-Dev@zope.org
Great, so rather than fix the warnings, we add code to ignore them...
*sigh*
Chris
Stefan H. Holek wrote:
Update of /cvs-repository/Zope
In directory cvs.zope.org:/tmp/cvs-serv6383
Modified Files:
Tag: Zope-2_7-branch
test.py
Log Message:
Implemented a --nowarnings flag for test.py.
Dennis Allison wrote:
Dieter's point about not includeing the traceback makes sense
if all it does is report on the reporting code.
Yeah, the traceback just shows where the ConflictError was raised, not
what caused it, and theyr'e always in very different places...
Wlorent, do you envision
Jean-Marc Orliaguet wrote:
In my case it's mostly filesystem-based resources (css files, or images)
accessed in read mode (zope-2.8.4). But the information no matter where
it comes from has very little value compared to other messages in the
log file, because these are completely predictable.
--On 4. Dezember 2005 20:55:48 +0100 Andreas Jung [EMAIL PROTECTED]
wrote:
--On 4. Dezember 2005 14:36:17 -0500 Jim Fulton [EMAIL PROTECTED] wrote:
Zope 3 seems to ve ready for a beta release. Does that mean Zope 2
is ready?
Zope 2 should be ready. However there seems to be an
Chris Withers wrote:
Is zLOG deprecated?
If not, it should be...
+10
zLOG/__init__.py says:
Note:
This module exists only for backward compatibility. Any new code
for Zope 2.8 and newer should use the logging module from Python's
standard library directly. zLOG is only an
Just to let you know: Zope 2.9 b1 will be released together with Zope 3.2 b1
this Wednesday..so the last changes and fixes should be done until
Wednesday morning.
Thanks,
Andreas
pgpnUD4IB53W0.pgp
Description: PGP signature
___
Zope-Dev maillist -
Andreas Jung wrote:
Just to let you know: Zope 2.9 b1 will be released together with Zope
3.2 b1
this Wednesday..so the last changes and fixes should be done until
Wednesday morning.
I'm going to try to get a 3.2 beta out today.
Jim
--
Jim Fulton mailto:[EMAIL PROTECTED]
--On 5. Dezember 2005 16:10:11 +0100 Andreas Jung [EMAIL PROTECTED]
wrote:
Just to let you know: Zope 2.9 b1 will be released together with Zope 3.2
b1
this Wednesday..so the last changes and fixes should be done until
Wednesday morning.
We will release 2.9 earlier. Jim is going to
I've added a long needed hasObject method to ObjectManager.
Note that BTreeFolder2 has had it for a long time and it's quite useful.
Enjoy.
Florent
--
Florent Guillaume, Nuxeo (Paris, France) CTO, Director of RD
+33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED]
Rocky Burt wrote:
Anyone know if there is any plan to add a toplevel products folder in
the zope svn repo like there currently is in zope's cvs repo? I know
this has held up a few products from going from zope CVS to SVN.
I don't think a separate Products folder is is necessary. Just make
On Fri, 2005-12-02 at 23:00 +0100, Florent Guillaume wrote:
1. Do you want these ConflictErrors retried logs to be at level:
- INFO
INFO
- BLATHER
- DEBUG
- not logged
- other
2. In addition, please specify if you feel those retried
ConflictErrors should have their full traceback
Philipp von Weitershausen wrote:
If not, it should be...
+10
Yeah, me too! Hence why I was asking ;-)
That means we could deprecate it even in Zope 2.9, using zLOG has
already been discouraged in Zope 2.8.
Cool, Andreas, can you make it start emitting deprecation warnings?
(if you do,
Chris Withers wrote:
# In the days of zLOG, there were 7 standard log levels, and
ZODB/ZEO used
# all of them. Here's how they map to the logging package's 5
standard
# levels:
#
#zLOG logging
#----
#
We probably want an ALL level as well which would map to the NOTSET
of the Python logging code and log everything.
Florent, I don't see a TRACE level in this list. Did you think one was
needed?
On Mon, 5 Dec 2005, Florent Guillaume wrote:
Chris Withers wrote:
# In the days of zLOG,
[Dennis Allison]
We probably want an ALL level as well which would map to the NOTSET
of the Python logging code and log everything.
Why not call it NOTSET? Then you already have it ;-) Or forget it --
TRACE gets everything anyway.
Florent, I don't see a TRACE level in this list. Did you
Florent Guillaume wrote at 2005-12-2 23:00 +0100:
Please vote for the level at which you want to log retried conflict
errors. These are the ConflictErrors that aren't returned to the user
but automatically retried by the Zope publisher.
1. Do you want these ConflictErrors retried logs to be
On Sat, Dec 03, 2005 at 11:29:48AM -0500, Tres Seaver wrote:
Paul Winkler wrote:
(snip)
... AcceleratedHTTPCacheManager has no test
suite at all.
Erm. Actually it does; Tres added it on the TRUNK many months ago.
I was looking at a 2.7 checkout! Mea culpa.
However, the test suite currently
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florent Guillaume wrote:
Please vote for the level at which you want to log retried conflict
errors. These are the ConflictErrors that aren't returned to the user
but automatically retried by the Zope publisher.
1. Do you want these
Chris Withers wrote:
Philipp von Weitershausen wrote:
If not, it should be...
+10
Yeah, me too! Hence why I was asking ;-)
That means we could deprecate it even in Zope 2.9, using zLOG has
already been discouraged in Zope 2.8.
Cool, Andreas, can you make it start emitting
Jean-Marc Orliaguet wrote at 2005-12-4 22:28 +0100:
...
In the log flle I'd like to be informed about events that are
unexpected. Conflict errors of this kind occur by design.
This argument is not convincing:
In a similar way, I could argue that MemoryErrors are there
by design.
While
Chris Withers wrote at 2005-12-5 07:37 +:
Great, so rather than fix the warnings, we add code to ignore them...
Usage: ./bin/zopectl test --keepbytecode --nowarnings --dir Products/CMFPlone
A colleague of mine will be very happy:
The hundreds of (mostly stupid deprecation) warnings
Andreas Jung wrote:
make sdist:
[EMAIL PROTECTED]:~/sandboxes/Zope-2.9/2.9.0b1: make sdist
zpkg -C /develop/sandboxes/Zope-2.9/2.9.0b1/releases/Zope2.cfg
'version.txt' doesn't match any files in collection
(in /develop/sandboxes/Zope-2.9/2.9.0b1/lib/python/zope/app/PACKAGE.cfg)
23 matches
Mail list logo
