2016-11-11 5:20 GMT-06:00 Hanno Schlichting <hanno@hannosch.eu>:
On Thu, Nov 10, 2016, at 09:12, Michael Howitz wrote:
You are right, it might look strange to have a Zope2 version 4.x. But renaming the Package on PyPI would cause problems for all packages which depend on Zope 4.x, especially for the ones which are even compatible with Zope 2.x and 4.x.
I agree that having the project/distribution name as Zope2 and the version as 4.x, 5.x, etc. isn't ideal.
But by now there are probably hundreds of other projects, which depend on Zope2 in their setup.py. Not to mention all kinds of buildout files, testing configurations or tools, the configuration for sites like https://zope3.pov.lt/py3/ and many other things we don't know about.
@Hanno: What do you think about renaming the PyPI package to Zope?
I think this is a cosmetic change, which at this point causes too much work and breakage for very little gain.
Hanno
And why not start a new package call "zope" (in PyPi) that it's really version 4. it's alpha version so no many projects are using it. -- ________________________________________ Lo bueno de vivir un dia mas es saber que nos queda un dia menos de vida
Am 11.11.2016 um 19:42 schrieb Miguel Beltran R. <yourpadre@gmail.com>:
And why not start a new package call "zope" (in PyPi) that it's really version 4. it's alpha version so no many projects are using it.
As mentioned earlier in this thread: This would it make nearly impossible to support both Zope 2.x and Zope 4.x in a single release of a third party package using Zope. Requiring separate releases for Zope 2 and Zope 4 is painful enough for the Zope core itself. Requiring this for the whole ecosystem would decrease the chance of Zope 4 to be used at all. -- Mit freundlichen Grüßen Michael Howitz
participants (2)
-
Michael Howitz -
Miguel Beltran R.