I've decided to start issue tracker on github to list all gotchas and
differences between Ember.js defaults and conventions vs. Django ones I
have encountered so far as well as solutions and fixes for those:
https://github.com/rafalp/django-ember-issues
I currently have file on two things her
This happens because "result" is class level attribute, not instance one,
and its expected behaviour in Python.
To made result instance attribute, define it in your __init__:
class Demo():
def __init__(self):
self.result = []
def do_something(self):
self.result.append(1
Really? You bring up three years old toy project that didn't went anywhere
and mock somebody's work because PHP's involved? Thats bad form OP.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving ema
On Friday, February 28, 2014 4:16:58 PM UTC+1, Scott Anderson wrote:
>
> Well, things like Twig are based on Django templates. We're currently
> migrating from PHP to Django, and if something like Django-PHP made that
> easier I would most definitely use it.
>
> To be honest I wish there were a T
Hello,
In my app I am using custom user model with my own createsuperuser command.
However after updating my dev to Django 1.7 I've realized that behaviour of
commands discoverer was changed from "last one wins", to "first_one_wins"
so first command discovered is preffered instead.
I've fixed
Allright, thanks for answer.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to djan
6 matches
Mail list logo
