Making sure that TestCase can be hashed#248
Conversation
|
I don't think the hash should default to |
|
I'm facing the exact same issue when running Django 1.11.x tests with Python 3. Is there any chance this gets merged? |
|
Unsubscribe
…On Thu, 15 Nov 2018 at 12:41, Darren Dormer ***@***.***> wrote:
Ping @jml <https://github.com/jml> and @gone <https://github.com/gone> :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#248 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAHq6i_a0Scfzw5q8pPMM_d2NhYLO2j5ks5uvWDfgaJpZM4LqiCw>
.
|
|
This looks useful to me! While waiting for the merge, I guess I can copy and paste the |
|
@ddormer sorry about ghosting - missed the notification for this. I see what you mean about using every test within the same case having the same id, but that's only going to be used if What's a good default to use when |
|
Bumping this up - been more active lately if there's desire to get this merged |
|
Updated - let me know if you'd like me to squash |
a74f0b4 to
313dead
Compare
Defining a custom eq method will prevent a TestCase instance from being hashed, and the django testing library attempts to hash all TestCases.