On May 25, 12:51 pm, Vinay Sajip wrote:
> The single codebase port of Django to Python 3 is now available on
> GitHub [1]. Recent core changes have been merged, and the test results
> are available at [2].
>
> Summary:
>
> 2.7.2: Ran 4734 tests in 540.793s - OK (skipped=112, expected
> failures=3)
On Thursday, May 24, 2012 3:57:26 PM UTC+2, Andre Terra wrote:
>
> Hi Ashraful,
>
> First of all, thank you for contributing with your ideas for this project.
> Your mockup is one of the most aesthetically pleasing so far IMHO but there
> are some issues that need addressing before it could be
The single codebase port of Django to Python 3 is now available on
GitHub [1]. Recent core changes have been merged, and the test results
are available at [2].
Summary:
2.7.2: Ran 4734 tests in 540.793s - OK (skipped=112, expected
failures=3)
3.2.2: Ran 4688 tests in 524.807s - OK (skipped=120, e
It's definitely possible for users to support commit=False. If you call
form.save(commit=False), you can then store form.save_m2m in a temporary
variable, define a new save_m2m function, and then call the old function
from the new. Here's sort of an example:
https://github.com/pculture/mirocomm
I already said cbvs are the better option however as you said some solutions
require custom views, it seems to me persistent login and registration widgets
while an anonymous user instance is present are common practice (ie coming from
à context processor) it felt repetitive to keep bending view
