summaryrefslogtreecommitdiff
path: root/numpy/f2py
Commit message (Collapse)AuthorAgeFilesLines
...
* ENH: testing: add SkipTest and KnownFailureExceptionEvgeni Burovski2015-11-162-9/+6
| | | | | | | | * 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
* MAINT: Dictionary litteralRémy Léone2015-11-071-4/+2
|
* BUG: Revert some import * fixes in f2py.Charles Harris2015-10-263-22/+15
| | | | | | | | | | | | | | | | 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.
* Merge pull request #6488 from charris/cleanup-6306Charles Harris2015-10-161-5/+2
|\ | | | | Cleanup 6306: BUG: allow extension of common blocks in numpy.f2py
| * BUG: allow extension of common blocks in numpy.f2pyAlexander Heger2015-10-161-5/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | BUG: Allow nested use of parameters for array dimensions in f2py.Alexander Heger2015-10-161-3/+4
|/ | | | | | | | | | | | | 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.
* STY: Break some long lines in numpy/f2py/*.py.Charles Harris2015-07-298-122/+50
| | | | | | | 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.
* STY: PEP8 fixes in numpy/f2py/tests.Charles Harris2015-07-256-24/+46
|
* STY: Make PEP8 fixes in numpy/f2pyCharles Harris2015-07-2515-3233/+4047
| | | | | Decided to bite the bullet on this one. The code is certainly more readable, so should be easier to fix if we need to.
* STY: Make pyflakes fixes in numpy/f2pyCharles Harris2015-07-2512-273/+405
|
* STY: PEP8 and pyflakes fixes for numpy/f2py/tests.Charles Harris2015-07-2511-258/+298
|
* BUG: revert use of !python for bdist_mpkg scriptsMatthew Brett2015-05-051-1/+1
| | | | | | 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.
* ENH: add bdist_mpkg, bdist_wininst to binary distsMatthew Brett2015-04-291-2/+3
| | | | | Add other binary distribution formats to list of build commands that should generate !python shebang lines.
* BUG: fix f2py shebang line for bdist wheel, eggMatthew Brett2015-04-291-1/+14
| | | | | | | | | 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.
* MANT: Use Py_RETURN_NONE whenever Py_None is returnedJaime Fernandez2015-04-241-2/+1
|
* Merge pull request #5565 from juliantaylor/pep338-f2pyJulian Taylor2015-03-092-26/+27
|\ | | | | ENH: make f2py an executable module
| * ENH: make f2py an executable moduleJulian Taylor2015-03-082-26/+27
| | | | | | | | allows pep 338 execution via python -mnumpy.f2py
* | BUG: Cannot read .f2py_f2cmaps under python 3.3David Powell2015-03-061-4/+4
|/ | | | | | | 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.
* Merge pull request #5309 from rgommers/remove-f2py-deprecationCharles Harris2015-01-062-5/+0
|\ | | | | MAINT: remove NPY_NO_DEPRECATED_API define from f2py.
| * MAINT: remove NPY_NO_DEPRECATED_API define from f2py.Ralf Gommers2014-11-232-5/+0
| | | | | | | | | | See gh-5281 for discussion. With the defines in, compiling scipy 0.14.0 and below isn't possible.
* | Merge pull request #5287 from chatcannon/reconcile-c-api-with-docsJulian Taylor2014-12-101-7/+10
|\ \ | |/ |/| | | Reconcile C API with docs
| * MAINT: cast PyArray_ITEMSIZE result to avoid warningsJulian Taylor2014-12-101-3/+3
| | | | | | | | return type depends on API version used
| * MAINT: Update printf statements in fortranobject.cChris Kerr2014-12-101-5/+8
| | | | | | | | Using NPY_INTP_FMT to format PyArray_ITEMSIZE
* | MAINT: change place where NPY_NO_DEPRECATED_API is defined in f2py.Ralf Gommers2014-11-163-2/+6
|/ | | | | 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.
* DEP: #declaring NPY_NO_DEPRECATED_API in fortranobject.hChris Kerr2014-11-101-0/+2
|
* DEP: removed deprecated API calls from test code (wrapmodule.c)Chris Kerr2014-11-101-31/+31
|
* DEP: Replace NPY_CONTIGUOUS with NPY_ARRAY_C_CONTIGUOUSChris Kerr2014-11-102-2/+2
|
* DEP: Corrected some type errors that appear when enabling NPY_NO_DEPRECATED_APIChris Kerr2014-11-101-7/+7
|
* DEP: Replaced NPY_[F,C]ARRAY with NPY_ARRAY_[F,C]ARRAYChris Kerr2014-11-102-6/+6
|
* DEP: Using the internal PyArrayObject_fields API for the swap_arrays and ↵Chris Kerr2014-11-101-2/+5
| | | | dump_attrs functions
* DEP: Using PyArray_SIZE and PyArray_TYPE instead of PyArray_DESCR()->elsize etcChris Kerr2014-11-101-5/+5
|
* DEP: Replaced arr->descr, arr->flags and arr->base with the PyArray_* functionsChris Kerr2014-11-104-20/+20
|
* DEP: replaced arr->dimensions with PyArray_DIMS(arr) or PyArray_DIM(arr,i)Chris Kerr2014-11-103-15/+15
|
* DEP: replaced arr->data with PyArray_DATAChris Kerr2014-11-104-52/+52
|
* DEP: replaced arr->nd with PyArray_NDIM in C code generation scriptsChris Kerr2014-11-102-7/+7
|
* DEP: Replaced arr->nd with PyArray_NDIM in fortranobject.cChris Kerr2014-11-101-18/+18
|
* MAINT: remove obsolete version checksJulian Taylor2014-10-151-17/+15
| | | | | minimum requirement is python2.6, this allows removing a couple 2.3 and 2.4 checks.
* Merge pull request #5168 from charris/f2py-space-fixCharles Harris2014-10-103-4/+47
|\ | | | | BUG: Make f2py work with intent(in out).
| * TST: Add basic test for compiling with intent(in out).Charles Harris2014-10-092-0/+41
| | | | | | | | | | This checks that the compilation works and that the expected error is raised when non-contiguous arrays are passed as intent(in out).
| * BUG: Make f2py work with intent(in out).Charles Harris2014-10-091-4/+6
| | | | | | | | | | | | | | Note that Fortran ignores spaces in this case, so that 'in out' is treated as 'inout'. Closes #479.
* | MAINT: f2py: rewrite fortran_docLars Buitinck2014-09-281-68/+124
| | | | | | | | | | | | | | | | | | 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.)
* | Changed the `goto fail` to a `return PyErr_NoMemory()`Chris Kerr2014-09-041-1/+4
| |
* | Add NULL check after malloc() in fortranobject.cChris Kerr2014-09-041-0/+1
| |
* | TST: skip clongdouble alignment checks on 32 bit archesJulian Taylor2014-09-031-3/+5
| | | | | | | | | | | | 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.
* | Merge pull request #5021 from charris/remove-missing-files-from-setupRalf Gommers2014-08-291-2/+0
|\ \ | | | | | | MAINT: Remove references to missing files from install.
| * | MAINT: Remove references to missing files from install.Charles Harris2014-08-291-2/+0
| |/ | | | | | | | | | | | | | | | | | | | | | | 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.
* | TST: win32 also does not provide 16 byte alignmentJulian Taylor2014-07-271-1/+1
| | | | | | | | | | mingw builds set the alignment requirement for complex doubles types to 16 byte so the tests checking the alignment flag must be disabled.
* | TST: disable tests that fail due to bad alignment on sparcJulian Taylor2014-07-021-35/+44
|/ | | | | | | (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.
* Merge pull request #4315 from charris/fix-gh-2408Charles Harris2014-02-201-8/+6
|\ | | | | BUG: #2408, Fix f2py Python 3 error message string bug.
| * BUG: #2408, Fix f2py Python 3 error message string bug.Charles Harris2014-02-171-8/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.