On 27. 7. 25 01:26, Daniel Sahlberg wrote:
Den lör 26 juli 2025 kl 22:19 skrev Branko Čibej <br...@apache.org>:
On 26. 7. 25 20:40, dsahlb...@apache.org wrote:
Author: dsahlberg
Date: Sat Jul 26 18:40:48 2025
New Revision: 1927483
Log:
GitHub removed their SVN server some years ago so getting sources with
svn won't work anymore.
* subversion/bindings/ctypes-python/README
(BUILDING CSVN): Remove example how to checkout from GitHub with svn
Modified:
subversion/trunk/subversion/bindings/ctypes-python/README
Modified: subversion/trunk/subversion/bindings/ctypes-python/README
==============================================================================
--- subversion/trunk/subversion/bindings/ctypes-python/README Sat Jul
26 15:14:07 2025 (r1927482)
+++ subversion/trunk/subversion/bindings/ctypes-python/README Sat Jul
26 18:40:48 2025 (r1927483)
@@ -16,8 +16,6 @@https://github.com/davidjamesca/ctypesge
the ctypes python bindings.
For example:
- $ svn cohttps://github.com/davidjamesca/ctypesgen/trunk ctypesgen
-or
$ git clonehttps://github.com/davidjamesca/ctypesgen
Once you have all of the above software installed, you can build the
The canonical URL is actually:
https://github.com/ctypesgen/ctypesgen.git
-- Brane
Good catch, thanks!
Still the whole binding seems to have fallen for bitrot... or else I'm
just to stupid to understand how to build it.
I haven't built ctypes-python in years. AFAICT the last/functional
/change there is 11 years old, everything else (up to 3 years ago) was
just bookkeeping.
In particular, it seems to depend on ctypes.pythonapi.PyFile_AsFile
which is no more since Python 3 and there doesn't seem to be an easy
replacement (at least not that I'm able to find on Google).
There'd have to be some magic translation code. In Python3, you have
PyObject_AsFileDescriptor() that returns an int, and you could wrap that
in fdopen() to get a FILE*, but that would work only for disk-based
Python streams. StringIO and similar (user-defined) file-like objects
don't support that, and I don't believe there's a standard way to
connect a FILE* to your own virtual file implementation.
That said, I don't think PyFile_AsFile worked for "non-file file-like"
objects, either.
If someone else is able to build it, let's adjust this as well.
Otherwise ... remove it?
/me shrugs. It's evidently unmaintained, and the Swig bindings work,
more or less.
-- Brane