18.9.2012 1:59, Andrew Godwin kirjoitti:
Hi all,
There's doubtless some polishing and bugfixing that will be needed
before final release, but I'll be keeping on top of that (by developing
an app that uses it, partially) and making sure that 1.5 ships with
something that's decently solid, and wi
The ticket page is here: https://code.djangoproject.com/ticket/16774
I previously said people trying to resolve URLs in their code may have
difficulty because the DoesNotResolve exception is not raised until the
view is run. Just now I thought how it would be done. I think changing
resolver.url
>
>
> Can you put this in a pull-request so I can comment inline?
>
>
I can indeed: https://github.com/django/django/pull/376
Andrew
--
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@goo
On Mon, Sep 17, 2012 at 3:59 PM, Andrew Godwin wrote:
> Hi all,
>
> I have now, I believe, got a working, feature-complete schema alteration
> branch ready to go. It has full support for PostgreSQL, MySQL, and SQLite,
> and follows the rough design principles I emailed the list about a while
> ba
Hi all,
I have now, I believe, got a working, feature-complete schema alteration
branch ready to go. It has full support for PostgreSQL, MySQL, and SQLite,
and follows the rough design principles I emailed the list about a while
back.
It's fully tested, but no documentation yet - I'm not sure wha
I'm not an expert in packaging, I've released a few apps, but my novice
eyes caught some things:
* Bullet 6 under "Packaging your app" mentions the manifest file, without
specifying anything useful about it to someone (eg: me) who doesn't know
what it's for. Maybe add a descriptional oneliner, or a
