-
-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dup-selected] Stack tracing related to sorting/diving #2254
Comments
This was a tricky one. Thanks for filing, @frosencrantz. |
saulpw
added a commit
that referenced
this issue
Jan 15, 2024
Every sheet instance needs its own _ordering list, which orderBy modifies. But _ordering is defined at the class level so it can be easily specified per class. Now we make a copy of the class _ordering when a new sheet is instantiated, so that orderBy doesn't modify the class list.
anjakefala
pushed a commit
that referenced
this issue
Jan 15, 2024
Every sheet instance needs its own _ordering list, which orderBy modifies. But _ordering is defined at the class level so it can be easily specified per class. Now we make a copy of the class _ordering when a new sheet is instantiated, so that orderBy doesn't modify the class list.
anjakefala
pushed a commit
that referenced
this issue
Jan 15, 2024
Every sheet instance needs its own _ordering list, which orderBy modifies. But _ordering is defined at the class level so it can be easily specified per class. Now we make a copy of the class _ordering when a new sheet is instantiated, so that orderBy doesn't modify the class list.
@saulpw Thanks for fixing it! I was trying to make it a simpler case, that seemed to be the smallest case. I understand now why it required a trip through multiple sheets. |
anjakefala
pushed a commit
that referenced
this issue
Jan 16, 2024
Every sheet instance needs its own _ordering list, which orderBy modifies. But _ordering is defined at the class level so it can be easily specified per class. Now we make a copy of the class _ordering when a new sheet is instantiated, so that orderBy doesn't modify the class list.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Small description
dup-selected
stack tracing related to sorting/divingExpected result
No stack, new sheet
Actual result with screenshot
https://asciinema.org/a/8vNNKLZ9KpAV91NDrVQSRTeso
If you get an unexpected error, please include the full stack trace that you get with
Ctrl-E
.Steps to reproduce with sample data and a .vd
echo '{"a":"b","c":["d"]}' | vd -f json
Then sort the sheet, pyobj-cell into the cell in column 'c', select the row, and then dup-select
In the vdj file below I added the dup-selected manually, so it is possible that line is fully correct.
Additional context
Please include the version of VisiData and Python. Latest develop. Python 3.9.2
The text was updated successfully, but these errors were encountered: