summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2009-11-29Prep for 1.2a2.Chris McDonough
2009-11-29- Fixed "Startup" narrative documentation chapter; it was explainingChris McDonough
"the old way" an application constructor worked.
2009-11-29Typo.Chris McDonough
2009-11-29(no commit message)Chris McDonough
2009-11-29Meh.Chris McDonough
2009-11-29Fix.Chris McDonough
2009-11-29(no commit message)Chris McDonough
2009-11-29- Trying to use an HTTP method name string such as ``GET`` as aChris McDonough
``request_type`` predicate caused a startup time failure when it was encountered in imperative configuration or in a decorator (symptom: ``Type Error: Required specification must be a specification``). This now works again, although ``request_method`` is a more modern predicate.
2009-11-29Prep for 1.2a1.Chris McDonough
2009-11-29Sigh.Chris McDonough
2009-11-28Get rid of these mentionings of zope.component for grep purposes.Chris McDonough
2009-11-28- Unit tests which use ``zope.testing.cleanup.cleanUp`` for theChris McDonough
purpose of isolating tests from one another may now begin to fail due to lack of isolation between tests. Here's why: In repoze.bfg 1.1 and prior, the registry returned by ``repoze.bfg.threadlocal.get_current_registry`` when no other registry had been pushed on to the threadlocal stack was the ``zope.component.globalregistry.base`` global registry (aka the result of ``zope.component.getGlobalSiteManager()``). In repoze.bfg 1.2+, however, the registry returned in this situation is the new module-scope ``repoze.bfg.registry.global_registry`` object. The ``zope.testing.cleanup.cleanUp`` function clears the ``zope.component.globalregistry.base`` global registry unconditionally. However, it does not know about the ``repoze.bfg.registry.global_registry`` object, so it does not clear it. If you use the ``zope.testing.cleanup.cleanUp`` function in the ``setUp`` of test cases in your unit test suite instead of using the (more correct as of 1.1) ``repoze.bfg.testing.setUp``, you will need to replace all calls to ``zope.testing.cleanup.cleanUp`` with a call to ``repoze.bfg.testing.setUp``. If replacing all calls to ``zope.testing.cleanup.cleanUp`` with a call to ``repoze.bfg.testing.setUp`` is infeasible, you can put this bit of code somewhere that is executed exactly **once** (*not* for each test in a test suite; in the `` __init__.py`` of your package would be a reasonable place):: import zope.testing.cleanup from repoze.bfg.testing import setUp zope.testing.cleanup.addCleanUp(setUp) - When there is no "current registry" in the ``repoze.bfg.threadlocal.manager`` threadlocal data structure (this is the case when there is no "current request" or we're not in the midst of a ``r.b.testing.setUp``-bounded unit test), the ``.get`` method of the manager returns a data structure containing a *global* registry. In previous releases, this function returned the global Zope "base" registry: the result of ``zope.component.getGlobalSiteManager``, which is an instance of the ``zope.component.registry.Component`` class. In this release, however, the global registry returns a globally importable instance of the ``repoze.bfg.registry.Registry`` class. This registry instance can always be imported as ``repoze.bfg.registry.global_registry``. Effectively, this means that when you call ``repoze.bfg.threadlocal.get_current_registry`` when no request or ``setUp`` bounded unit test is in effect, you will always get back the global registry that lives in ``repoze.bfg.registry.global_registry``. It also means that :mod:`repoze.bfg` APIs that *call* ``get_current_registry`` will use this registry. This change was made because :mod:`repoze.bfg` now expects the registry it uses to have a slightly different API than a bare instance of ``zope.component.registry.Components``.
2009-11-28Rearrange.Chris McDonough
2009-11-28(no commit message)Chris McDonough
2009-11-28Deal with registries we may not understand.Chris McDonough
2009-11-28Clarify.Chris McDonough
2009-11-28More windows friendliness.Chris McDonough
2009-11-28Deal with Windows.Chris McDonough
2009-11-28Allow initial registry setup to be called via a ``setup_registry`` method.Chris McDonough
Allow path specifications for renderers which are already resource specifications.
2009-11-28Typo.Chris McDonough
2009-11-28More fixes.Chris McDonough
2009-11-28More Rossi fixes.Chris McDonough
2009-11-28Fix mistakes caught by Rossi.Chris McDonough
2009-11-28ZCA -> ZCA registryChris McDonough
2009-11-28Add a what's new document.Chris McDonough
2009-11-28Yes.Chris McDonough
2009-11-28Notes.Chris McDonough
2009-11-28Fix.Chris McDonough
2009-11-28Fix.Chris McDonough
2009-11-28Updates.Chris McDonough
2009-11-28Typo.Chris McDonough
2009-11-28Bug found through interactive usage.Chris McDonough
2009-11-28Fix.Chris McDonough
2009-11-28Fix.Chris McDonough
2009-11-28General fixes.Chris McDonough
2009-11-28Fix up starter template generally.Chris McDonough
2009-11-28Fix.Chris McDonough
2009-11-28Document the request-only calling convention as the default.Chris McDonough
2009-11-28- Turn paths into resource specs in ZCML directives that useChris McDonough
context.path.
2009-11-28Docs.Chris McDonough
2009-11-27Remove ``zcml_configure`` API.Chris McDonough
2009-11-27(no commit message)Chris McDonough
2009-11-27(no commit message)Chris McDonough
2009-11-27Terminology.Chris McDonough
2009-11-27Meh.Chris McDonough
2009-11-27Meh.Chris McDonough
2009-11-27Add threadlocal to API.Chris McDonough
2009-11-27Updates.Chris McDonough
2009-11-27Coverage.Chris McDonough
2009-11-27Coverage.Chris McDonough
Remove set_security_policies configurator API method.
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-29 14:52:31 +0000