This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients lemburg, pitrou, scoder, skrah
Date 2014-08-23.22:44:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <53F9195B.1030103@free.fr>
In-reply-to <1408826550.92.0.86706856151.issue22194@psf.upfronthosting.co.za>
Content
Le 23/08/2014 16:42, Stefan Krah a écrit :
>
>> That's what I meant. The issue here is that Python's libmpdec is not exposed
>> to third-party code at all. Also there should probably be a (thin?) API to get
>> at the underlying mpdec object from a cdecimal PyObject (apologies for the poor
>> wording, I'm actually not acquainted with the libmpdec APIs).
>
> People were asking for libmpdec symbols to be hidden (#16745). It's easy to
> revert, just a couple of pragmas in the headers.

Who are those people? #16745 was opened by you :-)

> Platform specific maybe, but no hack:  I was thinking about storing the DSO
> handle in the PyModuleObject struct and add functions to lookup symbols.
> I'm attaching a diff for Linux -- It has been a while, but I'm rather certain
> that the corresponding scheme also worked on Windows (can't test now, my
> Windows VM is defunct).

How does it work? I've tried to dlopen() and then dlsym() the _decimal 
file manually, it wouldn't work for private (e.g. mpd) symbols.

> That would leave the usual troublemakers AIX etc., which have sketchy support
> anyway.

That sounds rather worrying. How about OS X? Why would that whole scheme 
be better than a capsule?
History
Date User Action Args
2014-08-23 22:44:48pitrousetrecipients: + pitrou, lemburg, scoder, skrah
2014-08-23 22:44:48pitroulinkissue22194 messages
2014-08-23 22:44:47pitroucreate