You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BUG: use internal linkage (static variables) in move.c (pandas-dev#24113)
* BUG: use internal linkage (static variables) in move.c
move.c declared global variables without explicitly declaring them static, so
they had global visibility. This meant that if you linked against a shared
object that provided the same symbols, the wrong data would be read. In
particular: linking to libgtk, which provides the symbol 'methods', would cause
an import error of pandas.util._move.
* DOC: whatsnew entry for pandas.util._move static variables
Copy file name to clipboardExpand all lines: doc/source/whatsnew/v0.24.0.rst
+1
Original file line number
Diff line number
Diff line change
@@ -1591,6 +1591,7 @@ Other
1591
1591
- Logical operations ``&, |, ^`` between :class:`Series` and :class:`Index` will no longer raise ``ValueError`` (:issue:`22092`)
1592
1592
- Checking PEP 3141 numbers in :func:`~pandas.api.types.is_scalar` function returns ``True`` (:issue:`22903`)
1593
1593
- Bug in :meth:`DataFrame.combine_first` in which column types were unexpectedly converted to float (:issue:`20699`)
1594
+
- Bug where C variables were declared with external linkage causing import errors if certain other C libraries were imported before Pandas. (:issue:`24113`)
0 commit comments