Gregory,
Not only is it not practical in Django, it's not a realistic solution using any framework.
There is no "machine ID" that is exposed to a web site, and originating IP addresses completely fails for all people accessing your site from behind a NAT box or other similar functional device. (I work in an office using a private ip address range - 10.1.xxx.xxx. All websites that any of us access all see the same originating IP address. So if I were to acknowledge that disclaimer, your software would assume that everyone in my office has done that - which I don't think you want.)
Yes, there are some options that would cover most of the common cases - you could use a cookie for example, to track on the user's side whether or not they've agreed to that disclaimer. That'll work for as long as they keep the cookies and don't change browsers - or run in incognito mode.
(And all of this is discounting any intentional actions to spoof / avoid that disclaimer.)
If you have any _real_ requirement for that disclaimer to be acknowledged, then an actual per-user account is the only way to do it.
Ken