PEPS, version control, release intervals
A more critical issue might be why people haven't adopted 2.0 yet; there seems little reason is there to continue using 1.5.2, yet I still see questions on the XML-SIG, for example, from people who haven't upgraded. Is it that Zope doesn't support it? Or that Red Hat and Debian don't include it?
Availability of Linux binaries is certainly an issue. On xml-sig, one
Linux distributor (I forgot whether SuSE or Redhat) mentioned that
they won't include 2.0 in their current major release series (7.x for
both).
Furthermore, the available 2.0 binaries won't work for either Redhat
7.0 nor SuSE 7.0; I think collecting binaries as we did for earlier
releases is an important activity that was forgotten during 2.0.
In addition, many packages are still not available for 2.0. Zope is
only one of them; gtk, Qt, etc packages are still struggling with
Unicode support. omniORBpy has #include
"Martin v. Loewis" wrote:
A more critical issue might be why people haven't adopted 2.0 yet; there seems little reason is there to continue using 1.5.2, yet I still see questions on the XML-SIG, for example, from people who haven't upgraded. Is it that Zope doesn't support it? Or that Red Hat and Debian don't include it?
Availability of Linux binaries is certainly an issue. On xml-sig, one Linux distributor (I forgot whether SuSE or Redhat) mentioned that they won't include 2.0 in their current major release series (7.x for both).
Furthermore, the available 2.0 binaries won't work for either Redhat 7.0 nor SuSE 7.0; I think collecting binaries as we did for earlier releases is an important activity that was forgotten during 2.0.
In addition, many packages are still not available for 2.0. Zope is only one of them; gtk, Qt, etc packages are still struggling with Unicode support. omniORBpy has #include
in their sources, ILU does not compile on 2.0 (due to wrong tests involving the PY_MAJOR/MINOR roll-over), Fnorb falls into the select.bind parameter change pitfall. This list probably could be continued - I'm sure many of the maintainers of these packages would appreciate a helping hand from some Python Guru.
Does this mean that doing CORBA et al. with Python 2.0 is currently not possible ? I will have a need for this starting this summer (along with SOAP and XML), so I'd be willing to help out. Who should I contact ? -- Marc-Andre Lemburg ______________________________________________________________________ Company: http://www.egenix.com/ Consulting: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/
Does this mean that doing CORBA et al. with Python 2.0 is currently not possible ?
It is possible; people have posted patches to Fnorb (which only add tuples in the right places). Also, the omniORB CVS cooperates with Python 2.0. There just is nothing that's officially released.
I will have a need for this starting this summer (along with SOAP and XML), so I'd be willing to help out. Who should I contact ?
Depends on what you want to take as a starting point. For Fnorb, it would be DSTC, although it appears to be "officially unmaintained" for the moment. For omniORB, contact Duncan Grisby - he's usually quite responsive. For ILU, it would be Bill Janssen; I'm sure he'll accept patches. If you need something in a commercial environment (i.e. where purchasing licenses is not an issue), feel free to contact me in private :-) In general, the DO SIG (do-sig@python.org) is a good place to discuss both CORBA and SOAP. Regards, Martin
"Martin v. Loewis" wrote:
Does this mean that doing CORBA et al. with Python 2.0 is currently not possible ?
It is possible; people have posted patches to Fnorb (which only add tuples in the right places). Also, the omniORB CVS cooperates with Python 2.0. There just is nothing that's officially released.
Looks like this is another issue with the current pace at which Python releases appear. I am starting to get these problems too with my mx tools: people download the wrong version and then find that the tools don't work with their installed version of Python (on Windows that is). Luckily, distutils makes this easier to handle, but many of the tools out there still don't use it.
I will have a need for this starting this summer (along with SOAP and XML), so I'd be willing to help out. Who should I contact ?
Depends on what you want to take as a starting point. For Fnorb, it would be DSTC, although it appears to be "officially unmaintained" for the moment. For omniORB, contact Duncan Grisby - he's usually quite responsive. For ILU, it would be Bill Janssen; I'm sure he'll accept patches. If you need something in a commercial environment (i.e. where purchasing licenses is not an issue), feel free to contact me in private :-)
Depends on the licensing costs, but yes, this is for a commercial product ;-)
In general, the DO SIG (do-sig@python.org) is a good place to discuss both CORBA and SOAP.
Thank you for the details. I'll sign up to that SIG as well (that should get me to 300 emails a day :-/). -- Marc-Andre Lemburg ______________________________________________________________________ Company: http://www.egenix.com/ Consulting: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/
participants (2)
-
M.-A. Lemburg
-
Martin v. Loewis