From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-May/015924.html | 85 +++++++++++++++++++++++++++++++++ 1 file changed, 85 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-May/015924.html (limited to 'zarb-ml/mageia-dev/2012-May/015924.html') diff --git a/zarb-ml/mageia-dev/2012-May/015924.html b/zarb-ml/mageia-dev/2012-May/015924.html new file mode 100644 index 000000000..8ecfb1f58 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-May/015924.html @@ -0,0 +1,85 @@ + + + + [Mageia-dev] Pyro update + + + + + + + + + +

[Mageia-dev] Pyro update

+ Oliver Burger + oliver.bgr at googlemail.com +
+ Tue May 29 14:56:51 CEST 2012 +

+
+ +
Hi there,
+
+I notice we have pyro 3.10 in the repositories. By now, according to the 
+projects homepage at http://packages.python.org/Pyro4/intro.html pyro 
+4.x (which is a reimplementation) can be considered as the main branch 
+of the project.
+So what to do? Both versions of pyro are not api compatible, so just 
+updating pyro 3.x to pyro 4.x might crush someone's applications.
+So should we import pyro 4.x as a versioned package and keep pyro 3.x as 
+it is or should we rename pyro 3.x to pyro3 and import pyro 4.x as pyro?
+I would prefer the first way, since upstream choose to call the newer 
+version pyro4 instead of pyro.
+
+Oliver
+
+-- 
+Oliver Burger aka obgr_seneca
+
+Mageia contributor
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1