[SVN-2565] svn python 2.4 bindings

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.x
• Fix Version/s: ---
• Component/s: bindings_swig_python

Environment

Windows 2000

• Assignee: Unassigned
• Reporter: Subversion Importer
• Created: 08/Jun/06 09:46
• Updated: 17/Jul/07 08:12
• Resolved: 17/Jul/07 08:12

Description

There is no Python 2.4 bindings. Seems like the problem is well described here:
http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=101731

But we still need to resolve the situation somehow.
Following the idea from this link
http://www.brunningonline.net/simon/blog/archives/001906.html
it is either

1. Distribute new Apache 2.x.x httpd binaries compiled by default with Visual
Studio C++ 2005 compiler. By default, because majority of people are using new
free version of Microsoft compiler or GCC instead of rather old MSVC++ 6.0. I do
not say to abandon MSVC++ 6.0 altogether - just provide different official
binaries. The point is that developers, who need to maintain old MSVC++ 6.0
sourcecode base for their extensions are still have to use older 1.3.x or 2.0.x
Apache versions and are unlikely to switch to new Apache 2.x.x, but even if they
do - they will be able to compile binaries, since support for VC++ 6.0 is not
abandoned.

2. Distribute new Python 2.4 compiled using old MSVC++ 6.0  This is not a good
solution. I bet they will not agree to fallback.

3. Provide alternative distribution for Python, Apache httpd ot both compiled
with the same compiler (VC6, VC7 or MinGW/GCC) with Python bindings. I guess
this is most possible if appropriate bandwidth and build machines are available,
of course. Huge build overhead needed to build.

4. Forget about 2.4 and future python bindings and install Python 2.3 Acceptable
if all you need from Python is just to make ViewVC available.

Original issue reported by techtonik