bpo-32635: Fix a segfault when importing the crypt module with libxcrypt. by stratakis · Pull Request #5284 · python/cpython

@stratakis

…rypt.

glibc is deprecating libcrypt in favor of libxcrypt, however python assumes
that crypt.h will always be included. This change makes the header inclusion
explicit when libxcrypt is present on the system.

vstinner

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request

Jan 24, 2018
…ypt. (pythonGH-5284)

glibc is deprecating libcrypt in favor of libxcrypt, however python assumes
that crypt.h will always be included. This change makes the header inclusion
explicit when libxcrypt is present on the system.
(cherry picked from commit e768c86)

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request

Jan 24, 2018
…ypt. (pythonGH-5284)

glibc is deprecating libcrypt in favor of libxcrypt, however python assumes
that crypt.h will always be included. This change makes the header inclusion
explicit when libxcrypt is present on the system.
(cherry picked from commit e768c86)

vstinner pushed a commit that referenced this pull request

Jan 24, 2018
…ypt. (GH-5284) (#5295)

glibc is deprecating libcrypt in favor of libxcrypt, however python assumes
that crypt.h will always be included. This change makes the header inclusion
explicit when libxcrypt is present on the system.
(cherry picked from commit e768c86)

vstinner pushed a commit that referenced this pull request

Jan 24, 2018
…ypt. (GH-5284) (#5296)

glibc is deprecating libcrypt in favor of libxcrypt, however python assumes
that crypt.h will always be included. This change makes the header inclusion
explicit when libxcrypt is present on the system.
(cherry picked from commit e768c86)