summaryrefslogtreecommitdiff
path: root/numpy/f2py
Commit message (Collapse)AuthorAgeFilesLines
...
* | 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.
* | Merge pull request #4305 from charris/fix-gh-4256Charles Harris2014-02-203-1/+30
|\ \ | | | | | | BUG: #4256: f2py, PyString_FromStringAndSize is undefined in Python3.
| * | BUG: #4256: f2py, PyString_FromStringAndSize is undefined in Python3.Charles Harris2014-02-163-1/+30
| |/ | | | | | | | | | | | | | | | | Use PyUString_FromStringAndSize defined in npy_3kcompat instead. Not using bytes may cause some problems, but strings seem like a better choice. As modules generated with current f2py error out, this particular use is not common and we are free to choose. Closes #4256.
* | BUG: Fix typo in f2py/cfuncs.py.Charles Harris2014-02-161-1/+1
|/ | | | | | | Replace "insinged_long_long" by "unsigned_long_long". Patch due to trac user pepijndevos. Closes #636.
* Merge pull request #4257 from juliantaylor/tostring-deprCharles Harris2014-02-141-1/+2
|\ | | | | ENH: add tobytes and stop using tostring in documentation
| * ENH: add tobytes and stop using tostring in documentationJulian Taylor2014-02-111-1/+2
| | | | | | | | | | | | | | tostring returns bytes which are not equal to string, so provide a tobytes function alias. tostring does not emit a deprecation warning yet so rdepends do not need to check two names to support older versions of numpy without warnings.
* | ENH: remove insecure mktemp useJulian Taylor2014-02-062-15/+15
|/ | | | | mktemp only returns a filename, a malicous user could replace it before it gets used.
* MAINT: fix some f2py related build warnings.Ralf Gommers2014-01-221-1/+1
|
* Merge pull request #4158 from rgommers/f2py-no-reloadCharles Harris2014-01-022-10/+41
|\ | | | | MAINT: remove use of ``reload`` from f2py. See gh-4139.
| * MAINT: remove use of ``reload`` from f2py. See gh-4139.Ralf Gommers2013-12-302-10/+41
| |
* | DOC: move f2py documentation under doc/ and link its user guide with SphinxPauli Virtanen2014-01-02101-11815/+0
| |
* | DOC: f2py manpage, use minus instead of hyphens for optionsJulian Taylor2014-01-021-2/+2
|/
* Changed CVS cens.ioc.ee documentation links to link to GitHubChris Kerr2013-11-121-8/+8
|
* Moved old news from README.txt to OLDNEWS.txtChris Kerr2013-11-122-47/+31
|
* Updated FAQ with links to github issues page etcChris Kerr2013-11-121-30/+18
| | | | Removed some questions that are no longer relevant
* crackfortran: changed string.lowercase to string.ascii_lowercaseochoadavid2013-10-241-1/+1
| | | Compatibility with Python3, which dosn't have string.lowercase.
* BUG: f2py, fix decref on wrong objectJulian Taylor2013-09-121-2/+3
| | | | | | missing brackets causes decref on an wrong object. shows itself as abort with negative refcount in test_callback using python-dbg.
* STY: Giant comma spacing fixup.Charles Harris2013-08-1828-1468/+1468
| | | | | | | Run the 2to3 ws_comma fixer on *.py files. Some lines are now too long and will need to be broken at some point. OTOH, some lines were already too long and need to be broken at some point. Now seems as good a time as any to do this with open PRs at a minimum.
* STY: Giant whitespace cleanup.Charles Harris2013-08-1822-180/+176
| | | | Now is as good a time as any with open PR's at a low.
* MAINT: Remove outdated version checks.Charles Harris2013-07-111-21/+0
| | | | | | | | | | Because Numpy 1.8.0 will no longer supports Python versions < 2.6 we no longer need to check for that and can also remove the code that is specific to those earlier versions. To make this a bit safer, the toplevel setup.py file now contains a check of the Python version number and raises an error when run by an unsupported version.
* BUG: f2py script shebang may refer to wrong pythonCarwyn Pelley2013-05-231-2/+2
| | | | | | | | | The f2py executable has a shebang which uses the default python, rather than the python it was compiled for. This causes issues for deployment of numpy (+f2py) across systems which have different environments. This fix uses sys.executable to determine the resulting hardcoded python to use.
* MAINT: Apply 2to3 idioms fixer.Charles Harris2013-05-028-53/+54
| | | | | | | | | | | | | | | | | | | The idioms fixer makes the following replacements. 1) int <- bool 2) comparison or identity of types <- isinstance 3) a.sort() <- sorted(a) There were two problems that needed to be dealt with after the application of the fixer. First, the replacement of comparison or identity of types by isinstance was not always correct. The isinstance function returns true for subtypes whereas many of the places where the fixer made a substitution needed to check for exact type equality. Second, the sorted function was applied to arrays, but because it treats them as iterators and constructs a sorted list from the result, that is the wrong thing to do. Closes #3062.
* 2to3: Apply types fixer.Charles Harris2013-04-146-67/+59
| | | | | | | | | | | | | | | | | | | | Python 3 removes the builtin types from the types module. The types fixer replaces such references with the builtin types where possible and also takes care of some special cases: types.TypeNone <- type(None) types.NotImplementedType <- type(NotImplemented) types.EllipsisType <- type(Ellipsis) The only two tricky substitutions are types.StringType <- bytes types.LongType <- int These are fixed up to support both Python 3 and Python 2 code by importing the long and bytes types from numpy.compat. Closes #3240.
* 2to3: Apply the `numliterals` fixer and skip the `long` fixer.Charles Harris2013-04-134-8/+12
| | | | | | | | | | | | | | | | | | | The numliterals fixer replaces the old style octal number like '01' by '0o1' removes the 'L' suffix. Octal values were previously mistakenly specified in some dates, those uses have been corrected by removing the leading zeros. Simply Removing the 'L' suffix should not be a problem, but in some testing code it looks neccesary, so in those places the Python long constructor is used instead. The 'long' type is no longer defined in Python 3. Because we need to have it defined for Python 2 it is added to numpy/compat/np3k.py where it is defined as 'int' for Python 3 and 'long' for Python 2. The `long` fixer then needs to be skipped so that it doesn't undo the good work. Closes #3074, #3067.
* replace exec by eval to ensure the c variable is defined for all relevant ↵Jos de Kloe2013-04-121-1/+1
| | | | python versions
* 2to3: Apply `map` fixer.Charles Harris2013-04-107-12/+15
| | | | | | | | | | | | | | | | | | | In Python 3 `map` is an iterator while in Python 2 it returns a list. The simple fix applied by the fixer is to inclose all instances of map with `list(...)`. This is not needed in all cases, and even where appropriate list comprehensions may be preferred for their clarity. Consequently, this patch attempts to use list comprehensions where it makes sense. When the mapped function has two arguments there is another problem that can arise. In Python 3 map stops execution when the shortest argument list is exhausted, while in Python 2 it stops when the longest argument list is exhausted. Consequently the two argument case might need special care. However, we have been running Python3 converted versions of numpy since 1.5 without problems, so it is probably not something that affects us. Closes #3068
* 2to3: Apply `repr` fixer.Charles Harris2013-04-0816-122/+122
| | | | | | | | | | | | This replaces python backtics with repr(...). The backtics were mostly used to generate strings for printing with a string format and it is tempting to replace `'%s' % repr(x)` with `'%r' % x`. That would work except where `x` happened to be a tuple or a dictionary but, because it would be significant work to guarantee that and because there are not many places where backtics are used, the safe path is to let the repr replacements stand. Closes #3083.
* Merge pull request #3205 from charris/2to3-apply-dict-fixerCharles Harris2013-04-074-52/+52
|\ | | | | 2to3: apply `dict` fixer.
| * 2to3: apply `dict` fixer.Charles Harris2013-04-064-52/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In Python3 `dict.items()`, `dict.keys()`, and `dict.values()` are iterators. This causes problems when a list is needed so the 2to3 fixer explicitly constructs a list when is finds on of those functions. However, that is usually not necessary, so a lot of the work here has been cleaning up those places where the fix is not needed. The big exception to that is the `numpy/f2py/crackfortran.py` file. The code there makes extensive use of loops that modify the contents of the dictionary being looped through, which raises an error. That together with the obscurity of the code in that file made it safest to let the `dict` fixer do its worst. Closes #3050.
* | Merge pull request #3202 from charris/2to3-reduce-fixupsnjsmith2013-04-071-2/+1
|\ \ | |/ |/| MAINT: Cleanup some imports involving reduce.
| * MAINT: Cleanup some imports involving reduce.Charles Harris2013-04-061-2/+1
| | | | | | | | | | | | | | | | | | | | Because reduce has been available in functools since Python 2.6 we can get rid of the version checks we currently have before we import it. Also removes some reduce related skips in tools/py3tool.py. We were already skipping the reduce fixer so this has no effect other than cleaning up the code.
* | 2to3: Apply `print` fixer.Charles Harris2013-04-0632-122/+122
|/ | | | | | | Add `print_function` to all `from __future__ import ...` statements and use the python3 print function syntax everywhere. Closes #3078.
* 2to3: Apply `imports` fixer.Charles Harris2013-04-022-3/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The `imports` fixer deals with the standard packages that have been renamed, removed, or methods that have moved. cPickle -- removed, use pickle commands -- removed, getoutput, getstatusoutput moved to subprocess urlparse -- removed, urlparse moved to urllib.parse cStringIO -- removed, use StringIO or io.StringIO copy_reg -- renamed copyreg _winreg -- renamed winreg ConfigParser -- renamed configparser __builtin__ -- renamed builtins In the case of `cPickle`, it is imported as `pickle` when python < 3 and performance may be a consideration, but otherwise plain old `pickle` is used. Dealing with `StringIO` is a bit tricky. There is an `io.StringIO` function in the `io` module, available since Python 2.6, but it expects unicode whereas `StringIO.StringIO` expects ascii. The Python 3 equivalent is then `io.BytesIO`. What I have done here is used BytesIO for anything that is emulating a file for testing purposes. That is more explicit than using a redefined StringIO as was done before we dropped support for Python 2.4 and 2.5. Closes #3180.
* 2to3: Use absolute imports.Charles Harris2013-03-2831-78/+78
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The new import `absolute_import` is added the `from __future__ import` statement and The 2to3 `import` fixer is run to make the imports compatible. There are several things that need to be dealt with to make this work. 1) Files meant to be run as scripts run in a different environment than files imported as part of a package, and so changes to those files need to be skipped. The affected script files are: * all setup.py files * numpy/core/code_generators/generate_umath.py * numpy/core/code_generators/generate_numpy_api.py * numpy/core/code_generators/generate_ufunc_api.py 2) Some imported modules are not available as they are created during the build process and consequently 2to3 is unable to handle them correctly. Files that import those modules need a bit of extra work. The affected files are: * core/__init__.py, * core/numeric.py, * core/_internal.py, * core/arrayprint.py, * core/fromnumeric.py, * numpy/__init__.py, * lib/npyio.py, * lib/function_base.py, * fft/fftpack.py, * random/__init__.py Closes #3172
* 2to3: Replace xrange by range and use list(range(...)) where neededCharles Harris2013-03-272-2/+2
| | | | | | | | | | | | | | | In python3 range is an iterator and `xrange` has been removed. This has two consequence for code: 1) Where a list is needed `list(range(...))` must be used. 2) `xrange` must be replaced by `range` Both of these changes also work in python2 and this patch makes both. There are three places fixed that do not need it, but I left them in so that the result would be `xrange` clean. Closes #3092
* Merge pull request #3014 from bfroehle/f2py_unque_symbolCharles Harris2013-03-011-1/+1
|\ | | | | BUG: Choose a more unique PY_ARRAY_UNIQUE_SYMBOL in f2py.
| * BUG: Choose a more unique PY_ARRAY_UNIQUE_SYMBOL in f2py.Bradley M. Froehle2013-02-241-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | In a few exceptional cases where symbols are shared between different Python modules the use of `PyArray_API` in f2py (fortranobject.h) conflicts with the regular use of the same symbol in the multiarray module. Generally the symptom of this conflicting use is a segfault when importing a f2py'ed module. This occurs because the module init code somehow overwrites the first element of `PyArray_API` with the location of `PyArray_API`, causing a crash when `PyArray_GetNDArrayCVersion` is called. Closes gh-2521.
* | MAINT: Make numpy/f2py/crackfortran docstring read better.Charles Harris2013-03-011-13/+12
| | | | | | | | | | The copyright and short summary were moved to the top of the docstring with the usage description below.
* | 2to3: Put `from __future__ import division in every python file.Charles Harris2013-03-0132-128/+189
| | | | | | | | | | | | | | | | This should be harmless, as we already are division clean. However, placement of this import takes some care. In the future a script can be used to append new features without worry, at least until such time as it exceeds a single line. Having that ability will make it easier to deal with absolute imports and printing updates.
* | Merge pull request #3056 from charris/2to3-filterCharles Harris2013-03-011-12/+18
|\ \ | | | | | | 2to3: Apply `filter` fixes. Closes #3053.
| * | BUG: Fix `not a in ...` to `a not in ...`.Charles Harris2013-02-281-14/+15
| | | | | | | | | | | | Also break regular expression compiles out of the loop.
View Lorry Controller Status