| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Harmonizes patterns a bit as well
|
| |
|
|\
| |
| | |
BUG: Infer return types for Fortran functions in `f2py`
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| |_|/
|/| | |
MAINT: remove redundant open() modes and io.open() alias
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
also made the threshold for rejecting a regex as too slow
much more lenient.
200ms should be enough time even for a bad CPU on a bad day.
a bad regex should fail with near certainty
|
|\ \ \
| |_|/
|/| | |
BUG: Fix bug in parsing F77 style string arrays.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Example problematic variable: CHARACTER WORDARR(3)*8
This would be wrapped by an array with shape (3, 8) and dtype |S1,
instead of the desired shape (3,) and dtype |S8.
See #23356.
|
| | | |
|
| | | |
|
| | |
| | |
| | | |
This is similar to #15248, removing the remaining usages of sys.exc_info() that are no longer necessary.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
My first replacement regex would have failed to match
cases like '@)@bind foo bar baz@(@@)@' which should
apparently be matched.
Added a test to make sure the regex does this.
|
| | | |
|
| | | |
|
|/ / |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
in previous version, any string scalar was converted to a string array of dimension len, i.e., a definition
character(len=N) :: X
effectively became
character(len=NNN), dimension(NNN) :: X
from the point of few of the numpy (python) interface:
X.shape == (NNN,)
X.dtype == '|SNNN'
Closes gh-23192
|
| |
| |
| |
| | |
Matti was wondering where it came from, so lets comment it out.
|
|\ \
| | |
| | | |
CI: Rebase NumPy compiled extension test modules on Cygwin
|
| | |
| | |
| | |
| | |
| | | |
This assumes NumPy is rebased before tests run,
but does not assume the locations are in the database.
|
| | |
| | |
| | |
| | |
| | | |
Also adjust CI so they don't immediately collide with NumPy.
I forgot to do that last time, which caused problems.
|
| | |
| | |
| | |
| | | |
This reverts commit 33709afdbbc47b7adb7dd06a730246d8c02f724f.
|
| | |
| | |
| | |
| | | |
This reverts commit 608864613b801b9c85573186a9d07eeac5e7e465.
|
| | |
| | |
| | |
| | | |
Forgot to check this earlier.
|
| | |
| | |
| | |
| | | |
Let's see if this fixes the 8-50 fork failures.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This clears the error holding only to the type. Since in the other
path the errmessage seemed completely uninitialized, I opted to just
ignore it entirely and keep the old error.
I could fathom to use error chaining here, but overall, I am not even
sure that chaining makes even sense for these errors. This fix is
meant to be minimal (the second one, I just noticed randomly), it
does not make this code clean.
|
| |
| |
| |
| |
| |
| |
| | |
Updates the free format handling of .f90 and other common extensions (through a minor re-write). Also removes an unused function.
This disallows previously allowed (but highly unlikely to be present) code-paths, namely having fixed form F77 code in a fortran 90 file (with .f90).
Co-authored-by: Sebastian Berg <sebastianb@nvidia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
(#22872)
* BUG: Use whole file for encoding checks [f2py]
* DOC: Add a code comment
Co-authored-by: melissawm <melissawm@gmail.com>
* TST: Add a conditional unicode f2py test
* MAINT: Add chardet as a test requirement
* ENH: Cleanup and switch f2py to charset_normalizer
* MAINT: Remove chardet for charset_normalizer
* TST: Simplify UTF-8 encoding [f2py]
Co-authored-by: melissawm <melissawm@gmail.com>
|
|/ |
|
|\
| |
| | |
MAINT: change subprocess arguments from Python>=3.7
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
| |
In some cases, the replacement is clearly not what is intended,
in those (where setup was called explicitly), I mostly renamed
`setup` to `_setup`.
The `test_ccompile_opt` is a bit confusing, so left it right now
(this will probably fail)
|
|\
| |
| | |
DEP: Deprecate conversion of out-of-bound Python integers
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was giving many warnings like this one in the SciPy build:
```
scipy/special/_specfunmodule.c: In function 'complex_double_from_pyobj':
scipy/special/_specfunmodule.c:198:47: warning: passing argument 1 of 'PyArray_DATA' from incompatible pointer type [-Wincompatible-pointer-types]
198 | (*v).r = ((npy_cdouble *)PyArray_DATA(arr))->real;
| ^~~
| |
| PyObject * {aka struct _object *}
In file included from /home/rgommers/code/numpy/numpy/core/include/numpy/ndarrayobject.h:12,
from /home/rgommers/code/numpy/numpy/core/include/numpy/arrayobject.h:5,
from /home/rgommers/code/numpy/numpy/f2py/src/fortranobject.h:16,
from scipy/special/_specfunmodule.c:22:
/home/rgommers/code/numpy/numpy/core/include/numpy/ndarraytypes.h:1524:29: note: expected 'PyArrayObject *' {aka 'struct tagPyArrayObject *'} but argument is of type 'PyObject *' {aka 'struct _object *'}
1524 | PyArray_DATA(PyArrayObject *arr)
| ~~~~~~~~~~~~~~~^~~
```
Fixing pointer mismatches is important for Pyodide/Emscripten.
|