Hi Josh,
In short, no - Twitter isn't a particularly reliable source for updates.
Someone in the core team will usually tweet about the release, but since
it's hard to share logins to a single Twitter account, and the person who
owns Django's twitter account won't always be involved in formally cu
On 25 mars 2013, at 18:02, SteveB wrote:
> I suspect this is a bug. Any thoughts?
Yes, it's annoying, all the more since Django exposes response.content as an
attribute.
> This works, but makes my code dependent on the internals of the HttpResponse
> class, which isn't great. Any better ideas
On Tue, Apr 2, 2013 at 4:49 AM, David Danier wrote:
> This is somethign that does not need to be inside Django core. So why
> not just start an thirt party app implementing the proposal?
I did just that: https://pypi.python.org/pypi/django-multiurl.
Turns out it takes a fair bit of spelunking in
Hi Shai,
The discover runner does discovery based on pattern.
So, if your tests are named, test_*.py, they would by be discovered by
default. Test discovery is recursive, under the root, so it doesn't
matter if you have tests in a tests directory.
The __init__.py imports would be redundant, and
Thanks for the release!
Kind of random question, but this seems like the best place to ask
it. I used to use Twitter mobile notifications to keep up with Django
releases, but I've noticed that the last three releases (since 1.4.4)
have not been announced on Django's Twitter. Is this just an over
> David: The slugs wouldn't be overlapping if they inherited from some
> sort of "Organization" model with unique slug. The user could also add
> validation code to prevent company and schools having same slugs.
If you have a common base model this sounds like some polymorphic model
problem, which
