Please first make sure you have looked at:

• Documentation: https://github.com/mkleehammer/pyodbc/wiki
• Other issues

Environment

To diagnose, we usually need to know the following, including version numbers. On Windows, be sure to specify 32-bit Python or 64-bit:

• Python: 2.7.14
• pyodbc: 4.0.23
• OS: MacOS
• DB: SQL Server
• driver: ODBC Driver 13 for SQL Server

Issue

Trying to use fast execute many option to insert data to the database throws the error shown below. It works if the flag is not set.

Expected behavior:

Cursor should be able to write to database without throwing an error.

Observed behavior:

---------------------------------------------------------------------------
Error                                     Traceback (most recent call last)
<ipython-input-24-5e5f851229b4> in <module>()
      1 cursor.fast_executemany = True
----> 2 cursor.executemany(query, x.values.tolist())

Error: ('HY010', u'[HY010] [unixODBC][Driver Manager]Function sequence error (0) (SQLParamData)')

Please first make sure you have looked at:

• Documentation: https://github.com/mkleehammer/pyodbc/wiki
• Other issues

Environment

To diagnose, we usually need to know the following, including version numbers. On Windows, be sure to specify 32-bit Python or 64-bit:

• Python: 2.7.6
• pyodbc: Latest version
• OS: ubuntu 14.04.5
• DB:
• driver:

Issue

pip install pyodbc --user Collecting pyodbc Using cached pyodbc-4.0.17.tar.gz Building wheels for collected packages: pyodbc Running setup.py bdist_wheel for pyodbc ... error Complete output from command /usr/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-build-YtLrrj/pyodbc/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" bdist_wheel -d /tmp/tmp5eqhA5pip-wheel- --python-tag cp27: running bdist_wheel running build running build_ext building 'pyodbc' extension creating build creating build/temp.linux-x86_64-2.7 creating build/temp.linux-x86_64-2.7/src x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -DPYODBC_VERSION=4.0.17 -DSQL_WCHART_CONVERT=1 -I/usr/include/python2.7 -c src/textenc.cpp -o build/temp.linux-x86_64-2.7/src/textenc.o -Wno-write-strings cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default] In file included from src/textenc.cpp:2:0: src/pyodbc.h:56:17: fatal error: sql.h: No such file or directory #include <sql.h> ^ compilation terminated. error: command 'x86_64-linux-gnu-gcc' failed with exit status 1

Failed building wheel for pyodbc Running setup.py clean for pyodbc Failed to build pyodbc Installing collected packages: pyodbc Running setup.py install for pyodbc ... error Complete output from command /usr/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-build-YtLrrj/pyodbc/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-CRLrEJ-record/install-record.txt --single-version-externally-managed --compile --user --prefix=: running install running build running build_ext building 'pyodbc' extension creating build creating build/temp.linux-x86_64-2.7 creating build/temp.linux-x86_64-2.7/src x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -DPYODBC_VERSION=4.0.17 -DSQL_WCHART_CONVERT=1 -I/usr/include/python2.7 -c src/textenc.cpp -o build/temp.linux-x86_64-2.7/src/textenc.o -Wno-write-strings cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default] In file included from src/textenc.cpp:2:0: src/pyodbc.h:56:17: fatal error: sql.h: No such file or directory #include <sql.h> ^ compilation terminated. error: command 'x86_64-linux-gnu-gcc' failed with exit status 1

----------------------------------------

Command "/usr/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-build-YtLrrj/pyodbc/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-CRLrEJ-record/install-record.txt --single-version-externally-managed --compile --user --prefix=" failed with error code 1 in /tmp/pip-build-YtLrrj/pyodbc/

Environment

• Python: 3.8.5
• pyodbc: 4.0.30
• OS: macOS 10.5.7
• DB: MS SQL Server 2017 and 2019
• driver: microsoft/mssql-release/msodbcsql17: stable 17.6.1.1

Issue

I cannot insert strings with a length greater than 2000 into columns with a datatype of varchar(max) ornvarchar(max) using parametrised queries.

In particular the POC (see below) fails with following output:

started
non-param: len(content)=2001: success
Traceback (most recent call last):
  File "test.py", line 54, in <module>
    cursor.execute(sql, (content,))
pyodbc.ProgrammingError: ('42000', "[42000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Cannot convert to text/ntext or collate to 'Latin1_General_100_CI_AS_SC' because these legacy LOB types do not support UTF-8 or UTF-16 encodings. Use types varchar(max), nvarchar(max) or a collation which does not have the _SC or _UTF8 flags. (4189) (SQLParamData)")

Every parametrised insert with a string having a length greater than 2000 fails with the above error message relating to a text/ntext conversion or Latin1_General_100_CI_AS_SC collation, which is strange considering that only plain ASCII is inserted.

How can I resolve this issue and insert strings of any length into the database?

POC:

import pyodbc

host = 'tcp:127.0.0.1,1433'
db = 'pyodbc_test'
user = 'sa'
pwd = 'P@ssw0rd'

print('started')

cnxn = pyodbc.connect('DRIVER={ODBC Driver 17 for SQL Server};SERVER='+host+';DATABASE='+'master'+';UID='+user+';PWD='+ pwd, autocommit=True)
cursor = cnxn.cursor()

try:
    cursor.execute(f'CREATE DATABASE {db} COLLATE Latin1_General_100_CI_AS_SC')
except pyodbc.ProgrammingError as e:
    pass # database exists

cursor.execute(f'USE {db}')

try:
    cursor.execute("""
        CREATE TABLE msg (
            id int identity(1,1) not null,
            content varchar(max) not null
        );""")
except pyodbc.ProgrammingError as exc:
    pass # table exists

content = 2001 * 'A'

cursor.execute(f"""
    INSERT INTO msg (content)
    VALUES ('{content}')""")
print(f'non-param: {len(content)=}: success')

# fails (pyodbc 4.0.30)
sql = f"""
      INSERT INTO msg (content)
      VALUES (?)"""
cursor.execute(sql, (content,))
print(f'param: {len(content)=}: success')

print('finished')

Please first make sure you have looked at:

• Documentation: https://github.com/mkleehammer/pyodbc/wiki
• Other issues

Environment

Windows WSL Bash

To diagnose, we usually need to know the following, including version numbers. On Windows, be sure to specify 32-bit Python or 64-bit:

• Python: Anaconda (python 3.6)
• pyodbc: 3.0.10
• OS: Ubuntu 16.04 and WSL Bash
• DB: SQL Server
• driver: ODBC Driver 13 for SQL Server

Issue

Although I was able to install the pyodbc package in Anaconda3, and the "import pyodbc" module load without any errors. But, the connection string line error-out giving the following error:

maxt@MTrinidadLT2:~$ python Python 3.6.0 |Anaconda 4.3.1 (64-bit)| (default, Dec 23 2016, 12:22:00) [GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] on linux Type "help", "copyright", "credits" or "license" for more information. import pyodbc cnxn = pyodbc.connect('DRIVER={ODBC Driver 13 for SQL Server};SERVER=MTRINIDADLT2,51417;DATABASE=master;UID=sa;PWD=$SqlPwd01!') Traceback (most recent call last): File "", line 1, in pyodbc.Error: ('01000', "[01000] [unixODBC][Driver Manager]Can't open lib '/opt/microsoft/msodbcsql/lib64/libmsodbcsql-13.1.so.7.0' : file not found (0) (SQLDriverConnect)")

Often it is easiest to describe your issue as "expected behavior" and "observed behavior".

Hi all, This is linked to an old closed issue but I wanted to re-raise. Simply if a connection cannot be made to a DB, for example a firewall is blocking the attempt my script will just hang forever. I've looked around at the docs and stack overflow and a lot of people seem to be reporting the keyword doesn't work / is ignored.

For example:

try:
        conn = pyodbc.connect(CONN_STRING,timeout=5)
except:
        print "Connetion to Database timed out"
        sys.exit(1)

Hi guys, I already had a look at previous similar issues but I could not find a proper solution. I am using a Jupyter notebook on Azure ML compute instance. I am trying to connect an Azure SQL database using pyodbc but I get below error: _('01000', "[01000] [unixODBC][Driver Manager]Can't open lib 'ODBC Driver 17 for SQL Server' : file not found (0) (SQLDriverConnect)")_

My code:

import pyodbc
server = 'tcp:xxx.database.windows.net'
database = 'xxxx'
username = 'xxx'
password = 'xxxxx'
cnxn = pyodbc.connect('DRIVER={ODBC Driver 17 for SQL Server};SERVER='+server+';DATABASE='+database+';UID='+username+';PWD='+ password)
cursor = cnxn.cursor()

Environment

• Kernel: Python 3.6 Azure ML
• Python: 3.6.9 |Anaconda, Inc. [GCC 7.3.0]
• pyodbc: 4.0.27
• OS: 16.04.6 LTS (Xenial Xerus)
• DB: Azure SQL
• driver: ODBC Driver 17 for SQL

Issue

Expected behaviour: I expect to have a successfull connection, Observerd behaviour: No connection to the DB because it can not locate ODBC Driver 17 for SQL.

Extra information from similar questions online: 1- There is no microsoft folder in /opt folder (referringthis question and solutions) 2- There is no odbcinst file in /etc folder (referring this question and solutions) 3- When I try pyodbc.drivers() it returns an empty array. (I uninstalled and reinstalled pyodbc, I am able to import it.) 4- I can not locate msodbcsql17 (referring here) 4- I tried ODBC Driver 13 as well, same problem exists.

Any help will be appreciated!

I'm doing selects/inserts/updates on my tables and SQL Server is creating an execution plan for every permutation of character lengths that the selects/inserts/updates into the table from python.

I believe this is causing some issues with the performance of the db and may create some memory issues.

I would like to be able to set the data type/length when passing parameters. Ideally, pyodbc would know the datatype/length before inserting and set them accordingly but I don't know if this will create more issues issues than it will solve, so being able to define them myself might help.

More specifically, when I run a trace, this is what I see:

declare @p1 int
set @p1=4882452
exec sp_prepexec @p1 output,N'@P1 nvarchar(11),@P2 nvarchar(16)',N'SELECT TOP 1 C_KEY FROM C WHERE A_NM = @P1 AND C_NM = @P2',N'Zantesuken1',N'RasalhagueLegacy'
select @p1

and when looking at the execution plans, I find that an execution plan has been created for every single permutation of these selects.

Perhaps something like this:

cursor.execute("SELECT X FROM Y WHERE Z1 = ? AND Z2 = ?", param1.type(varchar(50)), param2.type(bigint))

No idea if this makes sense and maybe this is already possible somehow and I don't know about it, so let me know if there's a way around this issue.

edit Also noticed that the auto-incrementing @p1 seems to be going up really quickly (I'm doing a lot of transactions). Is there any way to reset this counter? I've tried deleting the cursor, closing the connection, but nothing seems to be working.

Environment

• Python: 3.6.6 64bit
• pyodbc: 4.0.27
• OS: Windows 10 Enterprise
• DB: Microsoft Access DB Linked to Sharepoint 2016 List
• driver: Not sure how to check this. Please advise if this info is important.

Issue

I have two .accdb files. One is called Test.accdb, the other is called Test2.accdb.

Test.accdb is linked to a Sharepoint 2016 List. Test2.accdb is not linked to anything.

I am having issues setting up a conn variable.

I am assigning conn as follows:

conn = pyodbc.connect(r'Driver={Microsoft Access Driver (*.mdb, *.accdb)}; DBQ=C:\\Users\\userName\\Desktop\\Project Folders\\sharepointList\\test.accdb;')

When I run that line of code with test2.accdb as the file to connect to I have no issues. The line completes and I can run the rest of my code.

When I run the line of code with test.accdb, the one linked to Sharepoint, I can not get past it. I wrote a small amount of code to test a theory. It is shown below:

print("Before")
conn = pyodbc.connect(r'Driver={Microsoft Access Driver (*.mdb, *.accdb)}; DBQ=C:\\Users\\userName\\Desktop\\Project Folders\\sharepointList\\test.accdb;')
print("After")

I also tried the following, using try/except:

try:
    print("Before")
    conn = pyodbc.connect(r'Driver={Microsoft Access Driver (*.mdb, *.accdb)}; DBQ=C:\\Users\\userName\\Desktop\\Project Folders\\sharepointList\\test.accdb;')
except:
    print("Something Crashed")
print("After")

The new print statement was never executed. This leads me to believe that the code never really crashed, It just sort of stopped.

When I run this code with test2.accdb both print lines are executed. When I run this code with test.accdb, the one linked to sharepoint, only the "Before" print line is executed. I would expect the conn assignment to execute completely and allow me to execute the rest of my code. Instead, the code stops running at some point within the .connect() function. I get no error message when I run the code. The code simply stops.

• Python: 2.7.15 x86
• pyodbc: 4.0.24
• OS: Windows 10/Ubuntu 16.04
• DB: MS SQL Server 2017
• driver: FreeTDS 1.0.9

Issue

I have some complex T-SQL queries that have multiple commands like this:

     declare @fim date
			IF (OBJECT_ID('[dbo].[fnUTCDateTB]') IS NOT NULL)
				SET @fim = (select dateadd(day,-4,convert(date,DataLocal)) from [dbo].[fnUTCDateTB](GETDATE()))
			ELSE
				SET @fim = dateadd(day,-4,convert(date,getdate()))
			 SELECT CST.service_id as service_id
			     ,  CST.ID as customer_id
		    	 ,  CFG.ID as customer_config_id
		    	 ,  CASE cct.frequency_type
                  		WHEN 'DAY'   THEN DATEADD(DAY  , cct.frequency_quantity * cfg.cycle_number, cfg.birthday)
                        WHEN 'MONTH' THEN DATEADD(MONTH, cct.frequency_quantity * cfg.cycle_number, cfg.birthday)
                        WHEN 'YEAR'  THEN DATEADD(YEAR , cct.frequency_quantity * cfg.cycle_number, cfg.birthday)
                    END as next_birthday
		      FROM  CUSTOMER cst (NOLOCK)

which used to work with pymssql without any problem. Later we had to switch to PyODBC because we needed to connected to an AlwaysOn secondary database, and this required the ApplicationIntent=ReadOnly parameter. I configured it by compiling and installing the latest FreeTDS plugin with ODBC. I tested it with tsql and isql tools, in addition to MS SQL Management Studio 17 and JetBrains DataGrip, and the queries worked as expected. The problem only happens with my Python script using PyODBC. I get this error with complex queries:

first_row = cur.fetchone()

pyodbc.ProgrammingError: No results. Previous SQL was not a query.

If I test with short queries they would work even with @DECLARE statements, while long queries work only replacing when removing the @DECLARE statements and substituting all the variables inside the query with their values.

I hope that you can give me a tip on how I can solve that.

this fails consistently on 2 different machines one Windows Server 2012R2 and one Win8.1 the error is the same.

C:\Windows\System32>pip install pyodbc Collecting pyodbc Using cached pyodbc-3.0.10.tar.gz Installing collected packages: pyodbc Running setup.py install for pyodbc Complete output from command "c:\program files (x86)\python 3.5\python.exe" -c "import setuptools, tokenize;file='C:\Users\Kiril\AppData\Local\Temp \pip-build-wx_guj66\pyodbc\setup.py';exec(compile(getattr(tokenize, 'open', o pen)(file).read().replace('\r\n', '\n'), file, 'exec'))" install --recor d C:\Users\Kiril\AppData\Local\Temp\pip-0hu94gdr-record\install-record.txt --sin gle-version-externally-managed --compile: running install running build running build_ext building 'pyodbc' extension error: [WinError 2] The system cannot find the file specified

----------------------------------------

Command ""c:\program files (x86)\python 3.5\python.exe" -c "import setuptools, t okenize;file='C:\Users\Kiril\AppData\Local\Temp\pip-build-wx_guj66\py odbc\setup.py';exec(compile(getattr(tokenize, 'open', open)(file).read().re place('\r\n', '\n'), file, 'exec'))" install --record C:\Users\Kiril\AppData \Local\Temp\pip-0hu94gdr-record\install-record.txt --single-version-externally-m anaged --compile" failed with error code 1 in C:\Users\Kiril\AppData\Local\Temp
pip-build-wx_guj66\pyodbc

C:\Windows\System32>

when pip install pyodbc got error #include <sql.h> ^~~~~~~ compilation terminated. error: command 'gcc' failed with exit status 1

----------------------------------------

Command "/usr/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-install-e89qqq9z/pyodbc/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-record-_itwd76b/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-install-e89qqq9z/pyodbc/

Please first make sure you have looked at:

• Documentation: https://github.com/mkleehammer/pyodbc/wiki
• Other issues

Environment

To diagnose, we usually need to know the following, including version numbers. On Windows, be sure to specify 32-bit Python or 64-bit:

• Python: 3.11
• pyodbc: 4035
• OS: Ventura 13.1
• DB:database.windows.net
• driver: ODBC Driver 18 for SQL Server

Issue

Often it is easiest to describe your issue as "expected behavior" and "observed behavior".

File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/sqlalchemy/engine/default.py", line 598, in connect return self.dbapi.connect(*cargs, **cparams) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sqlalchemy.exc.OperationalError: (pyodbc.OperationalError) ('08001', '[08001] [Microsoft][ODBC Driver 18 for SQL Server]Client unable to establish connection (0) (SQLDriverConnect)') (Background on this error at: https://sqlalche.me/e/14/e3q8)

Please first make sure you have looked at:

• Documentation: https://github.com/mkleehammer/pyodbc/wiki
• Other issues

Environment

To diagnose, we usually need to know the following, including version numbers. On Windows, be sure to specify 32-bit Python or 64-bit:

• Python: 3.11 64-bit
• pyodbc: 4.0.35
• OS: Windows 10
• DB: SQL Server 2019 (15.0.4123.1)
• driver: ODBC Driver 18 for SQL Server (2018.181.02.01)
• SQL.LOG

Issue

The PRINT statement is not getting outputed. (see https://github.com/mkleehammer/pyodbc/wiki/Cursor#messages). It will work if I make input less than 2070 characters.

cnxn = pyodbc.connect(cnxn_str, autocommit=True)
    crsr = cnxn .cursor()
    input = '165,2900,3123,6135,2025,1117,5673,1889,7452,6652,4088,6837,6104,4129,676,6013,5963,4516,2947,1408,255,1859,7205,3747,3553,123,6446,357,1403,1091,2140,3397,3774,5924,3379,3436,6043,1194,5618,1406,1081,4120,2252,6751,3765,826,2645,949,2993,5718,1043,2316,4438,2535,7165,6562,4436,121,7429,4433,2610,663,832,6941,3554,3698,120,6920,3077,5965,2809,527,6566,4548,3929,6724,7228,2098,119,5771,1264,5843,1508,1075,5623,1239,4338,6787,7406,6569,4190,1683,2538,1415,6672,3521,3295,118,6615,1827,6406,7329,6831,7328,3534,849,2002,5746,2742,6549,7439,6892,2082,2042,1667,7446,2192,897,3428,1435,2487,780,117,6418,1858,2016,1193,3566,1237,4525,2085,1068,6369,2049,487,494,4362,846,1646,1588,875,793,6778,6177,1067,5708,712,7414,5973,4074,3832,3571,116,6594,3287,2870,3419,3174,115,4428,4124,1823,2422,3352,540,5863,2228,1714,2143,6195,5977,3894,545,5998,6755,6253,6847,1350,4515,2666,1929,7095,114,7061,3167,6689,6185,5722,7293,6834,6354,4421,6630,113,3565,3551,661,3307,1344,5717,7072,3114,7497,1184,3454,878,468,2188,6085,7071,112,4471,4331,2668,3533,7212,461,6946,7269,3550,6545,1005,3862,716,4205,1341,3976,6074,585,2287,3582,7221,3735,5643,3343,1551,2648,5695,353,3612,1850,1573,7006,1145,6824,6246,6669,703,4081,6070,3350,6067,3135,6184,5940,2927,5857,2581,2390,4295,6157,950,7110,7294,3275,3986,7113,4313,1739,1092,7495,6126,5855,3824,5839,6226,3069,2663,6722,5831,3705,5941,111,3786,1965,6441,6602,856,6140,4158,3610,6242,2170,1887,4429,1108,6404,3327,2251,1141,4100,7344,7342,2858,7343,110,4330,3062,1796,5671,4378,800,2539,6848,109,4150,5850,3090,3362,2385,1623,6927,3763,1263,2334,7167,7203,1487,6025,7411,2102,5644,3730,2722,1778,814,2104,1595,5794,635,4184,5881,3548,3048,6932,1574,6049,2320,3543,1387,5936,7079,108,7408,3497,3959,1389,1262,5574,3098,2341,2165,5680,3485,4430,1730,6329,7451,1757,7196,6179,107,2401,6411,6165,1012,1061,2642,5847,1585,2086,2081,6678,5575,6172,1727,6676,2807,2091,6655,3969,1795,4505,5915,5571,5674,2951,3253,4449,3120,499,105,104,103,4445,102,6805,6467,1177,3480,2670,101,753,475,1111,864,100,3517,5584,5804,1235,5960,6934,2957,1444,3477'
    crsr.execute("PRINT 'HI';SELECT ?", [input])
    print(crsr.messages)

Often it is easiest to describe your issue as "expected behavior" and "observed behavior".

Some tidy-up work on setup.py:

• Better to use shlex.split() instead of just plain str split() when parsing unix-style (posix-style) parameters (lines 234, 237). Plain split() will not correctly parse parameter values with spaces in them (e.g. echo "Hello world!").
• If odbc_config is not available at line 205, then there would be no stdout and the unpacking at line 206 would fail.
• Best not use dir as a variable at line 222 because it's a built-in function. Not an actual problem here because dir is in its own namespace within the list comprehension but still.
• Bump the pyodbc package version in setup.py. Version 4.0.35 has been-and-gone now so we should be concentrating on version 4.0.36 (or perhaps 5.0.0).
• General linting. This was largely done by Kleehammer in this commit but somehow it got reverted.

This is a potential minimalistic PR for dropping official support for Python 2.7 and 3.6. This PR does not remove any 2.7 code but it would at least mark a formal transition to the Python 3.7+ only version of pyodbc.

Note, this PR will not work with Python 2.7! Do not merge until pyodbc no longer supports Python 2.7.

The most significant part of this PR is that the unit test scripts have been moved into database-specific folders. There is now a separate folder for each database. The pytest utility is now directed to the relevant folder to find ("discover") all the unit tests for a specific database. Hence, in the future, new unit tests can be added to the relevant database folder simply as brand new scripts, rather than having to add the tests to the existing database-specific test script. pytest will find them all.

Other updates:

• Python 2.7 and 3.6 are dropped from the CI scripts (but this PR assumes they are already no longer supported)
• the Ubuntu build tests now use the new run_tests() utility function, so that all tests happen from one command
• for the Windows build tests on Appveyor:
  • SQL Server 2019 is now used (instead of SQL Server 2017)
  • PostgreSQL 13 is now used (instead of PostgreSQL 11 which is rather old now), including the drivers
  • the latest MySQL 8.0 drivers are now used
  • the updated run_tests() utility function is used to run tests
  • the build package is used to generate wheels instead of setup.py, to be more PEP517-compliant

Notes:

• The unit test scripts have not been changed to use "pytest" style unit tests. The scripts still use "unittest" style unit tests. That work will be the subject of a later PR.
• When Python 2.7 is dropped, the "tests2" folder will be deleted and the "tests3" folder will be renamed to just "tests". At that point, the testing code will have to be updated accordingly.

Environment

To diagnose, we usually need to know the following, including version numbers. On Windows, be sure to specify 32-bit Python or 64-bit:

• Python: 3.10.6
• pyodbc: 4.0.35
• OS: macOS Ventura (13.0)
• DB: N/A
• driver: N/A

Issue

overview: I upgraded my pyodbc version to the latest on PyPi (v4.0.35) and noticed I was getting a new error that I had never dealt with before. Specifically, when importing pyodbc I receive the following:

(0x0002): symbol not found in flat namespace '_SQLAllocHandle'

An issue for this was raised and closed a while ago; it references this exact problem: #885

expected behavior: pyodbc should import without issue

steps to reproduce:

1. Create new virtual environment and activate:

python -m venv .venv
source .venv/bin/activate

2. Install latest pyodbc:

pip install pyodbc

3. Import pyodbc and observe error:

python
>>> import pyodbc
>>> (0x0002): symbol not found in flat namespace '_SQLAllocHandle'