Metadata-Version: 1.1
Name: Products.GenericSetup
Version: 1.8.3
Summary: Read Zope configuration state from profile dirs / tarballs
Home-page: https://pypi.python.org/pypi/Products.GenericSetup
Author: Zope Foundation and Contributors
Author-email: zope-cmf@zope.org
License: ZPL 2.1 (http://www.zope.org/Resources/License/ZPL-2.1)
Description: ``Products.GenericSetup``
        =========================
        
        .. image:: https://travis-ci.org/zopefoundation/Products.GenericSetup.png?branch=master
                :target: https://travis-ci.org/zopefoundation/Products.GenericSetup
        
        This product provides a mini-framework for expressing the configured
        state of a Zope Site as a set of filesystem artifacts.  These artifacts
        consist of declarative XML files, which spell out the configuration
        settings for each "tool" in the site , and supporting scripts / templates,
        in their "canonical" filesystem representations.
        
        See ``docs/index.rst`` for full documentation.  This documentation can
        also be found online:  http://packages.python.org/Products.GenericSetup/
        
        ------------------------------------------------------------
        
        Changelog
        =========
        
        1.8.3 (2016-04-28)
        ------------------
        
        - Allowed overriding required and forbidden tools in ``toolset.xml``.
          If a tool is currently required and you import a ``toolset.xml``
          where it is forbidden, we remove the tool from the required list and
          add it to the forbidden list.  And the other way around.  The
          previous behavior was to raise an exception, which left no way in
          xml to remove a tool.  Fail with a ValueError when the ``remove``
          keyword is used.  The expected behavior is unclear.  [maurits]
        
        
        1.8.2 (2016-02-24)
        ------------------
        
        - Added optional ``pre_handler`` and ``post_handler`` to
          ``registerProfile`` directive.  When set, these dotted names are
          resolved to a function and are passed the setup tool as single
          argument.  They are called before and after applying all import
          steps of the profile they are registered for.  [maurits]
        
        - Sorted import profiles alphabetically lowercase.  Allow selecting a
          profile by title or id.  [maurits]
        
        - Do not show dependency options on the full import tab when there are
          no dependencies.  [maurits]
        
        - Do not select a profile by default in the import tabs.  [maurits]
        
        - Added simple toggle for all steps on the advanced import tab.
          Also added this on the export tab.
          [maurits]
        
        - Fixed importing a tarball.  This got an AttributeError: "'NoneType'
          object has no attribute 'startswith'".
          [maurits]
        
        - Split overly complex Import tab into three tabs: Import (for
          importing a full profile), Advanced Import (the original
          ``manage_importSteps`` url leads to this tab), and Tarball Import.
          [maurits]
        
        - Show note on import tab when there are pending upgrades.  Especially
          show this for the currently selected profile.
          [maurits]
        
        - Upgrades tab: show profiles with pending upgrades separately.  These
          are the most important ones.  This avoids the need to manually go
          through the whole list in order to find profiles that may need
          action.  This uses new methods on the setup tool:
          ``hasPendingUpgrades``, ``listProfilesWithPendingUpgrades``,
          ``listUptodateProfiles``.
          [maurits]
        
        
        1.8.1 (2015-12-16)
        ------------------
        
        - Purge the profile upgrade versions before applying a base profile.
        
        - Added ``purgeProfileVersions`` method to ``portal_setup``.  This
          removes the all profiles profile upgrade versions.
        
        - Added ``unsetLastVersionForProfile`` method to ``portal_setup``.  This
          removes the profile id from the profile upgrade versions.  Calling
          ``setLastVersionForProfile`` with ``unknown`` as version now has the
          same effect.
        
        
        1.8.0 (2015-09-21)
        ------------------
        
        - Be more forgiving when dealing with profile ids with or without
          ``profile-`` at the start.  All functions that accept a profile id
          argument and only work when the id does *not* have this string at
          the start, will now strip it off if it is there.  For example,
          ``getLastVersionForProfile`` will give the same answer whether you
          ask it for the version of profile id ``foo`` or ``profile-foo``.
        
        - Dependency profiles from ``metadata.xml`` that are already applied,
          are not applied again.  Instead, its upgrade steps, if any, are
          applied.  In code you can choose the old behavior of always applying
          the dependencies, by calling ``runAllImportStepsFromProfile`` with
          ``dependency_strategy=DEPENDENCY_STRATEGY_REAPPLY``.  There are four
          strategies, which you can choose in the ZMI.
        
        
        1.7.7 (2015-08-11)
        ------------------
        
        - Fix: when the last applied upgrade step had a checker, the profile
          version was not updated.  Now we no longer look at the checker of
          the last applied step when deciding whether to set the profile
          version.  The checker, if any is set, normally returns True before
          running the step (it can be applied), and False afterwards (it
          was already applied).
        
        - Add ``upgradeProfile`` method to setup tool.  This method applies all
          upgrades steps for the given profile, or updates it to the optional
          given version.  If the profile does not exist, or if there is no upgrade
          step to go to the specified version, the method warns and does nothing.
        
        - Check the boolean value of the ``remove`` option when importing
          objects.  Previously we only checked if the ``remove`` option was
          given, regardless of its value.  Supported are ``True``, ``Yes``,
          and ``1``, where case does not matter.  The syntax for removing
          objects, properties, and elements is now the same.
        
        - Support ``remove="True"`` for properties.
        
        
        1.7.6 (2015-07-15)
        ------------------
        
        - Enable testing under Travis.
        
        - Fix compatibility with Setuptools 8.0 and later.  Upgrade steps
          could get sorted in the wrong order, especially an empty version
          string (upgrade step from any source version) sorted last instead of
          first.
        
        
        1.7.5 (2014-10-23)
        ------------------
        
        - Allow skipping certain steps on ``runAllImportStepsFromProfile``.
        
        
        1.7.4 (2013-06-12)
        ------------------
        
        - On import, avoid clearing indexes whose state is unchanged.
        
        
        1.7.3 (2012-10-16)
        ------------------
        
        - Sort profiles on Upgrade form.
        
        - Use clickable labels with checkboxes on import, export and upgrade forms
          to improve usability.
        
        
        1.7.2 (2012-07-23)
        ------------------
        
        - Avoid using ``manage_FTPGet`` on snapshot exports: that method messes
          up the response headers.
        
        - ZopePageTemplate handler:  Fix export encoding: since 1.7.0, exports
          must be UTF-8 strings
        
        
        1.7.1 (2012-02-28)
        ------------------
        
        - Restore the ability to make the setup tool use only import / export
          steps explicitly called out by the current profile, ignoring any which
          might be globally registered.  This is particularly useful for configuring
          sites with baseline profiles, where arbitrary add-on steps are not only
          useless, but potentially damaging.
        
        
        1.7.0 (2012-01-27)
        ------------------
        
        - While importing ``toolset.xml``, print a warning when the class of a
          required tool is not found and continue with the next tool.  The
          previous behaviour could break the install or uninstall of any
          add-on, as the missing class may easily be from a different
          unrelated add-on that is no longer available in the zope instance.
        
        - Exporters now explicitly only understand strings. The provided
          registry handlers encode and decode data automatically to and from
          UTF-8. Their default encoding changed from None to UTF-8.
          If you have custom registry handlers, ensure that you encode your unicode.
          Check especially if you use a page template to generate xml. They return
          unicode and their output must also encoded.
          If you choose to encode your strings with UTF-8, you can be sure that
          your code will also work with GenericSetup < 1.7
        
Keywords: web application server zope zope2 cmf
Platform: UNKNOWN
Classifier: Development Status :: 5 - Production/Stable
Classifier: Framework :: Plone
Classifier: Framework :: Plone :: 4.3
Classifier: Framework :: Plone :: 5.0
Classifier: Framework :: Zope2
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: Zope Public License
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 2.6
Classifier: Programming Language :: Python :: 2.7
Classifier: Topic :: Software Development
Classifier: Topic :: System :: Archiving :: Packaging
Classifier: Topic :: System :: Installation/Setup
