- --verbose --progress didn't do what people expected

- --module matched module file paths rather than module dotted names

- Positional arguments weren't handled correctly

Changed the test-runner script, test.py to exclude packages currently
gotten via externals.

- import and whitespace cleanup

Doing so wipes out all the warning filters other tests may set
up to suppress warnings those tests need to provoke but want to
hide from the entity running the tests.

This stops all the DeprecationWarnings that were displayed from
the ZODB and ZEO tests when running Zope trunk's test suite.

- added some comments describing the meta_type info

- ZCTextIndex now accepts lexicons with the z3 interface

r39647 | jim | 2005-10-26 13:12:39 -0400 (Wed, 26 Oct 2005) | 6 lines

Fixed a bug in getting source that prevented tests from being used if
    there were pyc files around. Sigh.

Added tests for restrictions on augmented assignment and for handling
    generator expressions.

------------------------------------------------------------------------
    r39646 | jim | 2005-10-26 13:12:37 -0400 (Wed, 26 Oct 2005) | 2 lines

Added tests for handling generator expressions.

------------------------------------------------------------------------
    r39645 | jim | 2005-10-26 13:12:35 -0400 (Wed, 26 Oct 2005) | 3 lines

Added protection against the (small) risk that someone could mitate an
    object through an augmented assignment (aka inplace) operator.

------------------------------------------------------------------------
    r39644 | jim | 2005-10-26 13:12:32 -0400 (Wed, 26 Oct 2005) | 5 lines

Added protection against the (small) risk that someone could mitate an
    object through an augmented assignment (aka inplace) operator.

Also added handling for generator expressions.

------------------------------------------------------------------------
    r39643 | jim | 2005-10-26 13:12:30 -0400 (Wed, 26 Oct 2005) | 4 lines

Added notes on how restricted python works.  I hope I
    never need these again, but that's what I said the last time I had to
    rediscover how this worked. :)

- removed all dependencies on that support

Fix nonsensical test pointed out by Tim.  We now test to make sure that a subcommit attaches a _p_jar to the object.

all the time)

Stops deprecation warnings from ZODB 3.6.

Still no idea why deprecation warnings from the ZODB tests
show up (ZODB is already trying to suppress them, and that
works fine in a ZODB checkout and in a Zope3 checkout).

Make sure that savepoint creation is optimistic.

Also, now tests will be searched for in lib/python of instances.

No commit message

The checkin implies:

  - the "DBTab" package has been removed.  It is no longer necessary.
    Instead, we use ZODB 3.6's built-in multidatabase support.

  - ZODBMountPoint no longer monkey-patches ZODB to allow for mount
    support.

  - We temporarily hack setup.py to allow ZODB 3.6.0b1 to be compiled
    (it expects to be compiled via ZPackage).

Record switch to pywin32 build 205.

A one-character change to move to pywin32 build 205.

This should repair PySECURITY_ATTRIBUTES problems that
(mostly) Plone users report using recent Zopes on
Windows.

This change is in the 2.8.4 Windows installer I just
published on zope.org.  Alas, the 2.8.4 tarball there
(and the 2.8.4 tag) differs from the source used to build
the 2.8.4 Windows installer (by this one character,
bumping W32ALLVERSION in inst/WinBuilders/mk/python.mk).

- replaced url_quote by html_quote for add list values (pushing the add button escapes the value again)

there were pyc files around. Sigh.

Added tests for restrictions on augmented assignment and for handling
generator expressions.

object through an augmented assignment (aka inplace) operator.

object through an augmented assignment (aka inplace) operator.

Also added handling for generator expressions.

never need these again, but that's what I said the last time I had to
rediscover how this worked. :)

Products can look for such confgiurations to set product-specific options
(see the example '<product-config>' section in skel/etc/zope.conf.in
for sample usage).

root object from a Zope 3 point of view.

and uses zope.testing.testrunner as a module.