All you need to know about implementing your own policy:
http://xkcd.com/936/
On Sep 14, 1:17 pm, Paul McMillan wrote:
> I'm happy you're concerned about this, but suggest you search the
> archives for similar material so that new threads can contribute new
> content.
>
> This search is probably
Hello;
I second all of what Carl said and would like to point out the app-refactor.
I believe the most current code still lives in the app-loading branch on
jezdez's repository on GitHub[1]. The reason I point this out is because
the current testing structure is a legacy of the way Django intern
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/13/2011 08:46 AM, mvr wrote:
> Why doesn't the django test management command / test builder allow
> fully-qualified package names instead of just app-relative ones?
>
> At work we've been using the method below to monkey-patch the test
> builde
> Would it not be possible to move the second instance of the nonce (that
> will be compared to the form field) from a cookie to a session variable
> (at least when a session is available)? Would that result in other
> problems instead?
Yes it's possible, and that's how our CSRF protection worked
On Wed, Sep 14, 2011 at 8:42 PM, Jannis Leidel wrote:
>
> > Anybody knows somebody who started a django/py3 port already? We should
> unify our efforts.
>
> As I said earlier in this thread, there is now a Python 3 branch in the
> Django SVN.
>
Thank you! Really good to see that.
>
> > If core
On 14.09.2011, at 19:19, Cal Leeming [Simplicity Media Ltd] wrote:
> Can I ask, have the django core team already accepted that Django will
> eventually be a 3.x framework, or will it be un-officially forked?
Yes, the core team has identified the port to Python 3 as a needed step which
is why
On 14.09.2011, at 18:57, Ákos Péter Horváth wrote:
> Really, I started to port that with a recursive 2to3. It is not too far from
> good working. There are no big magic things, altough I think a py2 and py3
> support isn't possible from a common source tree. Some deep core improvement
> is nee
Can I ask, have the django core team already accepted that Django will
eventually be a 3.x framework, or will it be un-officially forked?
Personally - I'd love to see people ride the 2.x train until its last dying
breath, but that's just me ;)
Cal
2011/9/14 Ákos Péter Horváth
> Another vote to
Another vote to python3 :-)
Really, I started to port that with a recursive 2to3. It is not too far from
good working. There are no big magic things, altough I think a py2 and py3
support isn't possible from a common source tree. Some deep core improvement
is needed too, mostly on the unicode line
Hi,
On Wed, Sep 14, 2011 at 10:03 AM, Jannis Leidel wrote:
> Hi all,
>
> After last week's sprint I wanted to get you up-to-speed about the
> current state of porting Django to Python 3.
>
I'm very happy with this news.
> As some may be aware Martin von Löwis has been working on a port for
> a
Daniel,
> I wasn't trying to suggest we leave anyone behind, far from it. I
> was suggesting move the code to Python 3 now, while there's less code
> there (than some future date) but using 3to2[1] to help others on
> Python 2.X. Since Django still supports 2.5, it's possible that this
> isn't e
Help to cite appropriately. [1] was http://pypi.python.org/pypi/3to2.
On Sep 14, 10:55 am, Daniel Lindsley wrote:
> Jannis,
>
> I wasn't trying to suggest we leave anyone behind, far from it. I
> was suggesting move the code to Python 3 now, while there's less code
> there (than some future d
Jannis,
I wasn't trying to suggest we leave anyone behind, far from it. I
was suggesting move the code to Python 3 now, while there's less code
there (than some future date) but using 3to2[1] to help others on
Python 2.X. Since Django still supports 2.5, it's possible that this
isn't even an o
Daniel,
> "You have my sword." I want to see this happen & would love to be a
> part of it.
Huzzah!
> A couple questions:
>
> * How should patches be provided? Trac? BitBucket?
For now via Trac, that's why we've moved the changes into a SVN branch.
Unless anyone has a better idea I could cre
Jannis,
"You have my sword." I want to see this happen & would love to be a
part of it. A couple questions:
* How should patches be provided? Trac? BitBucket?
* Where should feedback go? This mailing list? Somewhere else?
* This is further off, but once we have a ported Django, how do get
the
Hi all,
After last week's sprint I wanted to get you up-to-speed about the
current state of porting Django to Python 3.
As some may be aware Martin von Löwis has been working on a port for
a while [1] but only recently I've had the chance to meet with him and
talk through the porting process.
I'
Hi,
> Today we've released Django 1.3.1 and Django 1.2.6 to deal with
> several security issues reported to us. Details of these issues and
> the releases, along with several important advisory notes, are
> available in the blog post on djangoproject.com:
>
> https://www.djangoproject.com/weblog/
17 matches
Mail list logo
