Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

bulkcopy_arrow() / bulkcopy()` broken in 1.16.0

Aperta
  • Qualcosa non va?
#855 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@jahnvi480 ci sta già lavorando.

Dal 22/10/2026.

  • #860 di @jahnvi480 — aperta

Valutazione

Difficoltà
3/5
Tempo stimato
Mezza giornata
Idoneità per principianti
72/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python
Ambito
database

Direzione di ricerca

Start by reading mssql_python/cursor.py at the bulkcopy_arrow() implementation and trace how it imports and uses mssql_py_core; inspect the corresponding bulkcopy() path too. Reproduce the reported import behavior with the 1.16.0 Windows package and check where the connection classes are exposed. Done when both bulk copy methods can access the connection class after a clean 1.16.0 install.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: bulk-copy bug inADO triage done under development

Title

bulkcopy_arrow() / bulkcopy() broken in 1.16.0: AttributeError: module 'mssql_py_core' has no attribute 'PyCoreConnection'

Description

After upgrading from 1.15.0 to 1.16.0, any call to cursor.bulkcopy_arrow(...) (and presumably cursor.bulkcopy(...), which shares the same pycore connection path) fails immediately with:

AttributeError: module 'mssql_py_core' has no attribute 'PyCoreConnection'

Full traceback:

File ".../site-packages/mssql_python/cursor.py", line 3764, in bulkcopy_arrow
    pycore_connection = mssql_py_core.PyCoreConnection(
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'mssql_py_core' has no attribute 'PyCoreConnection'

This reproduces on a clean pip install mssql-python==1.16.0 with no other code changes — the exact same script works correctly against 1.15.0.

Root cause

This looks like a packaging regression from the 1.16.0 change that split the Rust runtime out into a separate version-matched mssql-python-rs package (per the 1.16.0 release notes).

On Windows, after pip install mssql-python==1.16.0, the compiled extension lands at:

site-packages/mssql_py_core/mssql_py_core.pyd

There is no __init__.py inside site-packages/mssql_py_core/. As a result, import mssql_py_core resolves to an empty implicit namespace package (PEP 420) rather than loading the compiled extension — so mssql_py_core.PyCoreConnection doesn't exist at that path.

The compiled extension itself is fine and fully functional — it just needs to be imported one level deeper:

import mssql_py_core.mssql_py_core as core
print([a for a in dir(core) if "Connection" in a])
# -> ['PyAsyncConnection', 'PyCoreConnection']

But mssql_python/cursor.py's bulkcopy_arrow (and likely bulkcopy) does a plain top-level import mssql_py_core and then calls mssql_py_core.PyCoreConnection(...) directly, which hits the empty namespace package instead of the real module.

Likely fix: either (a) add an __init__.py to the mssql_py_core package in the mssql-python-rs wheel that re-exports from the nested mssql_py_core.mssql_py_core extension module, or (b) update mssql-python's internal imports to reference mssql_py_core.mssql_py_core explicitly.

Environment

  • mssql-python: 1.16.0 (regression; works correctly on 1.15.0)
  • mssql-python-rs: 0.3.0
  • mssql-python-odbc: 18.6.2.2
  • Python: 3.11.0
  • OS: Windows 10/11 (Windows-10-10.0.26200-SP0), x86_64
  • Install method: pip install mssql-python==1.16.0 (clean upgrade from 1.15.0 in an existing venv)

Reproduction steps

pip install mssql-python==1.16.0
python -c "
import mssql_python
cn = mssql_python.connect('SERVER=...;DATABASE=...;Trusted_Connection=yes;')
cur = cn.cursor()
cur.bulkcopy_arrow('some_table', some_pyarrow_record_batch_reader)
"

Minimal repro of the underlying import issue (no SQL Server connection needed):

import mssql_py_core
print(mssql_py_core.__file__)          # None -- confirms empty namespace package
print(hasattr(mssql_py_core, "PyCoreConnection"))  # False

import mssql_py_core.mssql_py_core as core
print(core.__file__)                   # points to the real .pyd
print(hasattr(core, "PyCoreConnection"))  # True

Expected behavior

import mssql_py_core should expose PyCoreConnection (and PyAsyncConnection) at the top level, as it presumably did before the 1.16.0 packaging split, so bulkcopy_arrow()/bulkcopy() work without modification.

Actual behavior

bulkcopy_arrow() / bulkcopy() are completely broken on 1.16.0 for Windows installs via pip, with no workaround short of pinning back to 1.15.0.

Impact

This blocks all bulk-copy / Arrow bulk-load workflows on 1.16.0. We've rolled back to 1.15.0 in the meantime.

Lingua principale
Python
Stelle
481
Fork
62
Merge medio
2g 16h
PR unite (30g)
15

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/mssql-python

Tutte le issue di microsoft/mssql-python

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.