| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
* use SkipTest in numpy tests instead of importing it from nose
* add a KnownFailureException as an alias for KnownFailureTest
(the former is preferred, but the latter is kept for backcompat)
* rename the KnownFailure nose plugin into KnownFailurePlugin,
and keep the old name for backcompat
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The files
* capi_maps.py
* crackfortran.py
* f90mod_rules.py
previously used `from .auxfuncs import *` and also called `eval`
without an explicit enviroment. An attempt to use explicit imports
led to errors, and because static code analysis in not sufficient
to determine what functions need to be imported, it is safest to
continue using `import *` pending a major refactoring of f2py.
Closes #6563.
|
|\
| |
| | |
Cleanup 6306: BUG: allow extension of common blocks in numpy.f2py
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Lack of this feature resulted in the generation of incorrect *.pyf
files.
For example, the pyf file created by:
subroutine sub3 (some arguments)
real a, b, c, d
common /coeff/ a, b
common /coeff/ c, d
<do stuff>
return
end
Should contain both common statements the declaration of all four
variables a, b, c, and d.
Closes #5876.
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
Nested use of parameters in specifying dimensions caused problems.
For example
parameter (i=7)
common buf(nvar*(nvar+1) * (n + 1))
This fix was suggested by Pearu on github.
Closes #5877.
|
|
|
|
|
|
|
| |
The fixes are generated by autopep8, which uses line continuation.
There are 441 cases that it is unable to handle, involving strings, and
that is more, and more delicate, work than I want to do at this time.
The line continuation characters at least mark some of the long lines.
|
| |
|
|
|
|
|
| |
Decided to bite the bullet on this one. The code is certainly more
readable, so should be easier to fix if we need to.
|
| |
|
| |
|
|
|
|
|
|
| |
bdist_mpkg is a very crude install method that will assume the path to
Python, so we should not use the `#!python` form when installing scripts
in bdist_mpkg.
|
|
|
|
|
| |
Add other binary distribution formats to list of build commands that
should generate !python shebang lines.
|
|
|
|
|
|
|
|
|
| |
Command `bdist_wheel` was generating a shebang line for f2py that uses
the Python path for the building Python. If we are building a wheel or
an egg, use the generic `#!python` shebang line for the f2py script
instead, which setuptools will modify at install time.
Closes gh-5812.
|
| |
|
|\
| |
| | |
ENH: make f2py an executable module
|
| |
| |
| |
| | |
allows pep 338 execution via python -mnumpy.f2py
|
|/
|
|
|
|
|
| |
When reading .f2py_f2cmaps, these is iteration over dictionaries keys()
and items(), which are iterators in python 3. This prohibits modifying the
dicionaries while iterating. By wrapping these calls with list(), the python 2
behaviour is restored. Fixes #5637.
|
|\
| |
| | |
MAINT: remove NPY_NO_DEPRECATED_API define from f2py.
|
| |
| |
| |
| |
| | |
See gh-5281 for discussion. With the defines in, compiling scipy 0.14.0 and
below isn't possible.
|
|\ \
| |/
|/|
| | |
Reconcile C API with docs
|
| |
| |
| |
| | |
return type depends on API version used
|
| |
| |
| |
| | |
Using NPY_INTP_FMT to format PyArray_ITEMSIZE
|
|/
|
|
|
| |
This makes sure to undef at the end, and by putting the define in the
C code it ensures that the error message is understandable.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
dump_attrs functions
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
minimum requirement is python2.6, this allows removing a couple 2.3 and
2.4 checks.
|
|\
| |
| | |
BUG: Make f2py work with intent(in out).
|
| |
| |
| |
| |
| | |
This checks that the compilation works and that the expected error
is raised when non-contiguous arrays are passed as intent(in out).
|
| |
| |
| |
| |
| |
| |
| | |
Note that Fortran ignores spaces in this case, so that 'in out' is
treated as 'inout'.
Closes #479.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Should not use sprintf, and certainly not with incorrect error checking
(gh-5044). Entirely rewritten for readability.
Also replaced a few sprintf calls that were just copying strings without
interpretation by the simpler and possibly faster strcpy/strcat.
(These need to be replaced by something more sensible.)
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
turns out not only sparc is borked, skip the checks on all 32 bit arches
with too large clongdouble alignments until we have an aligned
allocator.
|
|\ \
| | |
| | | |
MAINT: Remove references to missing files from install.
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The following directories and files have been moved or deleted
numpy/lib/benchmarks
numpy/f2py/docs
numpy/f2py/f2py.1
This PR removes references to them from the relevant setup.py files.
Closes #5010.
|
| |
| |
| |
| |
| | |
mingw builds set the alignment requirement for complex doubles types to
16 byte so the tests checking the alignment flag must be disabled.
|
|/
|
|
|
|
|
| |
(debian) sparc system malloc does not provide the alignment required by 16 byte
long double types this means the inout intent cannot be satisfied and several
tests fail as the alignment flag can be randomly true or fals when numpy gains
an aligned allocator the tests could be enabled again.
|
|\
| |
| | |
BUG: #2408, Fix f2py Python 3 error message string bug.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The original was generating an exception message and, after aliasing,
calling PyBytes_AsString on a unicode string -> error. It was also
leaking references, although that probably didn't matter in context.
The fix here is on the cheap side, just use a C string for the message
without including the extra information about the erroneous type that
led to the exception.
No test, I don't know how to evoke this error.
Closes #2408.
|