GH-45867: [Python] Fix SetuptoolsDeprecationWarning#47141
GH-45867: [Python] Fix SetuptoolsDeprecationWarning#47141pitrou merged 17 commits intoapache:mainfrom
SetuptoolsDeprecationWarning#47141Conversation
|
|
|
|
| # versions released after 2022 | ||
| "setuptools_scm[toml]>=8", | ||
| "setuptools>=64", | ||
| "setuptools>=77", |
There was a problem hiding this comment.
This is required due to setuptools<77 not recognizing the new license strings proposed in this PR (see pypa/setuptools#4903 for explanation). I'm not sure if this is controversial so bringing it up here. @raulcd
|
@github-actions crossbow submit |
|
|
@github-actions crossbow submit -g python -g wheels |
|
|
@github-actions crossbow submit -g python |
|
Revision: 6b1a08b Submitted crossbow builds: ursacomputing/crossbow @ actions-2fdf3226a1 |
python/LICENSE.txt
Outdated
There was a problem hiding this comment.
Does symbolic link work on Windows...?
There was a problem hiding this comment.
Good point. I guess there's no other way to fix it then other than copying or creating new licence and notice files.
There was a problem hiding this comment.
Have copied over the files for the tests @rok
There was a problem hiding this comment.
Short version: there is no exact equivalent for POSIX symlinks on Windows, and the closest thing is unavailable for non-admins by default unless Developer Mode is enabled and a relatively recent Windows 10 version is used. Therefore, symlink emulation support is only turned on by default when that scenario is detected. Support can be enabled by the user, via the core.symlinks=true config setting.
Windows 10 reached EOL last month, and supposedly Developer Mode is required for Visual Studio use.
I'm not sure of all the Windows workflows that may / may not require developer mode, but maybe its worth just requiring it for any Windows devs of PyArrow so that symlinks can be used?
|
@github-actions crossbow submit -g wheel |
SetuptoolsDeprecationWarningSetuptoolsDeprecationWarning
|
|
|
Revision: 6b1a08b Submitted crossbow builds: ursacomputing/crossbow @ actions-fe79dfe84b |
|
The macOS segfaults are expected and unrelated. |
|
@github-actions crossbow submit -g python |
|
@github-actions crossbow submit wheelcp313* |
|
Revision: e47ca7c Submitted crossbow builds: ursacomputing/crossbow @ actions-1176ee40f3 |
|
Revision: e47ca7c Submitted crossbow builds: ursacomputing/crossbow @ actions-8124fa0f6c |
|
CI failures are unrelated, thanks a lot @paddyroddy ! |
|
@github-actions crossbow submit python-sdist |
|
Revision: e47ca7c Submitted crossbow builds: ursacomputing/crossbow @ actions-b1e74a8dee
|
|
After merging your PR, Conbench analyzed the 2 benchmarking runs that have been run so far on merge-commit 866502e. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 1 possible false positive for unstable benchmarks that are known to sometimes produce them. |
Rationale for this change
When building locally, I get many errors along the lines of
What changes are included in this PR?
setup.cfgtopyproject.tomlsetuptoolsdue to macOS CI failures (don't know why this happened, caching maybe?)I appreciate the symlink change might prove controversial. See discussions in #45867, fixes #45867.
Are these changes tested?
When I rebuild locally, I get no errors any more.
Are there any user-facing changes?
Yes. The minimum required version of
setuptoolsis now77. However, this is available on>=3.9so won't affect anyone really.