On Wednesday, August 7, 2013 11:51:58 PM UTC+2, DrMeers wrote:
>
> On 13 June 2013 07:41, Simon Meers > wrote:
>
>> On 13 June 2013 03:33, > wrote:
>>
>>> I think that the usability of ForeignKeyRawIdWidget could be vastly
>>> improved if the representation part of the widget (the object name, i
On Thursday, October 24, 2013 7:42:50 AM UTC+3, Russell Keith-Magee wrote:
>
>
> On Thu, Oct 24, 2013 at 12:08 PM, schinckel
> > wrote:
>
>> Hi,
>>
>> I was wondering if there was any reason why fields such as
>> models.DateField() do not use the SubFieldBase metaclass
>> trick to ensure they al
Hi,
Good morning.
Your help is needed:
I am relatively new to Django. After developing a Django app, I am trying
to write my first patch for Django.
I checked out Django from github: VERSION = (1, 7, 0, 'alpha', 0).
When I run the unit tests with the command "python runtests.py", I get 6
err
How do you decide which version to put a feature in?
Why wasn't migrations in 1.6?
On Thu, Oct 24, 2013 at 12:01 AM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:
>
> On Thu, Oct 24, 2013 at 10:45 AM, Cody Scott wrote:
>
>> I know that I can look at the 1.7 release notes to see what is
I really like the idea of implementing this as a url pattern decorator.
This seems similar to Alex Gaynor's talk about everything being a view.
It's more flexible than a middleware because you can decorate any part of
the urls tree, such as the patterns for a single reusable app.
urls = decora
That's to do with the date a feature lands. Migrations isn't completely
feature complete or totally stable yet - squashing migrations actually
landed in the master branch this week.
When we release the beta, the version goes into feature freeze so only
minor bug fixes and any critical issues get m
Somewhat long post ahead - jump to the list in the end of post to see the
backwards incompatible changes.
Ticket #21169 deals with a bunch of different related manager improvements.
Some are bug fixes, some are there to make related manager methods work
consistently and finally the ticket's ori
Do you have anything running on port 8081 (running netstat will tell you)?
I just ran Django's test suite on my machine (Windows 7, Python
3.3.2), from the trunk cloned an hour ago, and it completed mostly
without an issue (there's a UnicodeDecodeError but that's likely
because it's printing a cha
As this is about running the Django teat suite in order to try to write a
patch it does belong on this mailing list.
I don't have any concrete ideas what's wrong - but it does look like all
your issues are related to running the LiveServer (selenium) tests.
Something bound to a certain port alread
These are minor bugfix releases, so not particularly urgent to upgrade.
Details and release notes are available from the blog post:
https://www.djangoproject.com/weblog/2013/oct/24/bugfix-releases/
--
You received this message because you are subscribed to the Google Groups
"Django developers"
10 matches
Mail list logo