Comments on: MySQL-python Windows 64bit and 32bit distributions http://www.codegood.com/archives/4 In the beginning was the Code, and the Code was Good. Mon, 29 Aug 2011 10:10:41 +0000 hourly 1 http://wordpress.org/?v=3.1.1 By: yuxc http://www.codegood.com/archives/4/comment-page-2#comment-6370 yuxc Thu, 14 Apr 2011 08:45:10 +0000 http://codegood.com/?p=4#comment-6370 Thx very very much!I just want to give it up.... Thx very very much!I just want to give it up….

]]> By: Timm http://www.codegood.com/archives/4/comment-page-2#comment-5848 Timm Sun, 27 Mar 2011 05:59:24 +0000 http://codegood.com/?p=4#comment-5848 Amazing, a real timesaver!! THX a lot! Amazing, a real timesaver!! THX a lot!

]]> By: Kosei Kitahara http://www.codegood.com/archives/4/comment-page-2#comment-5077 Kosei Kitahara Sat, 26 Feb 2011 08:23:27 +0000 http://codegood.com/?p=4#comment-5077 Awesome! Thank you so much! Awesome! Thank you so much!

]]> By: Anton http://www.codegood.com/archives/4/comment-page-2#comment-4260 Anton Sat, 15 Jan 2011 15:06:52 +0000 http://codegood.com/?p=4#comment-4260 Thank you man, I'm sick already of mac/linux centric pythonistas, you've made my day. Thank you man, I’m sick already of mac/linux centric pythonistas, you’ve made my day.

]]> By: saber7 http://www.codegood.com/archives/4/comment-page-2#comment-3795 saber7 Tue, 14 Dec 2010 07:35:39 +0000 http://codegood.com/?p=4#comment-3795 nice job:D thnx very much for this. nice job:D
thnx very much for this.

]]> By: Rinze http://www.codegood.com/archives/4/comment-page-2#comment-2812 Rinze Fri, 22 Oct 2010 09:21:59 +0000 http://codegood.com/?p=4#comment-2812 Got it resolved. The trick was to download Mysql C connector's source code and build that using Visual Studio 2003. The resulting mysqlclient.lib make the last linking errors go away. All unit tests passed, except two, which were due to un-configured permissions. The only difference now is that _mysql.pyd depends on ws2_32 instead of wsock32, but that shouldn't give any problems. For anyone interested, the installer MySQL-python-1.2.3.win32-py2.5.exe can be found here: http://www.sendspace.com/file/yg0yol Use at own risk though :) Got it resolved. The trick was to download Mysql C connector’s source code and build that using Visual Studio 2003. The resulting mysqlclient.lib make the last linking errors go away.

All unit tests passed, except two, which were due to un-configured permissions.

The only difference now is that _mysql.pyd depends on ws2_32 instead of wsock32, but that shouldn’t give any problems.
For anyone interested, the installer MySQL-python-1.2.3.win32-py2.5.exe can be found here: http://www.sendspace.com/file/yg0yol

Use at own risk though :)

]]> By: Rinze http://www.codegood.com/archives/4/comment-page-2#comment-2804 Rinze Thu, 21 Oct 2010 20:06:02 +0000 http://codegood.com/?p=4#comment-2804 A little update about my post: where I wrote python24.dll, it should say python25.dll Also, after writing I found your post on the x64 build you made of Mysql-python 1.2.2 for python2.5. It seems to have the same dependencies as my build, including the need for the dynamically linked libmysql.dll. The weird thing is still that I also have a x32 build of Mysql-python 1.2.2 for python 2.5, which does not depend on an external libmysql.dll. I'm going to try and get a hold of the guy who built that one. A little update about my post: where I wrote python24.dll, it should say python25.dll

Also, after writing I found your post on the x64 build you made of Mysql-python 1.2.2 for python2.5. It seems to have the same dependencies as my build, including the need for the dynamically linked libmysql.dll.

The weird thing is still that I also have a x32 build of Mysql-python 1.2.2 for python 2.5, which does not depend on an external libmysql.dll. I’m going to try and get a hold of the guy who built that one.

]]> By: Rinze http://www.codegood.com/archives/4/comment-page-1#comment-2793 Rinze Thu, 21 Oct 2010 11:51:24 +0000 http://codegood.com/?p=4#comment-2793 This might be a long shot, but maybe someone reading this can point me in the right direction. I'm trying to build Mysql-python 1.2.3 for Python 2.5 under Windows 7. I'm using MS Visual C++ 2003 from the command line for this. When I use 'setup.py bdist_wininst', the code compiles just fine but after that the linker fails with a bunch of 'unresolved external symbol' errors. To resolve these errors I added (hard coded) the 'zlib', 'msvcrt', 'libmysql' libraries to Mysql-python's 'setup_windows.py', which already had 'kernel32', 'advapi32', 'wsock32' and 'mysqlclient' defined. When I try to build now, I end up with a working installer. However, the resulting _mysql.pyd is only 44Kb large (way smaller than others I've seen from built packages) and it only works when it can find libmySQL.dll. Also, when I check _mysql.pyd's dependencies, I see that they differ from others. Mine depends on libmysql.dll, msvcr71.dll, python24.dll and kernels32.dll, while others typically depend on python25.dll, kernel32.dll, advapi32.dll and wsock32.dll. So, somewhere along the line the dependencies get screwed up and I think that some code that needs to be included within the _mysql.pyd doesn't end up there (resulting in the smaller size and dependency of an external libmysql.dll) Anyone got any ideas? This might be a long shot, but maybe someone reading this can point me in the right direction.

I’m trying to build Mysql-python 1.2.3 for Python 2.5 under Windows 7. I’m using MS Visual C++ 2003 from the command line for this.

When I use ‘setup.py bdist_wininst’, the code compiles just fine but after that the linker fails with a bunch of ‘unresolved external symbol’ errors. To resolve these errors I added (hard coded) the ‘zlib’, ‘msvcrt’, ‘libmysql’ libraries to Mysql-python’s ‘setup_windows.py’, which already had ‘kernel32′, ‘advapi32′, ‘wsock32′ and ‘mysqlclient’ defined.

When I try to build now, I end up with a working installer.

However, the resulting _mysql.pyd is only 44Kb large (way smaller than others I’ve seen from built packages) and it only works when it can find libmySQL.dll. Also, when I check _mysql.pyd’s dependencies, I see that they differ from others.

Mine depends on libmysql.dll, msvcr71.dll, python24.dll and kernels32.dll, while others typically depend on python25.dll, kernel32.dll, advapi32.dll and wsock32.dll.

So, somewhere along the line the dependencies get screwed up and I think that some code that needs to be included within the _mysql.pyd doesn’t end up there (resulting in the smaller size and dependency of an external libmysql.dll)

Anyone got any ideas?

]]> By: Govind Kelkar http://www.codegood.com/archives/4/comment-page-1#comment-1842 Govind Kelkar Fri, 03 Sep 2010 04:34:43 +0000 http://codegood.com/?p=4#comment-1842 Victor your blog did helped me in setting up MySQLdb for python 2.7. Though I do not know the content language of your blog but the keywords did helped a lot. Regards, Govind Victor your blog did helped me in setting up MySQLdb for python 2.7. Though I do not know the content language of your blog but the keywords did helped a lot.

Regards,
Govind

]]> By: Microkernel http://www.codegood.com/archives/4/comment-page-1#comment-1540 Microkernel Thu, 12 Aug 2010 18:29:13 +0000 http://codegood.com/?p=4#comment-1540 Python 2.7? Python 2.7?

]]>