Re^2: [OT++] Seeking Win32 Python Wisdom

[syphilis]

As mentioned already by thanos1983, modifying the result as it is returned to you, or overriding the method may be your best and/or safest bet

I'm dealing with an autotools (./configure) build, and the libtool script that's reporting the error is itself autogenerated during the build.

I suppose it might be possible to make the correction in that script and then reset the script's timestamp to it's original setting.
Line 5999 of the libtool script is:

absdir=`cd "$dir" && pwd`

I could try preceding that line of code with the shell scripting of $dir =~ s/\\/\//g
What would that shell scripting equivalent of that perl code look like ? (I know as much about sh as I do about python ;-)

It would be much better if Python just delivered a forward-slashed path.
I'm guessing that there's a python command that's handing over python's equivalent of something like $Config{prefix}.

C:\>perl -V:prefix
prefix='c:\MinGW\perl524_64int';

In perl I could easily hack a solution such that perl -V:prefix returned a forward-slashed rendition of that path.
I was hoping that python might also lend itself to such hacking.

looking at the _getuserbase() code within the /usr/lib/python2.7/sysconfig.py file, the result may be coming from somewhere in the os.path method (os.py file),

Hmmm ... altering os.sep might (or might not) be all that's needed.
How would I change that setting ?
Is there a simple python command (or script) that will tell me the current setting of os.sep ?

Cheers,
Rob