Still active?

[andybak]

I thought django-wham was a great idea. I am about to integrate with justgiving and I wondered if the project was still active?

[mbylstra]

Hi Andy. This sounds like a great use case! Probably the biggest issue with django-wham at the moment is that it hasn't been updated to Django 1.7+. Unfortunately this might be a difficult upgrade, as the model._meta API was changed in Django 1.7. The good news is that in Django 1.7, model._meta became an official public API, which means it will remain stable as Django goes through major releases. Previously it was an undocumented API, with no guarantees for stability, hence the breaking changes from Django 1.6 to Django 1.7.

I haven't had a chance to do the upgrade, and I'm no longer using django-wham on any projects. I don't think I'll find time to do the upgrade, but if you're interested in giving it a go, I'll be happy to answer any questions you might have. Messing with model._meta to get this to work can be a bit hairy, but it's also kinda fun - you have to get pretty intimate with how the django ORM works, if that interests you! There's much better documentation on model meta these days, which helps: https://docs.djangoproject.com/en/1.10/ref/models/meta/.

[andybak]

Thanks for the reply.

For my immediate need I went with using slumber (a very different tool but it solved the broad issue of giving me a less verbose and more Pythonic way to work with an API).

I also looked at tapioca-wrapper which has some similar benefits.

I might be tempted to look at wham again at some point. Do you know if many projects ended up using wham in production?

[Hann1bal]

Hello i can't find field one to one for primiry key? Can u help me?