Am 17.06.2015 um 16:48 schrieb charettes:
I suggest you use the following pattern which also accounts for py2/3:

...

This is stepping into the django-user@ territory so I suggest we move the
discussion over there if the provided example doesn't match your needs but you
are really just trying to write a portable third-party field.

Thanks for you suggestion.

I "moved" it to django-user list ;)

--


Mfg.

Jens Diemer


----
http://www.jensdiemer.de

--
You received this message because you are subscribed to the Google Groups "Django 
developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/mls207%24lkp%242%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.

Reply via email to