Hi Colin,
Good suggestion - and kinda obvious now you mention it! I'll make the
change when I get a chance.
Yours,
Russ Magee %-)
On Sunday, August 17, 2014, Collin Anderson wrote:
> Hi Russ,
>
> I like the new wiki home page. Would it make sense to have a link to
> Github? People who click "C
To triple check, I've created empty app and and it still fails. I've opened
trac ticket:
https://code.djangoproject.com/ticket/23305#ticket
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving
Hi Russ,
I like the new wiki home page. Would it make sense to have a link to
Github? People who click "Code" in the top right might be looking for the
source code.
Thanks,
Collin
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsub
It's not intended behaviour, it might be a bug with app loading or
migrations or it might just be a circular import issue.
Could you open a ticket with your test case on the Trac?
Andrew
On 16 Aug 2014 14:15, "Rafał Pitoń" wrote:
> I have noticed something today as I've added AppConfig to my ap
I have noticed something today as I've added AppConfig to my app:
This app at top of its __init__.py imports module "api.py" which in turn
imports models "Notification" from models.py.
When I fire "makemigrations myapp_label", it claims no changes where made,
which obviously is false. I have mo
Hi,
It seems to me that the taxonomy doesn't handle well FileField and ImageField.
It could be bundled in with ForeignKey (as the data it really represents is
only pointed at by the related column data), but not with the current wording.
For ImageField, there is -- in addition to the above -- t
On Saturday, August 16, 2014 4:38:30 AM UTC+3, Russell Keith-Magee wrote:
>
> b) "Relating" data fields - This means ForeignKey. Fields that manifest as
> a single column, but represent a relation to another model.
>
This definition will not work when multicolumn foreign keys are introduced.
Esp
Hello,
I've had another look at this. The novalidate attribute on the form for URL and
email fields indeed disables the validation in both Chrome and Safari. For
number fields, I can reproduce Patrick's test: Safari will still silently drop
the value.
So, for URL and email fields, this issue i
