In the past I believe we've built it with encryption. Regardless, we already ship encryption with Python thanks to the ssl module and I'm assuming the PSF has taken care of the necessary silly export document filing for the US so I see no reason to exclude it from bsddb.
On Wed, May 14, 2008 at 8:08 AM, Trent Nelson <[EMAIL PROTECTED]> wrote: > I was about to commit an initial import of the bsddb 4.6.21 source to the > 'external' area in the repo, which I obtained from the following URL: > > > http://www.oracle.com/technology/software/products/berkeley-db/index.html > > I downloaded the source that includes AES encryption, for no reason other > than it was first on the list. I'm now wondering if we should only be > importing the 'NC' source that doesn't contain any encryption? Jesus, does > pybsddb use any of the Berkeley DB encryption facilities? Would anything > break if we built the bsddb module without encryption? > > (Note that all of this only applies to Windows.) > > > Trent. > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/greg%40krypto.org > _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
