QTable should pass all Table tests that do not involve masking
See original GitHub issueThis implies getting other issues to work, e.g., vstack
of Quantity
(#4599)
EDIT: to clarity, the hope is to get all tests on Table
that do not involve any masking to work on QTable
as well. This would presumably only imply that quantity columns can do everything that a regular Column
can (except turning itself into a masked version).
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
QTableWidget with a masked password column - Stack Overflow
One possible solution is to change the displayed text through a delegate: from PyQt5 import QtWidgets class PasswordDelegate(QtWidgets.
Read more >Unified File Read/Write Interface — Astropy v5.2
It is possible to store not only standard Column objects to a FITS table HDU, but also any astropy native objects (Mixin Columns)...
Read more >Source code for astropy.table.table
The returned # Table object should NOT then be copied (though the meta # will be deep-copied anyway). data = data.__astropy_table__(self.__class__, copy, ...
Read more >Table-to-Table Synchronization Rules - Data Masker
Use Table-To-Table Synchronization Rules when you have denormalized data in multiple tables and you want to ensure that the data is ...
Read more >QTableWidget Class | Qt Widgets 6.4.1
The QTableWidget class provides an item-based table view with a default model. More. ... This will also remove all selections and headers. If...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Maybe we need a new astropy “project” for “Improve compatibility of Table mixin columns”. Then break it down into manageable bits like addressing specific issues (vstack, outputting to FITS, high-level operations where possible, add QTable to standard set of table_types in testing, etc).
#5841 ensured Table and QTable are now equivalent in support for joining, etc., so closing.