The current setup.py tries to compilelink against some pre-built Linux FreeTDS libraries, and also tries to link against librt, which doesnt exist on OSX.Additionally, it only explicitly looks for FreeTDS libraries from Fink or MacPorts, so if youve installed Homebrew (if you use if) or FreeTDS itself in a non-standard location, it may not be located by compilerlinker.You may need to adjust setup.py further if youve installed FreeTDS in a different location.You can generally ignore the warnings from the linker about missing directories that may not exist on your system.
By default, pymssl will be a multi-architecture build (assuming youre using the system Python 2.7.1), so even with a patched setup.py you will see a linker warning something like. You can avoid the warning by using ARCHFLAGS to make a x8664-only build. Provide details and share your research But avoid Asking for help, clarification, or responding to other answers. ![]() Not the answer youre looking for Browse other questions tagged python pymssql or ask your own question. Of course, I want this application to be run as cost effectively as possible so Im placing the Django app in AWS Lambda using Zappa for deployment. I gave a talk on using AWS Lambda and Zappa for a Django project at PSU MacAdmins 2017 called Imaging in 50 Locations. Needless to say, I love deploying Django apps this way. This post wont go into how to use Zappa.). The open-source MS SQL library Im using in my app is pymssql. This is a great library that works on many platforms including AWS Lambda (which is basically just the AWS EC2 Linux AMI). It even supports the latest version of Python 3.6 which Im also using. Pymssql Software On YourThis normally wouldnt be a problem since the team over pymssql also includes an option to build the software on your machine with a bundled version of FreeTDS in precompiled wheels. If I deploy from an EC2 Linux instance Zappa will upload a Linux compatible version of pymssql but its still missing FreeTDS. The quickest way to solve this would be for the team over at pymssql to release a precompiled Python 3.6 manylinux wheel. Until then I need a workaround. Make sure to install pymssql from the latest build: pip install git. Unfortunately, I still seem to be getting this error, which suggests that even though libsybdb.so.5 is in (what should be) the right location, the import script or interpreter is looking elsewhere for it. Any insights on how to check for where importlibinit.py is looking for the.so file Thanks. My project is Django-based so Zappa handles all the deployment for me. When I type in the command to activate, I get the error that virtualenvbinactivate is not a file or directory. I have tried multiple other things, including trying to uninstall virtualenv, but then I get a permission denied warning on usrlocalbin, which is an empty directory. By not running source, you are trying to run the activate file directly, which you cannot do. I have followed the same set up for SQL server and works perfectly. It may even mean there is an issue outside of the pymssql library itself. As this comment suggests ( ), Id recommend posting this instead as a topic on the discussion forum at since its not clear that this is a pymssql bug yet. You should mention in your posting what platform you are connecting from (e.g.: Linux, Mac, Windows, etc.), what version of Python youre using, how you installed pymssql (e.g.: pip install pymssql or python setup.py from code checked out from hg tip, etc.), what version of FreeTDS you have, etc. To find out more, including how to control cookies, see here.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2020
Categories |