Products-genericsetup

Latest version: v2.1.4

Safety actively analyzes 628918 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 5 of 6

1.8.2

Not secure
------------------

- 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

Not secure
------------------

- 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

Not secure
------------------

- 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

Not secure
------------------

- 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

Not secure
------------------

- 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

Not secure
------------------

- Allow skipping certain steps on ``runAllImportStepsFromProfile``.

Page 5 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.