[Checkins] SVN: grok/trunk/ Moved to GitHub.
Stephen Richter
cvs-admin at zope.org
Fri Mar 1 15:41:00 UTC 2013
Log message for revision 129944:
Moved to GitHub.
Changed:
D grok/trunk/CHANGES.txt
D grok/trunk/COPYRIGHT.txt
D grok/trunk/CREDITS.txt
D grok/trunk/INSTALL.txt
D grok/trunk/LICENSE.txt
A grok/trunk/MOVED_TO_GITHUB
D grok/trunk/README.txt
D grok/trunk/TODO.txt
D grok/trunk/bootstrap.py
D grok/trunk/buildout.cfg
D grok/trunk/doc/
D grok/trunk/documentation.cfg
D grok/trunk/etc/
D grok/trunk/grokwiki/
D grok/trunk/grokwiki.cfg
D grok/trunk/setup.py
D grok/trunk/src/
-=-
Deleted: grok/trunk/CHANGES.txt
===================================================================
--- grok/trunk/CHANGES.txt 2013-03-01 14:56:57 UTC (rev 129943)
+++ grok/trunk/CHANGES.txt 2013-03-01 15:40:59 UTC (rev 129944)
@@ -1,834 +0,0 @@
-Grok changes
-************
-
-1.10.4 (unreleased)
-===================
-
-- Nothing changed yet.
-
-
-1.10.3 (2012-05-10)
-===================
-
-- Make sure the correct layout is retrieved for layout aware form components
- too.
-
-1.10.2 (2012-05-10)
-===================
-
-- Import the grokcore.layout.layout directive into the grok namespace too.
-
-1.10.1 (2012-05-02)
-===================
-
-- Update version requirements.
-
-1.10 (2012-05-02)
-=================
-
-- Split off the Application component and the local_utility directive to
- grokcore.site. A backwards compatibility import for Application is left
- in place.
-
-- Split off the catalog and indexing components from grok into
- grokcore.catalog.
-
-- The permissions() directive, the Permission component and the Role
- component moved from grok to grokcore.security. The grok package imports
- these component, so they can still be accessed through the grok api.
-
-1.9 (2011-09-06)
-================
-
-- Added imports for `querySubscriptions()`, `queryMultiSubscriptions()`,
- `queryOrderedSubscriptions()` and `queryOrderedMultiSubscriptions()` functions
- that complement the Subscriptions and MultiSubscriptions components.
-
-1.8 (2011-07-14)
-================
-
-- Incorporate grokcore.chameleon and have it configured by default.
-
-- Expose the Layout, Page, AddFormPage, EditFormPage, DisplayFormPage and
- FormPage components that are brought by grokcore.layout. The grok variants
- mixin application_url() and flash() functionality typically found in grok's
- viewish components.
-
-- Expose the ExecptionPage, NotFoundPage and UnauthorizedPage component from
- grokcore.layout.
-
-- Expose the ContentProvider component from grokcore.view
-
-- Declare the name "index" as default view name for error views.
-
-1.7 (2011-05-26)
-================
-
-- Directly depend on zope.app.wsgi and configure it too to have the useful
- IResult adapters for (temporary) files registered.
-
-- Import grokcore.component.global_adapter too.
-
-1.6 (2011-04-04)
-================
-
-- Fix tests that relied on older versions of zope.testbrowser.
-
-- Added grok.index.Value component.
-
-1.5 (2011-02-14)
-================
-
-- Added import for Subscription and MultiSubscription components.
-
-1.4.3 (2011-02-08)
-==================
-
-- Fix tests now that error views no longer by default provide ISystemErrorView.
-
-1.4.2 (2011-01-20)
-==================
-
-- Should've listed IApplication as part of the grok API too.
-
-1.4.1 (2011-01-20)
-==================
-
-- Grok should still provide IApplication in the grok API, even now that it
- got moved to grokcore.site.interfaces.
-
-1.4 (2011-01-20)
-================
-
-- Define error view baseclasses for IException, INotFound and IUnauthorized
- errors: grok.ExceptionView, grok.NotFoundView, grok.UnauthorizedView. Lifts
- the indirect dependency on zope.app.http and zope.app.exception.
-
-- Moved the XMLRPC, REST component into separate packages
- grokcore.xmlrpc and grokcore.rest. Consequently the custom traverse
- components that Grok defined were moved to grokcore.traverser. Grok
- the-python-package acts more and more like an import-hub.
-
-- To build the docs we now use `collective.recipe.sphinxbuilder`
- instead of our own, early hack (get rid of `grokdocs`
- subpackage). Buildout now generates ``grokdocs2html`` and
- ``grokdocs2pdf`` which should do what you think they do.
-
-- The `IApplication` interface, and getApplication() moved to
- ``grokcore.site``.
-
-1.3 (2010-11-03)
-================
-
-- The `IGrokSecurityView` interface has been to ``grokcore.view``.
-
-- The `make_checker` util function has been moved to ``grokcore.view``.
-
-- The base publisher has been moved to ``grokcore.view`` as an
- optional feature : security_publication.
-
-- The JSON component and grokker are now moved to
- ``grokcore.json``. Grok now depends on this new grokore package.
-
-- Update to latest martian and grokcore.component.
-
-1.2.1 (2010-10-26)
-==================
-
-- Grok tutorial example projects updated.
-
-- Documentation updates in preparation for the Grok Toolkit 1.2 release.
-
-- Use zc.buildout-1.5.2.
-
-1.2 (2010-10-13)
-================
-
-- No changes were necessary.
-
-1.2a (2010-10-07)
-=================
-
-- Grok and the Grok Toolkit now use zc.buildout-1.5.1 that should simplify
- Grok's installation story significantly. It is now possible to use a system
- Python installation for installing Grok. This obsoletes the ``virtualenv``
- requirement.
-
-- Grok and the Grok Toolkit will use the ZTK-1.0 release. Note though that
- several package versions are overridden to include bugfix releases.
-
-- Various dependencies have been updated.
-
-- Removed z3c.testsetup-specific test collector from grok.testing. You can
- still use z3c.testsetup with grok, but have to declare the dependency in your
- project's ``setup.py`` explicitly.
-
-- The grok.View component now uses the grokcore.message package for its
- `flash` method.
-
-- Grok test zcml now explicitly sets a defaultView name (to `index.html`).
- This has been added since we no longer depend on packages such as
- zope.app.zcmlfiles, that used to take care of that configuration step.
-
-- Internationalization of title and description of roles are not lost anymore.
-
-- `create_application` now raises a `KeyError`, in cases of key duplication,
- to match the ``zope.container`` behavior. Tests have been adapted accordingly.
-
-- Added `KeyError` error handling to the existing `DuplicationError`, to fit
- the ``zope.container`` changes. Tests have been adapted accordingly.
-
-1.1.1 (2010-05-30)
-==================
-
-- Make use of the groktoolkit 1.1.1 that includes several bugfix releases
- of Grok's dependencies such as:
-
- - zope.password, where the SSHAPasswordManager was fixed.
-
- - zope.publisher, that fixes the long standing XML-RPC "hanging" bug.
-
-- Cleanups in the buildout parts.
-
-- Remove zope.app.twisted.
-
-1.1 (2010-05-18)
-================
-
-- Add zope.pluggablauth as a dependency.
-
-1.1rc1 (2010-02-25)
-===================
-
-* Now using grokcore.content for the base content types : Model,
- Container and OrderedContainer.
-
-* Lifted the dependency on zope.app.authentication and depend on
- zope.password instead.
-
-* Lifted dependencies on deprecate packages zope.app.error and
- zope.app.securitypolicy and zope.app.session.
-
-Beside these changes lot of work has been undertaken to remove as much
-dependencies on "older" zope.app.* packages as possible from Grok itself
-and from the dependencies of Grok. This work is not complete yet.
-
-1.1a2 (2009-12-22)
-==================
-
-* Updated z3c.recipe.compattest's version and used it for a bin/compattest
- that tests grok and all its dependencies.
-
-* Add grok.getApplication() that, similar to grok.getSite() retrieves
- the "nearest" enclosing grok.Application object.
-
-* Use zope.container instead of zope.app.container.
-
-* Use zope.catalog instead of zope.app.catalog.
-
-* Use zope.intid instead of zope.app.intid.
-
-* Use zope.keyreference instead of zope.app.keyreference.
-
-1.1a1 (2009-11-17)
-==================
-
-* This release depends on grokcore.view 1.13a1.
-
-* Add ZTK support (currently ZTK 1.0dev).
-
-* Grokdocs now uses ZTK pinned versions.
-
-* The ``grok.permissions()``, that is used in the ``grok.Role`` component now
- accepts references to ``grok.Permission`` class, not just permission ids.
- This behaviour is now symetrical to the ``grok.require()`` directive.
-
-* Added an util function, ``create_application``, to create an
- application and trigger the correct events during the process.
-
-* Grok now provides an application-centric event to complete the
- zope.lifecycle ones. This event, ``ApplicationInitializedEvent``, is
- destined to be trigged after the application has been added to a
- container. At this particular step, the application is considered
- safe for additional content to be created.
-
-* Use grokcore.site and grokcore.annotation instead of builtins
- implementations.
-
-* Update the reference to mention ``zope.View``.
-
-* Update the reference to mention direct references to permissions in
- ``grok.require`` and ``grok.permissions`` in ``grok.Role``.
-
-* Fix documentation bug where virtualenv wasn't explained correctly.
-
-* Remove the ``grok.View`` permission declaration in ``etc/site.zcml.in``,
- should have gone in 1.0b2 already
-
-1.0 (2009-10-07)
-================
-
-* Removed IReRaiseException adapter registration for IUnauthorized again in
- favor of using grokcore.startup's configurable``debug_application_factory``
- WSGI application factory function.
-
-* Use newer versions of simplejson and pytz.
-
- See also https://bugs.launchpad.net/grok/+bug/432115
-
-1.0b2 (2009-09-17)
-==================
-
-See: `upgrade_notes_1.0b2` for special notes on upgrading to this release.
-
-* Revert back to an older version of ``grokui.admin`` that has not seen any
- changes related to the ``grok.View`` permission and the
- ``View``/``CodeView`` split and still has the introspector that is removed
- from newer versions.
-
-* ``grokcore.view``, ``grokcore.viewlet`` and ``grokcore.formlib`` and
- Grok itself have been updated to undo the ``View``/``CodeView``
- split that we had temporarily introduced in the development versions
- after Grok 1.0a4. This means the behavior of ``grok.View`` is
- unchanged from Grok 1.0a4. Nothing to see here!
-
-* Changed the default permission to ``zope.View`` instead of
- ``zope.Public``. This means a modification needs to be made to your
- ``site.zcml`` if you're upgrading an existing Grok-based
- project. See the upgrade notes for more information.
-
- See also https://bugs.launchpad.net/grok/+bug/387332
-
-* Bump used zope.app.wsgi version (now: 3.4.2) to support
- product-configs in zope.conf files with paster. Fix
- https://bugs.launchpad.net/grok/+bug/220440
-
-* Default location for Data.fs and logfiles of grok's sample application is
- now ``var/filestorage/`` and ``var/log/`` instead of ``parts/data/``
- and ``parts/log/``.
-
-* Bump used `z3c.testsetup` version (now: 0.4). Fix
- https://bugs.launchpad.net/grok/+bug/395125
-
-* Bump used ZODB3 version (now: 3.8.3). Fix
- https://bugs.launchpad.net/grok/+bug/410703
- https://bugs.launchpad.net/grok/+bug/424335
-
-* Added `zope.publisher.interfaces.IReRaiseException` adapter for
- IUnauthorized exceptions. Closes
- https://bugs.launchpad.net/grok/+bug/332061
-
-* Removed `docutils` and `Pygment` from versions.cfg. Both are pinned
- in grokdocs subpackage. Closes
- https://bugs.launchpad.net/grok/+bug/340170
-
-* Corrected Content-type; JSON views now report 'application/json'.
-
-* updated zope.publisher dependency to 3.4.8 (fix paster.httpserver
- related bugs in XMLRPC, PUT)
-
-* switched buildout to paster based template (like grokproject default)
- https://bugs.launchpad.net/grok/+bug/307197
-
-* changed interpreter name from 'python' to 'grokpy'.
-
-* Restructured the upgrade and change documentation so that they now
- get generated into separate files by Sphinx
-
-1.0b1 (2009-09-14)
-==================
-
-* This release happened but never really was fully completed. See the
- release notes for 1.0b2 instead.
-
-1.0a4 (2009-05-21)
-==================
-
-* Pin grokcore.view to 1.7.
-
-* Import zope.app.container interfaces from their actual definition not from a
- re-import.
-
-* JSON views now report a Content-type: text/json. See
- https://bugs.launchpad.net/bugs/362902
-
-
-1.0a3 (2009-04-10)
-==================
-
-* Pin grokui.admin to 0.3.2
-
-* Pin grokcore.view to 1.5.
-
-* Pin grokcore.component to 1.6.
-
-
-1.0a2 (2009-04-08)
-==================
-
-* Documentation and doc string updates.
-
-* Pin grokui.admin to 0.3.
-
-* Pin grokcore.view to 1.4.
-
-* Synced versions.cfg with the latest KGS release available at:
- http://download.zope.org/zope3.4/3.4.0/versions.cfg
-
-* Expose ``IBeforeTraverseEvent`` for import in the ``grok`` namespace.
-
-1.0a1 (2009-01-08)
-==================
-
-See: `upgrade_notes_1.0a1` for special notes on upgrading to this release.
-
-Feature changes
----------------
-
-* Introduced ``grok.interfaces.IGrokSecurityView``, a marker interface
- which non-Grok views can use to state that they want to be handled
- like regular Grok views by the Grok publisher.
-
-* Expose the ``DirectoryResource`` component from grokcore.view and the
- accompanying ``path`` directive.
-
-* Similar to the layers and skins restructuring, the ``grok.RESTProtocol``
- baseclass has been removed in favour of a ``grok.restskin(name)`` directive
- that can be used on REST layer interfaces. Introduced the IRESTLayer base
- interfaces for defining REST layers.
-
-* Besides our extensive existing documentation, we have also started
- to add a lot of docstrings to the Grok source code so it becomes
- easier to understand.
-
-Bug fixes
----------
-
-* Have GrokForm define an empty actions attribute by default, in order
- for "action-less" forms to work easily.
-
-* Allow the grok.layer() directive on JSON components. Closes
- https://bugs.launchpad.net/grok/+bug/310558
-
-* Close a bad security hole (also fixed in 0.14.1 and other
- releases). See
- http://grok.zope.org/blog/security-issue-in-grok-please-upgrade
-
-Restructuring
--------------
-
-* Viewlet-related base classes and helpers have been moved out to a
- ``grokcore.viewlet`` package which Grok now depends on.
-
-0.14 (2008-09-29)
-=================
-
-See: `upgrade_notes_0.14` for special notes on upgrading to this release.
-
-Feature changes
----------------
-
-* Grok now officially supports Python 2.5 and still supports Python 2.4.
-
-* Merged the versions from the zope 3.4c7 KGS (known good set):
- http://download.zope.org/zope3.4/versions-3.4.0c7.cfg
- So we are now using the latest Zope 3 releases for all Zope packages.
-
-Restructuring
--------------
-
-* The ``grok.admin`` subpackage has been factored out to a separate
- package ``grokui.admin``. To have the Grok admin UI available in
- your environment, add ``grokui.admin`` to the required packages in
- the ``setup.py`` of your package.
-
-* Removed ``grok.Skin`` baseclass in favour of a ``grok.skin(name)``
- directive that can be used on layer interfaces. Also removed the
- ``IGrokLayer`` interface in favour of exposing ``IBrowserRequest``
- from the grok package.
-
-* Security-related directives and helpers have been moved out to a
- ``grokcore.security`` package.
-
-* View-related base classes, directives and grokkers have been moved
- out to a ``grokcore.view`` package.
-
-* Form-related base classes and helpers have been moved out to a
- ``grokcore.formlib`` package.
-
-Bug fixes
----------
-
-* Replace zope.deprecation.tests.warn with grok.testing.warn to:
-
- * Make the signature identical to warnings.warn
-
- * To check for \*.pyc and \*.pyo files.
-
- When zope.deprecation is fixed this warn() function can be removed again.
- Makes all the tests pass under Python-2.5.
-
-0.13 (2008-06-23)
-=================
-
-See: `upgrade_notes_0.13` for special notes on upgrading to this release.
-
-Restructuring
--------------
-
-* The basic component base classes (``Adapter``, ``MultiAdapter``,
- ``GlobalUtility``), their grokkers, as well as many of the basic
- directives have been factored out to a reusable
- ``grokcore.component`` package.
-
-* Ported directives to Martian's new directive implementation. As a
- result, many helper functions that were available from ``grok.util``
- were removed. The functionality is mostly available from the
- directives themselves now.
-
-* Refactored class grokkers to make use of Martian's new declarative
- way for retrieving directive data from classes, and Martian's new
- declarative way to write grokkers. See `upgrade_notes_0.13`
- for more information.
-
-
-Feature changes
----------------
-
-* ``GrokTemplate`` sets up the namespaces for the template by calling
- ``default_namespace() ``on the view component the template is
- associated with. As a result, ``ViewletManagers`` and ``Viewlet``
- can now push in the ``viewletmanager`` and ``viewlet`` namespaces
- into the template.
-
-* Updated tutorial section about grokproject to fit the latest changes.
-
-* Added ``grok.traversable`` directive for easy traversal to attributes and
- methods.
-
-* ``grok.require()`` can refer to subclasses of ``grok.Permission``
- directly, instead of their id. This, for one, avoids making typos in
- permission ids. Permission components *do* still need the
- grok.name() directive for defining the permission's id.
-
-* Added an optional parameter ``data`` to the method ``url()`` that
- accepts a dictionary that is then converted to a query string. See
-
- http://grok.zope.org/documentation/how-to/generate-urls-with-the-url-function-in-views/view
-
-* Added an ``OrderedContainer`` component.
-
-* Introduced the new `sphinx`-based documentation engine. See
- grokdocs/README.txt for details.
-
-* Merged the versions from the 3.4 KGS (known good set):
- http://download.zope.org/zope3.4/versions-3.4.0c1.cfg
-
- We are now using the latest Zope 3 releases for all Zope packages.
- See `upgrade_notes_0.13` for more information.
-
-* Added support for easier test setup based on ``z3c.testsetup``. This
- is a more stable and more powerful implementation of
- ``grok.testing.register_all_tests()``. See
-
- http://grok.zope.org/documentation/how-to/tests-with-grok-testing
-
- for details.
-
-* There is now a new ``IContext`` interface available. If you make
- your class implement that interface, it (and its subclasses) will be
- candidates for being a context in a module (for automatic context
- lookup if ``grok.context`` is not present). This relies on a feature
- introduced in ``grokcore.component`` 1.1.
-
-* ``grok.Model`` implements ``grok.interfaces.IContext`` now (which is
- imported from ``grokcore.component``). ``grok.Container`` now
- implements ``grok.interfaces.IContainer``. Traversers and default
- views have been set up for these interfaces, so that new
- implementations that function as a model or container can be easily
- created. Just use ``grok.implements(IContainer)`` or
- ``grok.implements(IContext)``. This is useful for Grok extensions
- that want to implement new content classes.
-
-Bug fixes
----------
-
-* Fix https://bugs.launchpad.net/grok/+bug/226555: the ``url()`` method on
- ``ViewletManager`` and ``Viewlet`` has been removed now that there's easy
- access to the view component the viewlet(manager) is registered for.
-
-* Fix https://bugs.launchpad.net/grok/+bug/231106: Use the
- viewletmanager.sort() method for sorting viewlets by using
- util.sort_components().
-
-* grok.REST views now have a properly set ``__parent__`` attribute and
- will correctly allow acquisition from parent objects, as it's used
- by the security policy for acquiring local grants, for example.
-
-* Fix https://bugs.launchpad.net/grok/+bug/229677:
- zope.app.securitypolicy egg missing. Now zope.app.securitypolicy
- 3.4.6 is additionally required by Grok and fetched by buildout.
-
-* Removed first testsetup hack from grok.testing.
-
-* Version 2.1 of z3c.autoinclude contained code that caused Grok to
- fail to start on some platforms if the system-supplied Python was
- used (at least on some versions of Ubuntu and Debian). Now include
- version 2.2 of z3c.autoinclude which should fix this problem. This
- fix was also made on Grok 0.12 in its online versions list after
- release.
-
-* Port fix of zope.formlib to correctly adapt the context to a FormField's
- interface, not the field.
-
-0.12 (2008-04-22)
-=================
-
-See: `upgrade_notes_0.12` for special notes on upgrading to this release.
-
-Feature changes
----------------
-
-* The new release needs new version of grokproject, please do::
-
- $ easy_install -U grokproject
-
-* Added testsetup classes in grok.testing to improve easy setup of
- unit- and functional tests.
-
-* Add support for viewlets and viewlet managers, ``grok.Viewlet``
- and ``grok.ViewletManager``.
-
-* Add a new directive, ``grok.order()``, which can be used to help
- sort components. At the time it is not used yet, but we intend to
- use it for the viewlets support. Note that this means Grok now
- requires Martian 0.9.3 or higher. See ``grok.interfaces`` for more
- documentation on this directive.
-
-* Now depend on ``z3c.autoinclude``. This allows the use of the
- ``<includeDependencies package="."/>`` directive, which automatically loads
- up ZCML needed for the dependencies listed in your project's
- ``setup.py``. The new release of grokproject adds this line
- automatically. Upgrade ``grokproject`` to make use of this
- functionality in new projects::
-
- $ easy_install -U grokproject
-
-* Classes that end with "-Base" are no longer implicitly considered base
- classes. These classes need to have the grok.baseclass() directive added to
- them explicitly.
-
- See `upgrade_notes_0.12` for more information.
-
-Bug fixes
----------
-
-* Do not register the publishTraverse and browserDefault methods of the
- JSON component as views.
-
-* Methods with names that start with an '_' are not registered as views
- for XMLRPC, REST and JSON components.
-
-* Use a configuration action for the registration of the static directory.
-
-* Fix imports from zope.app.securitypolicy.
-
-* Grok does not raise a GrokError anymore when it finds unassociated
- templates, but will issue a UserWarning.
-
-* Fix https://bugs.launchpad.net/grok/+bug/161948: grok.testing.grok()
- now also loads the ZPT template factories so that unit tests that
- need to configure views with ZPT templates continue to work.
-
-* Changed a few remaining references to ``grok.grok`` and
- ``grok.grok_component`` to their correct equivalents in
- ``grok.testing``.
-
-* ``grok.testing.grok_component()`` could not be used in a pure
- doctest. This needed a bugfix in Martian (since 0.9.2). Add a test
- that demonstrates this problem.
-
-* Fix https://bugs.launchpad.net/grok/+bug/162437: grok.Form and its
- subclasses did not implement IBrowserView.
-
-* Fix https://bugs.launchpad.net/grok/+bug/185414: grok introspector
- was broken for zipped eggs.
-
-* Fix https://bugs.launchpad.net/grok/+bug/125720: server control form
- had shutdown as default action, even when entering an admin message.
-
-* Fix https://bugs.launchpad.net/grok/+bug/80403: Fix situation where
- a module name is identical to the package name. At least modules
- with templates can now have same name as their package.
-
-* Multiple skins and REST protocols could be registered under the same
- name, but this is actually a conflict. Now give configuration
- conflict error when someone tries this.
-
-* Overriding traversal behavior using the ``traverse()`` method or
- ``grok.Traverser`` failed in the face of (REST) ``PUT`` and
- ``DELETE``. XML-RPC also failed when custom traversal was in use.
-
-* Fix https://bugs.launchpad.net/grok/+bug/187590 where config action
- discriminators for permission and role registrations were incorrect.
-
-* Permission definitions received the wrong, too high, configure
- action priority (not to be confused with grokker priority). In some
- cases this caused permissions to be defined later than they were
- used. Use a low action priority instead for permissions.
-
-Restructuring
--------------
-
-* Refactor commonalities out of meta.py.
-
-* zope.app.securitypolicy is no longer used. zope.securitypolicy provides
- all securitypolicy features used by Grok.
-
-0.11 (2007-11-08)
-=================
-
-See: `upgrade_notes_0.11` for special notes on upgrading to this release.
-
-Feature changes
----------------
-
-* Integrated skins and layers: ``grok.layer``, ``grok.IGrokLayer``,
- ``grok.Skin``.
-
-* Grok now supports hooking in new template languages without much work.
- See also doc/minitutorials/template-languages.txt. See Restructuring below
- for more techinical info.
-
-* Accessing a template macro via context/@@the_view/the_template is now
- deprecated for the standard ZPT story of using
- context/@@the_view/macro/the_template.
-
-* There is now a grok.direct() directive that can be used on GlobalUtilities
- to mark that the class provides the utility interface directly and need
- no instantiation.
-
-* Removed ``grok.define_permission`` in favor of the
- ``grok.Permission`` component base class. You should now subclass
- this base class to define permissions. See also
- doc/minitutorials/permissions.txt
-
-* Added the ``grok.Role`` component base class to define roles.
-
-* The admin UI now displays and offers deletion of broken objects.
-
-* Removed support for defining model schemas using an inner class with
- the special name ``fields``. This was abandoned in favor the usual
- Zope 3 way of defining schemas in interfaces and implementing them
- in our Grok models.
-
-* Integrated REST support. See doc/minitutorials/rest.txt for usage
- information.
-
-Bug fixes
----------
-
-* Remove zc.recipe.egg, zc.recipe.filestorage, zc.recipe.testrunner,
- zc.zope3recipes from version requirements.
-
-* The admin UI now shows interfaces in modules.
-
-* ``handle...`` is not a special function name anymore.
-
-* Views no longer need a custom ``AbsoluteURL`` view to determine
- their URL, since each instance now properly gets a ``__name__``
- attribute.
-
-* buildout.cfg extends versions.cfg to pin down the versions of the
- dependency tree. See also http://grok.zope.org/releaseinfo/readme.html
-
-Restructuring
--------------
-
-* Grokkers now emit configuration actions, much like ZCML directive
- handlers do. If you defined custom grokkers,
- see `upgrade_notes_0.11` for more information.
-
-* The new pluggable template language support includes some restructuring:
-
- - GrokPageTemplate is now split up into two. BaseTemplate, on which all
- templates need to be based, and GrokTemplate, which also provides a
- set of methods for easy integration of templating languages.
-
- - All objects based on GrokTemplate are now grokked, instead of having
- separate grokkers for each type of template.
-
- - The View is now completely template-language agnostic, which makes it
- easy to hook in new page template languages.
-
- - There are now new interfaces (ITemplate and ITemplateFileFactory)
- used when you implement support for a new templating language.
-
-* Changed the way grok's functional tests are set up. Instead of each
- test case doing its own test setup, it is now done once by the
- ftesting layer. This avoids ordering problems when some ftests
- would influence the environment of other ftests that were run later
- in time.
-
-0.10.2 (2007-10-24)
-===================
-
-Bug fixes
----------
-
-* Remove zc.recipe.egg, zc.recipe.filestorage, zc.recipe.testrunner,
- zc.zope3recipes from version requirements.
-
-* Require zope.app.error = 3.5.1
-
-0.10.1 (2007-10-10)
-===================
-
-Bug fixes
----------
-
-* buildout.cfg extends versions.cfg to pin down the versions of the
- dependency tree. This should avoid the situation where we release
- Grok, some dependency changes, and Grok breaks as a result. In
- conjunction with this we will also be releasing a new version of
- grokproject that will use this version infrastructure by default.
-
- For more information about this change, see:
- http://grok.zope.org/releaseinfo/readme.html
-
-0.10 (2007-08-21)
-=================
-
-Feature changes
----------------
-
-* Integrated admin user interface.
-
-* Configuration using Martian (http://pypi.python.org/pypi/martian).
-
-* Flash message infrastructure included.
-
-* Adjust dependencies for Grok so that grokproject should work on
- Windows.
-
-Bug fixes
----------
-
-* A fix in Martian where multiple grok.Model or grok.Container classes
- could result in something being found as a context twice.
-
-0.9 series (early 2007 until July 2007)
-=======================================
-
-Feature changes
----------------
-
-Grok was released in "continuous release" mode from SVN during this period.
-
-0.1 series (September 2006 until early 2007)
-============================================
-
-Feature changes
----------------
-
-Grok was created in September 2006.
Deleted: grok/trunk/COPYRIGHT.txt
===================================================================
--- grok/trunk/COPYRIGHT.txt 2013-03-01 14:56:57 UTC (rev 129943)
+++ grok/trunk/COPYRIGHT.txt 2013-03-01 15:40:59 UTC (rev 129944)
@@ -1 +0,0 @@
-Zope Foundation and Contributors
\ No newline at end of file
Deleted: grok/trunk/CREDITS.txt
===================================================================
--- grok/trunk/CREDITS.txt 2013-03-01 14:56:57 UTC (rev 129943)
+++ grok/trunk/CREDITS.txt 2013-03-01 15:40:59 UTC (rev 129944)
@@ -1,83 +0,0 @@
-CREDITS
-=======
-
-* Martijn Faassen (original developer)
-
-* Wolfgang Schnerring (original developer)
-
-* Christian Theune (original developer)
-
-* Philipp von Weitershausen (original developer)
-
-* Jan-Wijbrand Kolman (early developer (Grok Zwei sprint), release manager)
-
-* Uli Fouquet (admin interface, introspector, summer of code student)
-
-* Darryl Cousins (website, admin interface)
-
-* Kevin Teague (website, documentation)
-
-* Tim Terlegård (JSON support, viewlets, grokproject)
-
-* Maurits van Rees (grokproject, eggbasket)
-
-* Sebastian Ware (website effort, documentation)
-
-* Christian Zagrodnick (early grok discussions)
-
-* Mikhail Kashkin
-
-* Wim Boucqaert (admin interface layout improvements)
-
-* Kevin M. Smith (skins and layers support, viewlets)
-
-* Luciano Ramalho
-
-* Lennart Regebro (template pluggability)
-
-* Guido Wesdorp (template pluggability)
-
-* Brandon Rhodes (template pluggability, grokcore.component)
-
-* Godefroid Chapelle (conversion to Z3 configuration actions)
-
-* Souheil Chelfouh
-
-* Sylvain Viollon (work on martian, grokcore.formlib, grokcore.view,
- grokcore.viewlet)
-
-* Michael Haubenwallner (WSGI support, ZTK support)
-
-* Vincent Fretin
-
-* Reinout van Rees
-
-* Maurits van Rees
-
-* ME GROK (team mascot)
-
-Thank you
----------
-
-* The Zope 3 developers, who provided the mountain for Grok to stand
- on.
-
-* gocept for hosting the first grok sprint in Halle, Germany. Special
- thanks to Felicia Faassen Wong, Christian Zagrodnick and Magda
- Motyka for the delicious food.
-
-* Philipp von Weitershausen for hosting the second grok sprint in
- Dresden, Germany. Special thanks to Heinrich von Jagwitz for the
- delicious food.
-
-* The organizers of EuroPython 2007 in Vilnius for allowing us to host
- the third Grok sprint after EuroPython there.
-
-* ID StudioLab of the faculty of Industrial Design at the Delft
- University of Technology for sponsoring the development of REST
- support in Grok.
-
-* The Health Agency for hosting the "Grokkerdam sprint" in 2008.
-
-* GfU Cyrus in Cologne for generously hosting the "Neanderthal sprint" in
- 2007 and the "Neanderthal II sprint" in 2009.
Deleted: grok/trunk/INSTALL.txt
===================================================================
--- grok/trunk/INSTALL.txt 2013-03-01 14:56:57 UTC (rev 129943)
+++ grok/trunk/INSTALL.txt 2013-03-01 15:40:59 UTC (rev 129944)
@@ -1,86 +0,0 @@
-Developing grok
-===============
-
-Preparing for grok development
-------------------------------
-
-The Grok development sandbox is set up via `zc.buildout`_
-
-.. _zc.buildout: http://cheeseshop.python.org/pypi/zc.buildout
-
-You may have setuptools already installed for your system Python. In
-that case, you may need to upgrade it first because buildout requires
-a very recent version::
-
- $ sudo easy_install -U setuptools
-
-If this command fails because easy_install is not available, there is
-a good chance you do not have setuptools available for your system
-Python. If so, there is no problem because setuptools will be
-installed locally by buildout.
-
-Bootstrap the buildout environment::
-
- $ python bootstrap/bootstrap.py
-
-and run the buildout command::
-
- $ bin/buildout
- [lots of stuff will be downloaded and installed here]
-
-Note that if you have more than one sandbox for a Zope-based web
-application, it will probably make sense to share the eggs between the
-different sandboxes. You can tell zc.buildout to use a central eggs
-directory by creating ``~/.buildout/default.cfg`` with the following
-contents::
-
- [buildout]
- eggs-directory = /home/bruno/buildout-eggs
-
-Note, that this is the grok core package. If you want to develop Grok
-applications you might consider to use `grokproject
-<http://pypi.python.org/pypi/grokproject>`_ instead.
-
-
-Running the demo applications
------------------------------
-
-You can start Zope with the demo applications installed with the
-following command:
-
- $ bin/paster serve parts/etc/deploy.ini
-
-If you now connect to port 8080 and log in with username 'grok',
-password 'grok', you should be able to add the grok-based applications
-(such as grokwiki) from the menu.
-
-Running the tests
------------------
-
-Grok's tests are easily run by executing the test runner that's
-installed in the ``bin`` directory::
-
- $ bin/test
-
-Generating the website files
-----------------------------
-
-Grok's tutorial documents for the website can easily be generated
-using the following scripts in ``bin``::
-
- $ bin/grokdocs2html
-
-The output is by default written to ``build/html/``.
-
-Run::
-
- $ bin/grokdocs2html -h
-
-to get all options supported.
-
-With::
-
- $ bin/grokdocs2latex
-
-you get LaTeX output which can be used to generate PDF docs. This
-requires a working LaTeX installed on your system.
Deleted: grok/trunk/LICENSE.txt
===================================================================
--- grok/trunk/LICENSE.txt 2013-03-01 14:56:57 UTC (rev 129943)
+++ grok/trunk/LICENSE.txt 2013-03-01 15:40:59 UTC (rev 129944)
@@ -1,44 +0,0 @@
-Zope Public License (ZPL) Version 2.1
-
-A copyright notice accompanies this license document that identifies the
-copyright holders.
-
-This license has been certified as open source. It has also been designated as
-GPL compatible by the Free Software Foundation (FSF).
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-
-1. Redistributions in source code must retain the accompanying copyright
-notice, this list of conditions, and the following disclaimer.
-
-2. Redistributions in binary form must reproduce the accompanying copyright
-notice, this list of conditions, and the following disclaimer in the
-documentation and/or other materials provided with the distribution.
-
-3. Names of the copyright holders must not be used to endorse or promote
-products derived from this software without prior written permission from the
-copyright holders.
-
-4. The right to distribute this software or to use it for any purpose does not
-give you the right to use Servicemarks (sm) or Trademarks (tm) of the
-copyright
-holders. Use of them is covered by separate agreement with the copyright
-holders.
-
-5. If any files are modified, you must cause the modified files to carry
-prominent notices stating that you changed the files and the date of any
-change.
-
-Disclaimer
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ``AS IS'' AND ANY EXPRESSED
-OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
-EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY DIRECT, INDIRECT,
-INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
-PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
-EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Added: grok/trunk/MOVED_TO_GITHUB
===================================================================
--- grok/trunk/MOVED_TO_GITHUB (rev 0)
+++ grok/trunk/MOVED_TO_GITHUB 2013-03-01 15:40:59 UTC (rev 129944)
@@ -0,0 +1 @@
+See https://github.com/zopefoundation/grok
\ No newline at end of file
Deleted: grok/trunk/README.txt
===================================================================
--- grok/trunk/README.txt 2013-03-01 14:56:57 UTC (rev 129943)
+++ grok/trunk/README.txt 2013-03-01 15:40:59 UTC (rev 129944)
@@ -1,48 +0,0 @@
-Grok
-****
-
-What is grok?
-=============
-
-Grok is a smashing web framework based on `Zope Toolkit`_ technology.
-
-.. _`Zope Toolkit`: http://docs.zope.org/zopetoolkit
-
-Grok uses the Component Architecture and builds on Zope concepts like
-content objects (models), views, and adapters. Its simplicity lies in
-using **convention over configuration** and **sensible defaults** when
-wiring components together. That means neither a configuration
-language like ZCML nor a lot of repetition are needed to create a web
-application with grok.
-
-You can find out much more about Grok at our http://grok.zope.org
-website.
-
-Who is grok?
-============
-
-Grok is a friendly caveman from the Stone Age. He has a big club that
-he hunts mammoths with. He will also use this club to smash anything
-he doesn't like.
-
-"ME GROK SMASH ZCML!"
-
-Getting grok
-============
-
-The easiest way to get started with grok is to install the
-`grokproject <http://cheeseshop.python.org/pypi/grokproject>`_ package
-(e.g. via ``easy_install grokproject``) and then create a new project
-area by calling the ``grokproject`` script like so::
-
- $ grokproject MyProject
- ... many lines of output here
-
-This will create a project area in ``MyProject`` as well as download
-and install grok.
-
-You can also get grok from the subversion repository::
-
- svn co svn://svn.zope.org/repos/main/grok/trunk grok
-
-Then follow the instructions of ``INSTALL.txt``.
Deleted: grok/trunk/TODO.txt
===================================================================
--- grok/trunk/TODO.txt 2013-03-01 14:56:57 UTC (rev 129943)
+++ grok/trunk/TODO.txt 2013-03-01 15:40:59 UTC (rev 129944)
@@ -1,121 +0,0 @@
-====
-TODO
-====
-
-Meta
-====
-
-- Check demo applications for issues with patterns (grok wiki, ldap address
- book)
-
-
-Core
-====
-
-- choice fields / sources (theuni)
-
-- testing strategy for the tutorial (faassen)
-
-- make it easier to write tests (wosc, faassen)
-
-- error reporting during grokking (provide file/line-number information
- on our extrinsically generated errors) (philikon)
-
-- What will happen if we make a utility a old style class and use the
- MRO stuff. Since we don't support non-persistent local utilities yet this
- may be a rare case.
-
-- What about local utilities that don't subclass persistent? Perhaps we
- can look for IPersistent and give an error if the utility doesn't
- state it is.
-
-- Change error messages: whenever we report about a callable, add
- () to the name. Core Python expections do this.
-
-- JSON support similar to XMLRPC.
-
-
-Schema/formlib support
-----------------------
-
-- support nested class 'fields' directly on a view (do we really want this?)
-
-- list form for grok.Container (w/ zc.table?)
-
-- delete action on list form
-
-- make formlib macros available in some form?
-
-- what about subclassing a model that has a 'fields'?
-
-
-Need to discuss
----------------
-
-- Do we want to ship Grok with a javascript library dependency such as
- MochiKit, to enable out of-the-box AJAX?
-
-- Make it even easier to set up the catalog (intids should be set up
- automatically if not already present. Perhaps Index grokkers?).
-
-- Testing support. Test grokkers?
-
-- Error pages: make it easy to register application-specific error
- pages for exceptions.
-
-- Easier queries: integrate hurry.query in some way?
-
-- fall back to a static resource that is defined in a package on a higher
- level if no static resource directory is defined locally in a package?
-
-- grok.grokkable (to allow grokking of imported things)
-
-- skins
-
-- form redirect
-
-- authentication (pau integration) (faassen)
-
-- sessions (get the session information for something, similar to
- annotations?)
-
-- menus - define a menu, associate a view with a menu (module-level,
- class-level)
-
-- making new widgets (faassen, philikon)
-
-- IMPORTANT: different strategies: grok.definefoo() versus n =
- grok.Foo(), watch out for consistency/symmetry/...
-
-- use ZCML's conflict resolution machinery; actions for Grok.
-
-- do not accept automatic template directory guessing convention for
- __init__.py, bail out with grok error instead?
-
-- grok.name, grok.template class restrictions (e.g. grok.template
- should only be usable from grok.View subclasses)
-
-- support grok.template(template) in addition to
- grok.template('name_of_template')?
-
-- support grok.resource on view class level?
-
-- should grok.context and grok.Model be order-dependent?
- (so their meaning becomes "below here, this is the context")
-
-- Do we want to initialize model attributes for any schema that the model
- implements (in addition to the initialization that is taking place for the
- model-level fields)?
-
-
-Punt
-----
-
-- making new fields
-
-- viewlets / content providers (LATER)
-
-- RDB - via extension: megrok.sqlalchemy for example - make it easy to
- go between the different schema implementations
-
-- containment constraints (wait for zope 3 to do them right)
Deleted: grok/trunk/bootstrap.py
===================================================================
--- grok/trunk/bootstrap.py 2013-03-01 14:56:57 UTC (rev 129943)
+++ grok/trunk/bootstrap.py 2013-03-01 15:40:59 UTC (rev 129944)
@@ -1,260 +0,0 @@
-##############################################################################
-#
-# Copyright (c) 2006 Zope Foundation and Contributors.
-# All Rights Reserved.
-#
-# This software is subject to the provisions of the Zope Public License,
-# Version 2.1 (ZPL). A copy of the ZPL should accompany this distribution.
-# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY AND ALL EXPRESS OR IMPLIED
-# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS
-# FOR A PARTICULAR PURPOSE.
-#
-##############################################################################
-"""Bootstrap a buildout-based project
-
-Simply run this script in a directory containing a buildout.cfg.
-The script accepts buildout command-line options, so you can
-use the -c option to specify an alternate configuration file.
-"""
-
-import os, shutil, sys, tempfile, textwrap, urllib, urllib2, subprocess
-from optparse import OptionParser
-
-if sys.platform == 'win32':
- def quote(c):
- if ' ' in c:
- return '"%s"' % c # work around spawn lamosity on windows
- else:
- return c
-else:
- quote = str
-
-# See zc.buildout.easy_install._has_broken_dash_S for motivation and comments.
-stdout, stderr = subprocess.Popen(
- [sys.executable, '-Sc',
- 'try:\n'
- ' import ConfigParser\n'
- 'except ImportError:\n'
- ' print 1\n'
- 'else:\n'
- ' print 0\n'],
- stdout=subprocess.PIPE, stderr=subprocess.PIPE).communicate()
-has_broken_dash_S = bool(int(stdout.strip()))
-
-# In order to be more robust in the face of system Pythons, we want to
-# run without site-packages loaded. This is somewhat tricky, in
-# particular because Python 2.6's distutils imports site, so starting
-# with the -S flag is not sufficient. However, we'll start with that:
-if not has_broken_dash_S and 'site' in sys.modules:
- # We will restart with python -S.
- args = sys.argv[:]
- args[0:0] = [sys.executable, '-S']
- args = map(quote, args)
- os.execv(sys.executable, args)
-# Now we are running with -S. We'll get the clean sys.path, import site
-# because distutils will do it later, and then reset the path and clean
-# out any namespace packages from site-packages that might have been
-# loaded by .pth files.
-clean_path = sys.path[:]
-import site
-sys.path[:] = clean_path
-for k, v in sys.modules.items():
- if k in ('setuptools', 'pkg_resources') or (
- hasattr(v, '__path__') and
- len(v.__path__)==1 and
- not os.path.exists(os.path.join(v.__path__[0],'__init__.py'))):
- # This is a namespace package. Remove it.
- sys.modules.pop(k)
-
-is_jython = sys.platform.startswith('java')
-
-setuptools_source = 'http://peak.telecommunity.com/dist/ez_setup.py'
-distribute_source = 'http://python-distribute.org/distribute_setup.py'
-
-# parsing arguments
-def normalize_to_url(option, opt_str, value, parser):
- if value:
- if '://' not in value: # It doesn't smell like a URL.
- value = 'file://%s' % (
- urllib.pathname2url(
- os.path.abspath(os.path.expanduser(value))),)
- if opt_str == '--download-base' and not value.endswith('/'):
- # Download base needs a trailing slash to make the world happy.
- value += '/'
- else:
- value = None
- name = opt_str[2:].replace('-', '_')
- setattr(parser.values, name, value)
-
-usage = '''\
-[DESIRED PYTHON FOR BUILDOUT] bootstrap.py [options]
-
-Bootstraps a buildout-based project.
-
-Simply run this script in a directory containing a buildout.cfg, using the
-Python that you want bin/buildout to use.
-
-Note that by using --setup-source and --download-base to point to
-local resources, you can keep this script from going over the network.
-'''
-
-parser = OptionParser(usage=usage)
-parser.add_option("-v", "--version", dest="version",
- help="use a specific zc.buildout version")
-parser.add_option("-d", "--distribute",
- action="store_true", dest="use_distribute", default=False,
- help="Use Distribute rather than Setuptools.")
-parser.add_option("--setup-source", action="callback", dest="setup_source",
- callback=normalize_to_url, nargs=1, type="string",
- help=("Specify a URL or file location for the setup file. "
- "If you use Setuptools, this will default to " +
- setuptools_source + "; if you use Distribute, this "
- "will default to " + distribute_source +"."))
-parser.add_option("--download-base", action="callback", dest="download_base",
- callback=normalize_to_url, nargs=1, type="string",
- help=("Specify a URL or directory for downloading "
- "zc.buildout and either Setuptools or Distribute. "
- "Defaults to PyPI."))
-parser.add_option("--eggs",
- help=("Specify a directory for storing eggs. Defaults to "
- "a temporary directory that is deleted when the "
- "bootstrap script completes."))
-parser.add_option("-t", "--accept-buildout-test-releases",
- dest='accept_buildout_test_releases',
- action="store_true", default=False,
- help=("Normally, if you do not specify a --version, the "
- "bootstrap script and buildout gets the newest "
- "*final* versions of zc.buildout and its recipes and "
- "extensions for you. If you use this flag, "
- "bootstrap and buildout will get the newest releases "
- "even if they are alphas or betas."))
-parser.add_option("-c", None, action="store", dest="config_file",
- help=("Specify the path to the buildout configuration "
- "file to be used."))
-
-options, args = parser.parse_args()
-
-# if -c was provided, we push it back into args for buildout's main function
-if options.config_file is not None:
- args += ['-c', options.config_file]
-
-if options.eggs:
- eggs_dir = os.path.abspath(os.path.expanduser(options.eggs))
-else:
- eggs_dir = tempfile.mkdtemp()
-
-if options.setup_source is None:
- if options.use_distribute:
- options.setup_source = distribute_source
- else:
- options.setup_source = setuptools_source
-
-if options.accept_buildout_test_releases:
- args.append('buildout:accept-buildout-test-releases=true')
-args.append('bootstrap')
-
-try:
- import pkg_resources
- import setuptools # A flag. Sometimes pkg_resources is installed alone.
- if not hasattr(pkg_resources, '_distribute'):
- raise ImportError
-except ImportError:
- ez_code = urllib2.urlopen(
- options.setup_source).read().replace('\r\n', '\n')
- ez = {}
- exec ez_code in ez
- setup_args = dict(to_dir=eggs_dir, download_delay=0)
- if options.download_base:
- setup_args['download_base'] = options.download_base
- if options.use_distribute:
- setup_args['no_fake'] = True
- ez['use_setuptools'](**setup_args)
- if 'pkg_resources' in sys.modules:
- reload(sys.modules['pkg_resources'])
- import pkg_resources
- # This does not (always?) update the default working set. We will
- # do it.
- for path in sys.path:
- if path not in pkg_resources.working_set.entries:
- pkg_resources.working_set.add_entry(path)
-
-cmd = [quote(sys.executable),
- '-c',
- quote('from setuptools.command.easy_install import main; main()'),
- '-mqNxd',
- quote(eggs_dir)]
-
-if not has_broken_dash_S:
- cmd.insert(1, '-S')
-
-find_links = options.download_base
-if not find_links:
- find_links = os.environ.get('bootstrap-testing-find-links')
-if find_links:
- cmd.extend(['-f', quote(find_links)])
-
-if options.use_distribute:
- setup_requirement = 'distribute'
-else:
- setup_requirement = 'setuptools'
-ws = pkg_resources.working_set
-setup_requirement_path = ws.find(
- pkg_resources.Requirement.parse(setup_requirement)).location
-env = dict(
- os.environ,
- PYTHONPATH=setup_requirement_path)
-
-requirement = 'zc.buildout'
-version = options.version
-if version is None and not options.accept_buildout_test_releases:
- # Figure out the most recent final version of zc.buildout.
- import setuptools.package_index
- _final_parts = '*final-', '*final'
- def _final_version(parsed_version):
- for part in parsed_version:
- if (part[:1] == '*') and (part not in _final_parts):
- return False
- return True
- index = setuptools.package_index.PackageIndex(
- search_path=[setup_requirement_path])
- if find_links:
- index.add_find_links((find_links,))
- req = pkg_resources.Requirement.parse(requirement)
- if index.obtain(req) is not None:
- best = []
- bestv = None
- for dist in index[req.project_name]:
- distv = dist.parsed_version
- if _final_version(distv):
- if bestv is None or distv > bestv:
- best = [dist]
- bestv = distv
- elif distv == bestv:
- best.append(dist)
- if best:
- best.sort()
- version = best[-1].version
-if version:
- requirement = '=='.join((requirement, version))
-cmd.append(requirement)
-
-if is_jython:
- import subprocess
- exitcode = subprocess.Popen(cmd, env=env).wait()
-else: # Windows prefers this, apparently; otherwise we would prefer subprocess
- exitcode = os.spawnle(*([os.P_WAIT, sys.executable] + cmd + [env]))
-if exitcode != 0:
- sys.stdout.flush()
- sys.stderr.flush()
- print ("An error occurred when trying to install zc.buildout. "
- "Look above this message for any errors that "
- "were output by easy_install.")
- sys.exit(exitcode)
-
-ws.add_entry(eggs_dir)
-ws.require(requirement)
-import zc.buildout.buildout
-zc.buildout.buildout.main(args)
-if not options.eggs: # clean up temporary egg directory
- shutil.rmtree(eggs_dir)
Deleted: grok/trunk/buildout.cfg
===================================================================
--- grok/trunk/buildout.cfg 2013-03-01 14:56:57 UTC (rev 129943)
+++ grok/trunk/buildout.cfg 2013-03-01 15:40:59 UTC (rev 129944)
@@ -1,68 +0,0 @@
-[buildout]
-extends = http://svn.zope.org/repos/main/groktoolkit/trunk/grok.cfg
-parts =
- interpreter
- mkdirs
- test
- zope_conf site_zcml deploy_ini debug_ini
- zpasswd
-develop =
- .
- grokwiki
-versions = versions
-extensions =
- buildout.dumppickedversions
- mr.developer
-
-[versions]
-grok =
-
-[interpreter]
-recipe = z3c.recipe.scripts
-eggs =
- grokwiki
- zest.releaser
-interpreter = grokpy
-
-[mkdirs]
-recipe = z3c.recipe.mkdir
-paths =
- ${zope_conf:filestorage}
- ${zope_conf:logfiles}
-
-[test]
-recipe = zc.recipe.testrunner
-eggs =
- grok
- grok[test]
-defaults = ['--tests-pattern', '^f?tests$', '-v', '--auto-color']
-
-[zope_conf]
-recipe = z3c.recipe.template
-input = etc/zope.conf.in
-output = ${buildout:parts-directory}/etc/zope.conf
-filestorage = ${buildout:directory}/var/filestorage
-logfiles = ${buildout:directory}/var/log
-
-[site_zcml]
-recipe = z3c.recipe.template
-input = etc/site.zcml.in
-output = ${buildout:parts-directory}/etc/site.zcml
-
-[deploy_ini]
-recipe = z3c.recipe.template
-input = etc/deploy.ini.in
-output = ${buildout:parts-directory}/etc/deploy.ini
-
-[debug_ini]
-recipe = z3c.recipe.template
-input = etc/debug.ini.in
-output = ${buildout:parts-directory}/etc/debug.ini
-
-# This section is named so that the zpasswd utility is
-# called `zpasswd`
-[zpasswd]
-recipe = z3c.recipe.dev:script
-eggs = grokwiki
-module = zope.app.server.zpasswd
-method = main
Deleted: grok/trunk/documentation.cfg
===================================================================
--- grok/trunk/documentation.cfg 2013-03-01 14:56:57 UTC (rev 129943)
+++ grok/trunk/documentation.cfg 2013-03-01 15:40:59 UTC (rev 129944)
@@ -1,17 +0,0 @@
-[buildout]
-extends = buildout.cfg
-develop = .
-parts =
- sphinxpython
- generate_documentation
-
-[sphinxpython]
-recipe = z3c.recipe.scripts
-interpreter = sphinxpython
-eggs = grok
-
-[generate_documentation]
-recipe = collective.recipe.sphinxbuilder
-source = ${buildout:directory}/doc
-build = ${buildout:directory}/doc/_build
-interpreter = ${buildout:bin-directory}/sphinxpython
Deleted: grok/trunk/grokwiki.cfg
===================================================================
--- grok/trunk/grokwiki.cfg 2013-03-01 14:56:57 UTC (rev 129943)
+++ grok/trunk/grokwiki.cfg 2013-03-01 15:40:59 UTC (rev 129944)
@@ -1,20 +0,0 @@
-[buildout]
-extends = http://svn.zope.org/repos/main/groktoolkit/trunk/grok.cfg
-parts = grokwiki
-develop =
- .
- grokwiki
-versions = versions
-extensions = buildout.dumppickedversions
-
-[versions]
-grok =
-
-[grokwiki]
-recipe = z3c.recipe.scripts
-eggs =
- grokwiki
- Paste
- PasteDeploy
- PasteScript
- z3c.evalexception>=2.0
Deleted: grok/trunk/setup.py
===================================================================
--- grok/trunk/setup.py 2013-03-01 14:56:57 UTC (rev 129943)
+++ grok/trunk/setup.py 2013-03-01 15:40:59 UTC (rev 129944)
@@ -1,99 +0,0 @@
-from setuptools import setup, find_packages
-import os
-
-def read(*rnames):
- return open(os.path.join(os.path.dirname(__file__), *rnames)).read()
-
-long_description = (
- read('README.txt')
- + '\n' +
- read('CHANGES.txt')
- + '\n' +
- 'Download\n'
- '********\n'
- )
-
-tests_require = [
- 'zope.app.wsgi',
- 'zope.configuration',
- 'zope.testing',
- ]
-
-setup(
- name='grok',
- version='1.10.4.dev0',
- author='Grok Team',
- author_email='grok-dev at zope.org',
- url='http://grok.zope.org',
- download_url='http://cheeseshop.python.org/pypi/grok/',
- description='Grok: Now even cavemen can use Zope 3!',
- long_description=long_description,
- license='ZPL',
- classifiers=[
- 'Environment :: Web Environment',
- 'Intended Audience :: Developers',
- 'License :: OSI Approved :: Zope Public License',
- 'Programming Language :: Python',
- 'Framework :: Zope3',
- ],
- packages=find_packages('src'),
- package_dir = {'': 'src'},
- include_package_data = True,
- zip_safe=False,
- install_requires=[
- 'grokcore.annotation >= 1.1',
- 'grokcore.catalog',
- 'grokcore.chameleon >= 1.0',
- 'grokcore.component >= 2.5',
- 'grokcore.content >= 1.1',
- 'grokcore.formlib >= 1.4',
- 'grokcore.json >= 1.2',
- 'grokcore.layout >= 1.6',
- 'grokcore.message',
- 'grokcore.rest >= 1.3',
- 'grokcore.security[role] >= 1.6',
- 'grokcore.site >= 1.6.1',
- 'grokcore.traverser >= 1.1',
- 'grokcore.view >= 2.7',
- 'grokcore.viewlet >= 1.10',
- 'grokcore.view [security_publication]',
- 'grokcore.xmlrpc >= 1.2',
- 'martian >= 0.14',
- 'pytz',
- 'setuptools',
- 'simplejson',
- 'z3c.autoinclude',
- 'zc.catalog',
- 'ZODB3',
- 'zope.annotation',
- 'zope.app.appsetup',
- 'zope.app.publication',
- 'zope.app.wsgi',
- 'zope.browserpage',
- 'zope.catalog',
- 'zope.component',
- 'zope.container',
- 'zope.contentprovider',
- 'zope.errorview [browser]',
- 'zope.event',
- 'zope.exceptions',
- 'zope.i18n',
- 'zope.i18nmessageid',
- 'zope.interface',
- 'zope.intid',
- 'zope.keyreference',
- 'zope.lifecycleevent',
- 'zope.location',
- 'zope.login',
- 'zope.password',
- 'zope.principalregistry',
- 'zope.publisher',
- 'zope.schema',
- 'zope.security',
- 'zope.securitypolicy',
- 'zope.site',
- 'zope.traversing',
- ],
- tests_require=tests_require,
- extras_require={'test': tests_require},
-)
More information about the checkins
mailing list