| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \ \
| | | | |
| | | | | |
Merge with distutils@8c3c3d29
|
| | | | | |
|
| |\ \ \ \
|/ / / / /
| | | | _ |
|
| |\ \ \
| | | | |
| | | | | |
Fixed accumulating include dirs after compile
|
| | | | |
| | | | |
| | | | |
| | | | | |
- fixes https://github.com/pypa/setuptools/issues/3591
|
| |\ \ \ \
| | | | | |
| | | | | | |
add a pypy CI run
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
distutils.ccompiler: Remove correct executable file on Windows
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The previous code did not take into account the .exe file extension
on Windows.
|
| |\ \ \ \ \ \
| | |/ / / / /
| |/| | | | | |
Fix MinGW-w64 segmentation fault (v2)
|
| | | |/ / /
| | |/| | | |
|
| |/ / / / |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This reverts commit 0171aee1bc0e5811d710e6d9253ec80556817095, reversing
changes made to fb2a173bcd783040a36ca20c41b967f0673c56a3.
|
| |\ \ \ \
| | | | | |
| | | | | | |
distutils.ccompiler: Make has_function work with more C99 compilers
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
C99 removed support for implicit function declarations. This means
that just calling a function, without declaring the function first,
can result in a compilation error. Today, has_function works with
most compilers because they issue just a warning, create an object
file, and attempt a link, which then detects available of the symbol
at link time, as intended. With future compilers, compilation will
already fail, and no link test is performed.
The has_function interface provides the caller with a way to supply
a list of header files to include. However, even with today's
compilers, this only works if the function does not expect any
parameters. Otherwise, the function call in the C fragment created
by has_function will not supply the correct argument list and fail
compilation. Therefore, this change supplies and incorrect prototype
without arguments. This is what autoconf does today in a very
similar situation, so it is quite likely that compilers will support
this construct in this context in the future.
The includes and include_dirs arguments are deprecated because of
the parameter list mismatch issue.
Fixes pypa/setuptools#3648.
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
Add `tests/test*.py` to source distributions
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Because most Python packages maintain tests in top-level directory
`tests/` instead of `test/`, add both to source distributions for
consistency.
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Fix typos found by codespell
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| | |/ / / / / /
| |/| | | | | | |
Fix MinGW-w64 segmentation fault
|
| | | |/ / / /
| | |/| | | | |
|
| |\ \ \ \ \ \
| | |_|_|/ / /
| |/| | | | | |
For 'get_python_inc', bypass missing config include dir
|
| | | | | | | |
|
| | |\ \ \ \ \ |
|
| | | |/ / / / |
|
| | |/ / / /
| | | | | |
| | | | | |
| | | | | | |
Fixes pypa/distutils#178.
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
Update outdated GitHub Actions
|
| | |/ / / / |
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
Apply refurb suggestions
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
[FURB109]: Replace `in [x, y, z]` with `in (x, y, z)`
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
[FURB131]: Replace `del x[y]` with `x.pop(y)`
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
[FURB108]: Use `x in (y, z)` instead of `x == y or x == z`
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
[FURB113]: Use `x.extend(...)` instead of repeatedly calling `x.append()`
|
| | |/ / / /
| | | | | |
| | | | | |
| | | | | | |
[FURB123]: Replace `str(x)` with `x`
|
| |\ \ \ \ \
| | |/ / / /
| |/| | | | |
Link directly to PEP
|
| |/ / / / |
|
| | | | | |
|
|\ \ \ \ \ |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | |_|_|/
| |/| | | |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
PR MESSAGE:
This is a difference between pip's legacy wheel build (or direct
invocations of setup.py) and the PEP 517 build.
While setup.py scripts that rely on this are fragile, it was quite
painful to debug! Since Python 3.4, __file__ is usually an absolute
path, so this change might result in fewer surprises.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is a difference between pip's legacy wheel build (or direct
invocations of setup.py) and the PEP 517 build.
While setup.py scripts that rely on this are fragile, it was quite
painful to debug! Since Python 3.4, `__file__` is usually an absolute
path, so this change might result in fewer surprises.
|
|/ / / / |
|
|\ \ \ \ |
|