Tags from casa

casa3k-5.6.3_1

2020-08-07T23:04:50Z

casa3k-5.6.3_0

2020-08-07T23:04:50Z

casa3k-5.4.1_4

2019-07-25T16:39:09Z

code/CMakeLists.txt: old hand-rolled Boost detection broke; use CMake…

…'s scheme

casa3k-5.4.1_3

2019-07-25T16:39:09Z

code/CMakeLists.txt: old hand-rolled Boost detection broke; use CMake…

…'s scheme

casa3k-5.4.1_2: gcwrap: fix Python modules on macOS/py37

2019-02-07T19:58:35Z

gcwrap: fix Python modules on macOS/py37

The problem is that now, if a module links with libpython, you will get a
segfault. This seems to be the case not only for the various CASA Python
extension modules themselves but also for CASA's `libtools.dylib`, which they
link to. I've copied the linker flags manually since I can't figure out how to
figure them out on-the-fly in any reasonable way.

TEMP-WORKED

2019-02-07T17:06:46Z

casa3k-5.4.1_1

2018-09-25T18:15:05Z

casa3k-5.4.1_0

2018-09-25T18:15:05Z

casa3k-5.1.2_0

2018-02-09T04:11:39Z

casa3k-5.1.1_3: gcwrap/tools/StdCasa/conversions_python.cc: map strings to lists

2017-11-02T17:10:21Z

gcwrap/tools/StdCasa/conversions_python.cc: map strings to lists

Previously CASA would map C++ strings to numpy arrays with byte-sequence
dtypes. This is OK in Python 2, but in Python 3 these values don't stringify
nicely: `str(value) = "b'BLAH'"`. So, special-case string arrays to be
rendered into standard lists rather than Numpy arrays, since we already have
the machinery to Unicode-ify them correctly in either Python 2 or 3.