Спасибо!

I completely forgot about this, sorry (I didn't get notifications for the answers...)

I suppressed the remaining tests about that, I think. Should be compliant with the description, now.

The Kata is a good opportunity to learn/reinforce knowledge of the class creation process and descriptors. However, the instructions are not very explicit, and I wasted a lot of hours because of that. To anyone else, I suggest:

1. Check out the code of the Test Cases to see what is going on with the tests
2. The tests will change attributes of the object after it is instantiated
3. Defaults are only relevant at User class instantiation, not if an attribute is changed after the instance is created
4. The DateTimeField (if auto_now is set) should return the current time if the default attribute is accessed (mentioned in other discussions, but not in the Kata description)
5. The EmailField length restrictions apply to the whole field, not each of the 3 parts (it could be taken either way in the description)

Hope this helps someone :-)

Gj

I still encounter this problem.

You commented out the first occurrence but not the second occurrence.

test.expect(default2 > now2 > default > now, msg)
TypeError: '>' not supported between instances of 'NoneType' and 'datetime.datetime'

Where so? in the samplet tests, I guess? Then you're(were) using an outdated version of the sample tests: I commented out that test in both the sample tests and the full test suite ages ago.

I want to continue this discussion.

I also kept getting the same error:

    test.expect(default2 > now2 > default > now, msg)
TypeError: '>' not supported between instances of 'NoneType' and 'datetime.datetime'

And after expanding the further comments, it is revealed that the test contains:

field2 = DateTimeField(auto_now=True, blank=True)
default = field2.default

This feels out of scope, since DateTimeField shouldn't be accessed outside a class. I had to put in extra hacks in my solution to get this to work.

Informational question only: Will descriptors work in place of metaclasses here? I understand the purpose of the kata is to learn metaclasses.

removed => isinstance is now allowed

.

handled, testing only at Model instantiation time. Oh, I forgot to talk about default taking precedence over auto_now. I'll add that in the next fork.

suppressed the meaningless requirement (and updated the description)

Thanks again for the feedback and the time you spent on this! I did have to check my validation, probably have to refactor it later.

Tests passed! Thanks for modifying the tests! Really helped a lot!