bpo-41744: Package NuGet python.props with correct name to be used by vslavik · Pull Request #22154 · python/cpython
Conversation
NuGet automatically includes .props file from the build directory in the target using the package, but only if the .props file has the correct name: it must be $(id).props Rename python.props correspondingly in all the nuspec variants. Also keep python.props as it were for backward compatibility.
miss-islington added a commit to miss-islington/cpython that referenced this issue
Sep 14, 2020
…ythonGH-22154) NuGet automatically includes .props file from the build directory in the target using the package, but only if the .props file has the correct name: it must be $(id).props Rename python.props correspondingly in all the nuspec variants. Also keep python.props as it were for backward compatibility. (cherry picked from commit 7c11a9a) Co-authored-by: Václav Slavík <vaclav@slavik.io>
miss-islington added a commit to miss-islington/cpython that referenced this issue
Sep 14, 2020
…ythonGH-22154) NuGet automatically includes .props file from the build directory in the target using the package, but only if the .props file has the correct name: it must be $(id).props Rename python.props correspondingly in all the nuspec variants. Also keep python.props as it were for backward compatibility. (cherry picked from commit 7c11a9a) Co-authored-by: Václav Slavík <vaclav@slavik.io>
miss-islington added a commit that referenced this issue
Sep 14, 2020…H-22154) NuGet automatically includes .props file from the build directory in the target using the package, but only if the .props file has the correct name: it must be $(id).props Rename python.props correspondingly in all the nuspec variants. Also keep python.props as it were for backward compatibility. (cherry picked from commit 7c11a9a) Co-authored-by: Václav Slavík <vaclav@slavik.io>
xzy3 pushed a commit to xzy3/cpython that referenced this issue
Oct 18, 2020
…ythonGH-22154) NuGet automatically includes .props file from the build directory in the target using the package, but only if the .props file has the correct name: it must be $(id).props Rename python.props correspondingly in all the nuspec variants. Also keep python.props as it were for backward compatibility.
methane pushed a commit that referenced this issue
Oct 21, 2020…H-22154) NuGet automatically includes .props file from the build directory in the target using the package, but only if the .props file has the correct name: it must be $(id).props Rename python.props correspondingly in all the nuspec variants. Also keep python.props as it were for backward compatibility. (cherry picked from commit 7c11a9a) Co-authored-by: Václav Slavík <vaclav@slavik.io>
chrisburr added a commit to chrisburr/cpython that referenced this issue
Dec 9, 2020
…ythonGH-22154) NuGet automatically includes .props file from the build directory in the target using the package, but only if the .props file has the correct name: it must be $(id).props Rename python.props correspondingly in all the nuspec variants. Also keep python.props as it were for backward compatibility.