Is there anyone else out there who doesn't like having to import models from
app X into app Y just so that app Y can connect post save signals to them?
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visi
It's a shame we couldn't skip straight to Python 3.3 and take
advantage of PEP414...
On 22 August 2012 07:32, Adrian Holovaty wrote:
> On Tue, Aug 21, 2012 at 5:46 AM, Aymeric Augustin
> wrote:
>> In my opinion, option (2) is a logical move at this point. However I
>> believe it deserves a publi
On Tue, Aug 21, 2012 at 5:46 AM, Aymeric Augustin
wrote:
> In my opinion, option (2) is a logical move at this point. However I
> believe it deserves a public discussion (or at least an explanation).
> What do you think?
I prefer option 2 as well, because it seems like the Right Thing To
Do. Of c
Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.
Thanks,
Karen
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googl
--This is the Model definition
FEEDBACK_CHOICES = (
(1, 'FOR'),
(-1, 'AGAINST'),
(0, 'NEUTRAL'),
)
class user (models.Model):
user_name = models.CharField(max_length=150)
class comments (models.Model):
comment = models.CharField(max_length=1000)
Hi Aymeric, I prefer the eventual resulting consistency of option 2 and
less gotchas when coding; thanks for asking.
On 21/08/2012 06:46, Aymeric Augustin wrote:
Hello,
The first steps of porting Django to Python 3 was to switch on
unicode_literals, as explained here [1]. This change was discu
On 21 elo, 13:46, Aymeric Augustin
wrote:
> Hello,
>
> The first steps of porting Django to Python 3 was to switch on
> unicode_literals, as explained here [1]. This change was discussed in
> ticket #18269 [2] and committed in changeset 4a103086d5 [3].
>
> This changeset added `from __future__ imp
Hello,
The first steps of porting Django to Python 3 was to switch on
unicode_literals, as explained here [1]. This change was discussed in
ticket #18269 [2] and committed in changeset 4a103086d5 [3].
This changeset added `from __future__ import unicode_literals` only
where necessary, ie. in modu
Thanks for your work during the GSOC, Rohan - don't worry about not
achieving everything, it looks like there's still some useful code there!
Hopefully we can get some of the code merged, especially centralised
tokenisation if it's so near completion, as it looks like a nice bit of
cleanup code!
