extensions for issues: Artemis (how to upgrade to python 3.X)

[Dr. Arne Babenhauserheide]

Simon Harrison <info at simonh.uk> writes:
>> However it only runs under python 2.7 and soon mercurial will drop 2.7
>> support. The author basically told me some time ago, that he no longer
>> maintains actively Artemis and will not make the necessary changes to
>> make it run under python 3.X.
>> 
>> Unfortunately I have not much experience with python: is there any
>> documentation, of what to take into account when trying to make an
>> extension compatible with python 3.X?

I had pretty bad experiences porting extensions to Python 3. b now works
again under py3, but porting of infocalypse already cost me several
weekend-tries and isn’t finished yet. That one is pretty hard, though,
because it not only interacts with Mercurial. It also communicates with
Freenet and has the 4 conversion points:

- commandline arguments and output
- mercurial data and output
- freenet socket communication
- filesystem reading and writing for upload and download.

It might have been easier if I had started by identifying these and
defining clear conversion points beyond which only a single
representation is used (likely bytes, to avoid conversion cost between
extension and mercurial).

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1125 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20210803/bfb9d03b/attachment.asc>