Re: Path puzzle

On Sep 5, 2024, at 18:26, bob prohaska <fbsd@www.zefox.net> wrote:

> On Thu, Sep 05, 2024 at 07:47:23PM +0100, Steve O'Hara-Smith wrote:
>> On Thu, 5 Sep 2024 11:37:06 -0700
>> bob prohaska <fbsd@www.zefox.net> wrote:
>> 
>>> bob@pelorus:~ % head server_try
>>> #!/usr/bin/python3.11
>> 
>> Bingo! On FreeBSD python3.11 will be in /usr/local/bin not /usr/bin.
>> 
>> This is why the recommended shebang for python code is
>> 
>> #!/usr/bin/env python3.11
>> 
>> Which is portable.
> Thank you....never crossed my mind to check the executable location 8-(
> 
> It turns out that the python code being run (from 
> https://gitlab.com/ldo/ssl_try_python) works on Debian Linux Bookworm but
> not on FreeBSD stable/14.1. Is there a guide to differences between the
> dialects? 

As I read that wording, you might be talking programming
language instead of library compatibility/portability.
But:

https://gitlab.com/ldo/ssl_try_python/-/blob/master/server_try?ref_type=heads

shows:

import sys
import os
import enum
import signal
import socket
import select
import ssl
import getopt

in addition to server_try's own source code. Do you
have all that context available/set-up so that the
imports should find everything? (Warning: I'm no
python expert so it could be that the language
requires all those to be automatically available.)

Also, if found, which of imports might be portable
between "Debian Linux Bookworm" vs. "FreeBSD
stable/14.1"? Which imports are not in some way?
Such points need not be tied to language 
compatibility.

I suggest showing/pointing-to specifics of what
evidence there is of the does-not-work status,
such would not be so open-ended and without
context.

In essence you have taken on the job of doing the
investigation of what it would take to know how to
create a port for ssl_try_python --or at least for
server_try. Or so it appears to me.

===
Mark Millard
marklmi at yahoo.com