| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
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.
|
|\ \
| | |
| | | |
BUG: #4256: f2py, PyString_FromStringAndSize is undefined in Python3.
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/
|
|
|
|
|
| |
Replace "insinged_long_long" by "unsigned_long_long". Patch due to trac
user pepijndevos.
Closes #636.
|
|\
| |
| | |
ENH: add tobytes and stop using tostring in documentation
|
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/
|
|
|
| |
mktemp only returns a filename, a malicous user could replace it before
it gets used.
|
| |
|
|\
| |
| | |
MAINT: remove use of ``reload`` from f2py. See gh-4139.
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
| |
Removed some questions that are no longer relevant
|
|
|
| |
Compatibility with Python3, which dosn't have string.lowercase.
|
|
|
|
|
|
| |
missing brackets causes decref on an wrong object.
shows itself as abort with negative refcount in test_callback using
python-dbg.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Now is as good a time as any with open PR's at a low.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
python versions
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|