You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
---------------------------------------------------------------------------
TypeError Traceback (most recent call last)
<ipython-input-60-186ab71ceb04> in <module>()
6 location=EarthLocation(-2446354, 4237210, 4077985, unit='m'))
7 t['b'] = [3, 1]
----> 8 t.sort('b')
~/conda-main/envs/ipyfits/lib/python3.6/site-packages/astropy/table/table.py in sort(self, keys)
2475
2476 for col in self.columns.values():
-> 2477 col[:] = col.take(indexes, axis=0)
2478
2479 if sort_index is not None:
TypeError: 'Time' object does not support item assignment
(Apologies if all of the issues I'm opening here are known issues or the expected behavior)
@mwcraig - I suspect it's not, I vaguely remember the sorting is relying on a new feature/API change added after the LTS (but somehow cannot find the PRs now).
Activity
taldcroft commentedon Nov 3, 2018
Is this for master? It should be working, and that's what I see:
mwcraig commentedon Nov 4, 2018
Sorry, forgot to check both master and the latest release. Looks like it is fixed in master, broken in 3.0.5, so feel free to close.
mwcraig commentedon Nov 4, 2018
@taldcroft -- one question about this one...sorting by a
Timecolumn fails in LTS. Is this a fix that should be backported?bsipocz commentedon Nov 4, 2018
@mwcraig - I suspect it's not, I vaguely remember the sorting is relying on a new feature/API change added after the LTS (but somehow cannot find the PRs now).
taldcroft commentedon Nov 4, 2018
Yes sorting relies on Time being mutable which is a new feature of 3.1!