From: Sébastien S. <sa...@us...> - 2009-10-22 16:53:18
|
Hi Andrei, I think you are right it would be more consistent to also prefer the mono-threaded libraries on 64 bits architectures. I will make the modification you suggested. On the other hand, it would be even better if we could specify with a compilation flag to setup.py the preferred way to compile: static/dynamic - threaded/non-threaded. I will try to see if such options can be added, with a lower priority. regards -- Sébastien Sablé Gnepp, Andrei a écrit : > Hi, > > In revision 405, setup.py was changed to default to the non-thread-safe > Sybase libraries under 32-bit compilation. However, 64-bit compilation > still defaults to the thread-safe ones (with "_r" in the name). > > 91 extensions = [('', 'a'), ('', 'so'), ('_r', 'a'), ('_r', > 'so')] > > 92 if have64bit and sys.platform not in ['osf1V5']: > > 93 extensions = [('_r64', 'a'), ('_r64', 'so')] + extensions > > Is this discrepancy between 32- and 64-bit intentional, or can 64-bit > compilation also default to the non-thread-safe libraries when available? > > i.e. something like: > > 93 extensions = [('64', 'a'), ('64', 'so'), ('_r64', > 'a'), ('_r64', 'so')] + extensions > > Andrei Gnepp > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > > > ------------------------------------------------------------------------ > > _______________________________________________ > Python-sybase-misc mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-sybase-misc |