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
add guidelines for testing dicts to devel guide #17362
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
E.g. something along the lines of
but perhaps someone might have an actual example that had to be fixed for the Sage doc to test right, I am pretty sure Trac is full of these. |
comment:4
I didn't know about that aspect of it, only the graphics part. So will doctests automatically fail if people put them in the order that their computer gives and it's not sorted? That could be confusing! So maybe it should still be mentioned in the guide, along with the graphics piece - which is not what the command line gives. And, more relevant to my immediate concern, what if the keys themselves are dictionary-enough that they are platform-dependent? See #16331 for an explicit example of this. It would be great if you could give some advice for that, because we haven't come to any useful consensus yet. |
comment:5
Replying to @kcrisman:
There are 2 dict orders: the Python order and the IPython order. The Python order is what you get with |
comment:6
Replying to @kcrisman:
Well, #16331 is special because you're sorting a list containing integers and strings. The problem is that the output of |
comment:7
Yikes, and apparently isn't even allowed in Python 3.
Hmm, although I still think some updating could be done, I guess a ticket just for that or the graphics thing, which is now everywhere, probably isn't that worthwhile. |
comment:8
Close as "wontfix"? |
comment:9
ok |
Reviewer: Karl-Dieter Crisman |
Changed reviewer from Karl-Dieter Crisman to Jeroen Demeyer, Karl-Dieter Crisman |
The developer guide doesn't mention that dictionaries can come out platform-dependent or worse in Python. New developers should have a good place to find a good example or two of how to deal with this.
Component: documentation
Reviewer: Jeroen Demeyer, Karl-Dieter Crisman
Issue created by migration from https://trac.sagemath.org/ticket/17362
The text was updated successfully, but these errors were encountered: