[tahoe-lafs-trac-stream] [pycryptopp] #44: test what happens if another Python module loads Crypto++ dynamic link library

[pycryptopp]

#44: test what happens if another Python module loads Crypto++ dynamic link
library
-------------------+--------------------------
Reporter:  zooko   |          Owner:
    Type:  defect  |         Status:  reopened
Priority:  major   |      Milestone:  0.6.0
 Version:  0.5.19  |     Resolution:
Keywords:          |  Launchpad Bug:
-------------------+--------------------------

Comment (by zooko):

 Okay, the programme from comment:8 starts with undoing [20100904201728
 -92b7f-1d838bc41934d7375fe2e611470a4e4c56185c49], but it turns out that in
 [459114f2aaf043274aa851c367ddfddabdb6f2e3/git] we already removed all
 trace of the old way of doing things, which was to set the
 {{{RTLD_GLOBAL}}} flag. No buildbot-performed tests or reports from the
 field have said that there was any problem with failure to identify two
 occurrences of the same symbol, from two different compilation modules, as
 the same, such as the original problem of "exception thrown from one
 module can't be caught in the other because the type of the exception
 class never compares equal". Therefore, I'm going to skip this step and
 assume that there is no need to set {{{RTLD_GLOBAL}}} anymore and proceed
 with the next step.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/pycryptopp/ticket/44#comment:13>
pycryptopp <https://tahoe-lafs.org/trac/pycryptopp>