An AutoOneToOneField that works with Django 1.8

[skorokithakis]

An AutoOneToOneField that works with Django 1.8

[skorokithakis]

Thanks for this. Can you open a PR? Is it backwards-compatible?

[beaugunderson]

@nutztherookie I don't think my technique is backwards-compatible though is the only issue :)

[skorokithakis]

Thanks for the PR! If I understood correctly, this is to avoid the ValueError, right? In that case, the change is backwards-incompatible indeed, but does it work at all without this?

I haven't used 1.8 yet, and I rarely use this field, but if it breaks completely with 1.8, we should probably do it this way. Maybe adding a check for the Django version would be prudent.

[andreasnuesslein]

It does work partially - I think pulling the object worked, but not auto-creating it. I will try and create a version-agnostic patch asap

[andreasnuesslein]

actually.. I just tested a bit and I'm pretty sure it IS backward-compatible. tried django 1.7 and django 1.6 and both work fine with the new code.

[skorokithakis]

Alright, it looks backwards-compatible to me too, and this is the way Django recommends, so I'll merge it, thank you!

[andreasnuesslein]

@skorokithakis would it be okay for you to release django-annoying with this fixed?
It'd be better here at work to be able to pull from pypi (via pip)

Thanks a lot

[skorokithakis]

Sure, no problem. I will do it shortly, thanks!

[skorokithakis]

The dev->master diff tells me I made too many changes in my botched py3k attempt, so I'll have to fix those before I can release it...

[Kobold]

Thanks for all the work! Just wanted to leave the feedback that AutoOneToOneField is the primary reason I use django-annoying.

[andreasnuesslein]

thanks as well! and: same here ;)

On Tue, May 5, 2015 at 9:00 PM, Andy Kish [email protected] wrote:

Thanks for all the work! Just wanted to leave the feedback that
AutoOneToOneField is the primary reason I use django-annoying.

—
Reply to this email directly or view it on GitHub
#36 (comment)
.