Skip to content

Conversation

@drfho
Copy link
Contributor

@drfho drfho commented Jan 20, 2026

Image Ref: https://github.com//pull/436

Zope uses native namespace

Zope replaces pkg_resources namespace with PEP 420 native namespace and thus with pip ≥ 21.3 and setuptools ≥ 64.0.0. Zope could find (for the editable-mode) the init-pathes for ZMS only if some backwards-compatibity flags are set in pip installation:

pip install --use-pep517 --config-settings editable_mode=compat -e git+https://github.com/zms-publishing/ZMS.git@main#egg=ZMS`

see: 955d8ba

ZMS installation fitted to new requirements

Now two measure are accomplished to make ZMS run with Zope6:

  1. the ZMS-code is reorganised:
./Products/zms
==>
./src/Products/zms
  1. the setup.py-file is replaced by the pyproject.toml-file

Important Note: ZMS6 needs to be installed for registering the new code-paths (you cannot just git-pull the ZMS6-code over an existing ZMS5 installation.
For installing the branch in editable mode use:

pip install -e git+https://github.com/zms-publishing/ZMS.git@zms6#egg=ZMS 

Copy link
Contributor Author

@drfho drfho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This gitignore allows to use a symlink ln -s src/Products Products for branch-switching between zms6 and main-branch in a primariliy PEP517/setup.py-based installation

@drfho drfho self-assigned this Jan 20, 2026
@drfho drfho requested review from cmeier76 and zmsdev January 20, 2026 17:53
@drfho drfho marked this pull request as draft January 20, 2026 17:53
Copy link
Contributor

@zmsdev zmsdev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@cmeier76
Copy link
Member

cmeier76 commented Jan 21, 2026

Local smoke testing of ZMS6 with new src-layout

  • Python-3.14.2 + Zope-6.0b2 ✅ -> next major runtime versions work
  • Python-3.13.5 + Zope-5.13 ✅ -> current runtime versions keep working

-> straightforward development by merging to main branch may work @drfho
-> we will double check with our target environments in February @OscarMeier

Refs

drfho added a commit that referenced this pull request Jan 21, 2026
@drfho drfho mentioned this pull request Jan 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants