Skip to content

(WIP) Fix in-place updates to binary table columns of unsigned ints - #4709

Closed
embray wants to merge 2 commits into
astropy:masterfrom
embray:fix-table-uint-update
Closed

embray wants to merge 2 commits into
astropy:masterfrom
embray:fix-table-uint-update

Conversation

@embray

@embray embray commented Mar 18, 2016

Copy link
Copy Markdown
Member

This is a work-in-progress fix to the issue reported on Stack Overflow here: http://stackoverflow.com/questions/35921060/updating-pyfits-bin-table-data#35921060

I believe this might also be the same issue as #3921, but as the use case in that issue is slightly different I'm not 100% sure (nevertheless it still relates to updating unsigned int data in a table).

Right now this PR only contains the regression test, and some preliminary code cleanup that I realized was possible. I haven't had time to complete the fix yet. But if someone else wants to look into it I can point you in the right direction.

embray added 2 commits March 18, 2016 10:12
…hat always nice? This handling of unsigned ints already happens in FITS_rec.from_columns, by way of Column._convert_to_valid_data_type.
@embray
embray force-pushed the fix-table-uint-update branch from 62307c1 to 5eb6e55 Compare March 18, 2016 09:13
@embray

embray commented Mar 18, 2016

Copy link
Copy Markdown
Member Author

Rebased on latest master--apparently I was working off a relatively old master. Note the CI for this PR will still fail for now as I've only added the regression test but not the fix yet.

@pllim

pllim commented May 11, 2017

Copy link
Copy Markdown
Member

Incomplete and unlikely to be worked on anymore. Original issue #3921 still open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants