If anyone feels competent to review, there's a PR open now for the first
part of this, adding Referrer-Policy support:
https://github.com/django/django/pull/9953
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" gr
I've written this up in pseudo-DEP format partly for ease of
organization, and partly because I'm unsure whether it would require a
DEP. Right now I'm just throwing it out here as a proposal, and
offering to work on implementing it; if you have questions, concerns,
or suggestions for things to add
One approach you might try is on every test run, randomly select some lines
from the list of common passwords and verify they fail the validator. That
way we know it's not just testing a single, fixed, contrived case.
--
You received this message because you are subscribed to the Google Groups
"
I can think of several cases where I'd want a custom field to be able to
add an index, and contribute_to_class() is, as you say, the natural place
to do it -- it's the hook for everything else fields want to add as part of
their setup.
So I'd be +1 on making sure it's possible to add indexes throu
To be honest, I'm curious why the SQLAlchemy approach isn't being discussed
more here. Implementing a calculated-field property decorator, and
supplying both the SQL side (via a method which returns a Q object, most
likely) and the Python side wouldn't be too difficult to implement, and
avoids the
80% covered by two approaches that aren't really compatible with each other
doesn't get there :)
Again: to get into Django, something really needs to be as close as
possible to "one size fits all", not "one size fits some, another size fits
some more".
--
You received this message because you ar
Generally, I'd like to see something satisfying the needs of around 80% of
use cases out of the box before including it directly in Django. No
database-translation tool I'm aware of is even close to that level.
--
You received this message because you are subscribed to the Google Groups
"Django
Because even if you collapse the number of approaches to just two general
options, there's still enough variability in the specifics of how to
implement those options that there's no clear "one size fits all" solution
at the moment. If there ever is one, it can be considered for inclusion in
Django
For questions about using Django, please use the django-users mailing list.
This list is for the development of Django itself.
On Thu, Jun 8, 2017 at 12:21 PM, Matheus Fernandes <
matheus.souza.fernan...@gmail.com> wrote:
> Hi!
>
> It's the first time that I'm developing a real-time application.
On Thu, Apr 6, 2017 at 5:22 PM, James Pic wrote:
> Do I need this to deploy my projects ? No of course, because I use the
> prettiest way hhihihi ;) I'm more than happy to win a debate
>
Please don't do this. This does not make you look like someone who I could
constructively engage with to try
WSGI is a framework-independent protocol to allow HTTP servers to
communicate with Python applications. It defines a standard API and
serialization mechanism to be used by the HTTP server and the Python
application in order to allow them to work together.
WSGI *only* does plain HTTP. And in fact i
On Mon, Jan 16, 2017 at 4:47 AM, Adam Johnson wrote:
> We implemented something similar at YPlan but discovered that it wasn't a
> good idea as a system check, because if a dependency changes from another
> devs work then often Django can't even start and run the system check.
> Especially a prob
On Sun, Jan 15, 2017 at 1:09 PM, Pkl wrote:
> My bad, if people are guaranteed 2 x 24-month cycles before a feature gets
> removed, it's already much better. However, the same pattern as previously
> appears in docs : "each feature release will continue to have a few
> documented backwards incomp
Please read Florian's message. 2.0 is not going to be "we bumped the major
version, now we can pile in lots of breaking changes".
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this gro
On Fri, Jan 6, 2017 at 7:03 PM Tim Graham wrote:
> I don't know if matters to anyone, but I guess as long as we support
> Python 3.4 we can't do the type hinting project (PEP 484) since that's new
>
> The typing module also exists standalone on PyPI and thus is pip
> installable for Python 3 < 3.
On Tue, Jan 3, 2017 at 1:14 AM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> Regarding arguments, since signal receivers must accept **kwargs (that’s a
> document requirement), I think it’s acceptable for assertSignalSent to
> ignore unexpected arguments.
>
It's often the case
At DUTH this year I opened a ticket to add test-case assertions checking
whether (or not) a signal was sent:
https://code.djangoproject.com/ticket/27447
And corresponding PR:
https://github.com/django/django/pull/7508
The PR has gotten bogged down in API design discussion, so I'd like to hash
t
I think I once implemented something that dynamically generated model
classes at runtime and prefixed the class names with an underscore.
But I also didn't do much with those models other than set up tables for
them and store/retrieve instances with very simple queries. Also, what I
was doing was
For what it's worth, I'm suspicious of threat models which begin with
"assume the DB has already been significantly compromised..." simply
because there's so much someone can do if they gain even read access that
it's not worth expending a ton of effort hardening Django against those
cases.
Simila
On Wed, Aug 31, 2016 at 10:55 AM, Alex Gaynor wrote:
> If these are what qualifies as critical, I don't think this is a good use
> of our time.
>
>
>
Agreed. If those are the critical things, then either Django is really
really good, or there are things it's missing. I suspect there are things
it
Whee, this thread got big!
The takeaway I'm getting here is that we should be careful about what we
adopt into core and when; I'm going to take a couple days and write up some
notes on what I think a good conservative approach would look like, and ask
for feedback on that.
(spoiler: probably the
Apologies for how late in the process this is; job hunt + moving
cross-country ate a lot of my time.
At Django Under the Hood I proposed that for Django 1.10 we try to find
some common best practices for deploying Django on popular
platform-as-a-service (PaaS) solutions, and building support for t
Personally I've long been in favor of drastically simplifying the email
regex and essentially telling people that if they want to support
triply-nested comments in a bang-path address they can write their own :)
Is there an actual compelling reason to not just pare it down to "word
characters and/
The only argument I see for format() over the % operator is that bytes
objects explicitly do not have the format() method and so it'll catch
errors where a bytes object is passed to something expecting a string.
But since we're already Unicode-ifying everything at the boundaries and
have been sinc
I'd be against such a change. I've used a lot of bug trackers, and the only
thing I've learned is there is no good one; replacing one with another just
swaps one set of annoying limitations/frustrations for another. And since
there's a lot of inertia in whatever's currently being used, and it would
Thanks to everyone for the quick consensus, and to Tim for backporting it
and fixing the docs before I could get around to it :)
On Mon, Dec 7, 2015 at 9:23 AM, Tim Graham wrote:
> Done in
> https://github.com/django/django/commit/9c835990ea2911c06a877296fbc25157c1302e1d
> -- thanks for pointing
About two months ago, ticket #25548[1] was opened, pointing out that
on an invalid form submission, FormView was calling form validation
methods twice (what was actually happening was that the original form
instance was discarded, a new one constructed with the same data, and
the first access to it
Never mind, just saw that 3.5 is listed in the 1.8 release notes and
answered my own question.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from i
Bumping this thread a bit because I subscribe to Debian's tracker for their
Django package, and there's some question of whether we do or do not
officially support Python 3.5 on Django 1.8. Was there ever a final
decision?
On Tue, Oct 27, 2015 at 5:19 PM, Ned Batchelder
wrote:
> BTW, there's a m
8 years later, I still think we should figure out how to make exclude() do
what people expect it to do, rather than implement another lookup type that
overlaps with it.
On Fri, Nov 20, 2015 at 7:27 PM, Aaron C. de Bruyn
wrote:
> With all due respect, looking through the ticket and reading respon
ms
of potential impersonation.
On Sat, Aug 29, 2015 at 2:59 PM, Tim Graham wrote:
> The suggested change is to not allow a new user if there's a
> username__iexact match.
>
> On Saturday, August 29, 2015 at 2:56:14 PM UTC-4, James Bennett wrote:
>>
>> On Sat, Aug 29,
On Sat, Aug 29, 2015 at 1:54 PM, Florian Apolloner
wrote:
> Which is? Following the ticket I do not see any clear consenus at all. Imo
> Registration apps should handle that, which is not something Django ships
> with. I am -0 on changing the admin to disallow such users.
>
For what it's worth,
On Tue, Aug 11, 2015 at 5:43 PM, Tim Graham wrote:
> It seems that django-contrib-comments has a moderation feature where you
> can specify a field on your model to control how comments are handled [2],
> so this was presumably used for that.
>
>
The field on FlatPage has been there since the beg
One option for declaring an app "unmanaged" could be via AppConfig. That's
fairly clean, mirrors the way you can already set a model as unmanaged in
its Meta declaration, and allows for the end user of the app to override by
supplying an AppConfig which will generate migrations (should they, for
so
There's not much to this, really, except what's in the subject line of this
message.
The problem of providing a single-file, no-build-step format for
distributing and installing Python packages has been solved by wheels, and
wheels also don't cause the pile of weirdness that comes with using eggs.
On Wed, Apr 1, 2015 at 10:28 AM, Stan wrote:
> A classical pip install Django command without --mirrors or --use-mirrors
> modifier.
>
> I did some --upgrade, but the first installation is not 10 years old (2
> maybe).
>
>
> Pip is a Debian package (1.1.3)
>
> [$ whereis django-admin
> django-adm
There's been some recent discussion in a django-users thread[1] about
the impending end-of-life of Django 1.6, which in turn will mean
end-of-life for Django supported on Python 2.6. In addition, the
end-of-life of the current LTS release, Django 1.4, will mean
end-of-life for Django supported on P
Please keep discussion going in this mailing-list thread, and keep in mind
Django's policies regarding re-opening a "wontfix" ticket (which are
essentially: don't do it).
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django its
On Thu, Jan 15, 2015 at 12:05 AM, Horacio G. de Oro
wrote:
> If you see the new hash in the database, I think that, maybe the admin, is
> saving the user instance with the new hash. And doing that, ie: save()'ing
> the user returned by authenticate() solved the issue for me too (but I
> don't wan
-1.
The conflict between niche "technically correct terminology even if no-one
actually uses these words" terms and "technically incorrect terminology but
everybody uses it anyway" should, in most cases, be won by the
technically-incorrect terminology. My favorite relevant examples of this
are the
The first bugfix release in the 1.7 series is out, along with bugfix
releases for the supported 1.4 and 1.6 release series, and what will
hopefully be the final release of the 1.5 series, which is now past
end-of-life.
Full details are available on the Django project weblog:
https://www.djangopro
On Tue, Sep 9, 2014 at 6:25 PM, Benjamin Scherrey
wrote:
> I really appreciate you for being the first person to directly respond
> to this most critical issue in this debate. You are correct, this incident
> is quite central to my point and concern. However, I have again reviewed
> the group
I have been involved in building and participating in and running
technically-oriented groups for fifteen years. I've seen a lot of stuff.
The most common problem pattern I have seen is the "I'm not touching you"
game. To understand what this means, imagine parents driving a car, with
two children
Django 1.7 is now available:
https://www.djangoproject.com/weblog/2014/sep/02/release-17-final/
Alongside this are bugfix releases for 1.4, 1.5 and 1.6. The bugfix 1.5
release is the final releae in the 1.5 series, as Django 1.5 has now
reached end-of-life.
--
You received this message because
Today we've issued releases to address four security issues reported to us.
Full disclosure is on the djangoproject.com weblog:
https://www.djangoproject.com/weblog/2014/aug/20/security/
All users are encouraged to upgrade.
Additionally, for anyone who missed it, last week we published an adviso
Two things:
1. This is django-developers, the list for discussing the development of
Django itself. For questions about using Django or Django-based
applications, please use the django-users mailing list.
2. You've just shared your SECRET_KEY setting publicly with thousands of
people who received
I like the idea -- if nothing else, it would provide an easy way to have a
test suite discover N+1 problems, especially in templates.
Not sure about the feasibility, though; would you be willing to work up a
rough implementation of it?
--
You received this message because you are subscribed to t
Speaking for myself, I am still willing to hand over the reins of
django-registration to someone who's genuinely motivated to try to solve
the issues surrounding things like custom User support, etc., though I
still do believe that's just a bridge too far for what was meant to be a
simple app.
I'v
Check out the weblog for details (including information on a change to the
keys used to sign Django releases):
https://www.djangoproject.com/weblog/2014/jul/27/17rc2/
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this
We're closing in on the final Django 1.7 release, so it's release-candidate
time!
Details are up on the Django project blog:
https://www.djangoproject.com/weblog/2014/jun/26/17rc1/
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubs
On Tue, May 27, 2014 at 12:07 PM, Meira wrote:
> It seems to be, there are enough reasonable people leaving comments like
> this one: https://github.com/django/django/pull/2720#issuecomment-44296843
>
We'll just get the databases to change their terminology before we change
ours!
Of course, the
It's worth noting that during that two-week time period the core team has
been a bit preoccupied with doing a security release and followup bugfix
release :)
If no-one else has looked at and commented on those two DEPs within the
next day or two, I will have time to do so, and will do so (and feel
Today we've issued releases which remedy a regression reported with last
week's security release.
Details and updated packages are available from the Django project blog:
https://www.djangoproject.com/weblog/2014/apr/28/bugfix-releases-issued/
--
You received this message because you are subscr
Today we've issued releases to remedy three security issues reported to us.
Affected versions are Django 1.4, Django 1.5, Django 1.6 and the Django 1.7
beta.
Full details and download information are on the Django project weblog:
https://www.djangoproject.com/weblog/2014/apr/21/security/
--
Yo
We're getting closer to 1.7!
Details in the blog post here:
https://www.djangoproject.com/weblog/2014/mar/20/django-17b1/
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, se
Yup, we're on the way to 1.7!
Check out the blog post (which mentions a couple of important issues to be
aware of *before* trying out the alpha):
https://www.djangoproject.com/weblog/2014/jan/22/django-17-alpha-1-released/
And the in-progress 1.7 release notes for a full rundown of what's going
Django 1.6 and Django 1.4.10 are out today; the latter is a bugfix release
to restore Python 2.5 compatibility in the 1.4 series.
Full details are in the blog post:
https://www.djangoproject.com/weblog/2013/nov/06/django-16-released/
--
You received this message because you are subscribed to th
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"
It's almost here!
Tonight we've issued a release candidate for Django 1.6. Information,
including links to downloads and release notes, is available on the Django
project blog:
https://www.djangoproject.com/weblog/2013/oct/22/16c1/
--
You received this message because you are subscribed to the
Earlier today a message posted to the django-developers mailing list
publicly disclosed what was later determined to be an exploitable security
issue in Django.
As such, we have short-circuited our normal one-week process and moved to
immediately issuing new releases to remedy the problem.
Full d
Today the Django team is issuing multiple releases -- Django 1.4.7, Django
1.5.3, and Django 1.6 beta 3 -- as part of our security process. These
releases address a directory-traversal vulnerability in one of Django's
built-in template tags.
More details can be found on our blog:
https://www.djan
This list is for discussion of the development of Django itself. For
discussion of how to use Django, please see the django-users mailing list.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receivin
I also think the overlap between
1) People who want to always be running the absolute latest-released
cutting-edge versions of software, and
2) People who are running older editions of RHEL
...is likely to be rather small.
--
You received this message because you are subscribed to the Google Gr
Yup, it's finally here!
* Announcement blog post here:
https://www.djangoproject.com/weblog/2013/feb/26/15/
* Release notes here: https://docs.djangoproject.com/en/1.5/releases/1.5/
* Download it here: https://www.djangoproject.com/download/
--
You received this message because you are subscribe
We've issued several security releases today. Details are in the blog post:
https://www.djangoproject.com/weblog/2013/feb/19/security/
We recommend everyone carefully read this one, as it has an
end-user-visible change requiring action beyond simply upgrading your
Django package.
--
You receive
On Sun, Feb 17, 2013 at 1:17 AM, Skylar Saveland
wrote:
> I would be interested in getting this (or something like it) into 1.4.X and
> 1.5.X. Might this be possible?
Unless it fixes a release-blocking regression, it's not possible for
this to get into either of those release branches. Also, gene
1.5 is almost here!
Today marks the release candidate, which you can read about on the weblog:
https://www.djangoproject.com/weblog/2013/jan/04/15-rc-1/
Assuming no release-blocking bugs, Django 1.5 will be released next week.
--
You received this message because you are subscribed to the Goog
On Sat, Dec 22, 2012 at 6:28 PM, Kevin Veroneau wrote:
> I believe, it would be most beneficial for the Django website to provide
> such an option. I bet most Windows users who hear about Django visit the
> website, but don't see a download link for their system. These users will
> either seek h
Django 1.3.5, Django 1.4.3 and Django 1.5 beta 2 have just been issued
in response to security issues.
Details are available here:
https://www.djangoproject.com/weblog/2012/dec/10/security/
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
Our second milestone on the road to Django 1.5 came today, with the
release of the first beta package.
Blog post about it is here:
https://www.djangoproject.com/weblog/2012/nov/27/15-beta-1/
Release notes are here:
https://docs.djangoproject.com/en/dev/releases/1.5-beta-1/
And you can get the
Our first milestone on the road to Django 1.5 came today, with the
release of the first alpha package.
Blog post about it is here:
https://www.djangoproject.com/weblog/2012/oct/25/15-alpha-1/
Release notes are here:
https://docs.djangoproject.com/en/dev/releases/1.5-alpha-1/
And you can get th
Django 1.4.2 and 1.3.4 have just been released in response to a
security issue reported to us.
Details are here:
https://www.djangoproject.com/weblog/2012/oct/17/security/
Everyone is encouraged to upgrade.
--
You received this message because you are subscribed to the Google Groups
"Django d
Today we've issued Django 1.3.3, a quick bugfix release which restores
Python 2.4 compatibility in the Django 1.3 release series:
https://www.djangoproject.com/weblog/2012/aug/01/django-13-bugfix-release/
Affected users are encouraged to upgrade.
--
You received this message because you are sub
Today we've issued several releases to remedy security problems
reported to the Django team.
Details are here:
https://www.djangoproject.com/weblog/2012/jul/30/security-releases-issued/
All users are encouraged to upgrade immediately.
--
You received this message because you are subscribed to
Questions about how to use Django should be directed to the
django-users mailing list. This list is for discussion of development
of Django itself.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-
On Mon, Mar 26, 2012 at 7:44 PM, Reinout van Rees wrote:
> Having a release before the tag? Sounds weird to me. Making a tag is
> integral to the actual release, right? Curious :-)
The tag and the release package are both just the same revision from
trunk, so there is no requirement for the tag t
Django 1.4 is finally here!
For details, checkout the weblog:
https://www.djangoproject.com/weblog/2012/mar/23/14/
And the release notes:
https://docs.djangoproject.com/en/dev/releases/1.4/
--
You received this message because you are subscribed to the Google Groups
"Django developers" group
Subject line says it all, and details, as always, are on the weblog:
https://www.djangoproject.com/weblog/2012/mar/14/14rc2/
--
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@googlegroup
We're nearly there!
The Django 1.4 release candidate package is now available, and you can
read all about it on the blog:
https://www.djangoproject.com/weblog/2012/mar/05/14-rc-1/
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You received this message be
Hot off the presses, it's the first Django 1.4 beta! Blog post with
more information is here:
https://www.djangoproject.com/weblog/2012/feb/15/14-beta-1/
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You received this message because you are subscribed to
On Wed, Feb 15, 2012 at 4:37 PM, Donald Stufft wrote:
> I know this has been discussed before, but I wanted to bring it up again in
> light of the oncoming Djnago 1.4 beta.
So, here's the thing: you're asking for a fairly significant,
massively backwards-incompatible change which requires every D
Folks, we've had three different members of core point out that,
important as it is, this is a topic for another list/forum. Please
take the discussion there, now.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You received this message because you are sub
On Tue, Dec 27, 2011 at 8:30 AM, Ryan McIntosh wrote:
> With the utmost respect, I must rebuke Paul's claim that this discussion is
> misplaced on the dev list. We all have a stake in this legislation. All
> free software projects have a stake in this legislation. I urge those
> unfamiliar w
Tonight as part of the 1.4 development process, we've released the
first alpha for Django 1.4. You can read all about it on the blog:
https://www.djangoproject.com/weblog/2011/dec/22/14-alpha-1/
And in the release notes:
https://docs.djangoproject.com/en/dev/releases/1.4-alpha-1/
--
"Bureaucr
We have the following constraints:
1. Django supports class-based views.
2. Django supports function-based views (ultimately these are the same
thing, which is that Django supports anything as a 'view' so long as
it's callable, accepts an HttpRequest as its first positional argument
when being ca
Due to an issue with yesterday's 1.2.6 release package, today we are
issuing Django 1.2.7. All users of 1.2.X Django should upgrade to
1.2.7, rather than to 1.2.6.
Details here:
https://www.djangoproject.com/weblog/2011/sep/10/127/
--
"Bureaucrat Conrad, you are technically correct -- the best
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/2011/sep/09/secur
It's here!
Django 1.3 has been officially released.
Blog post here: http://www.djangoproject.com/weblog/2011/mar/23/13/
Release notes here: http://docs.djangoproject.com/en/dev/releases/1.3/
Download here: http://www.djangoproject.com/download/
--
"Bureaucrat Conrad, you are technically correc
Tonight we're proud to announce the first release candidate for Django
1.3; if all goes well, the final release will happen in about a week.
Details for the release candidate are available on the official Django weblog:
http://www.djangoproject.com/weblog/2011/mar/03/13-rc/
--
"Bureaucrat Conr
Tonight the Django team has released updated versions of Django 1.2
and Django 1.1 to correct multiple security issues reported to us.
* Details in the blog post here:
http://www.djangoproject.com/weblog/2011/feb/08/security/
* Download updated versions of Django here:
http://www.djangoproject.co
On Tue, Jan 25, 2011 at 3:45 PM, Graham Dumpleton
wrote:
> Since the 'futures' module is only a part of Python 3.2, that must mean you
> are using that and thus have ported Django to Python 3 already. When can we
> expect that then. ;-)
So, here's what happened.
You all may remember that some ti
On Wed, Jan 5, 2011 at 10:05 AM, Russell Keith-Magee
wrote:
> We will obviously to do a 1.2.5 release when we hit 1.3 final; but I'm
> not sure if we should push an 1.2.5 (and 1.1.4) ASAP addressing these
> regressions, and then do 1.2.6 when we cut 1.3 final.
I'm in favor of doing 1.2.5 as soon
On Tue, Jan 4, 2011 at 8:52 AM, Alexander Pugachev
wrote:
> Why http://code.djangoproject.com/ticket/14202 is not in trunk being accepted?
Short answer: because "accepted" doesn't mean "closed, fixed".
Longer answer: up until the beta release, just before Christmas, quite
a bit of development ti
Tonight we've released Django 1.3 beta 1, as well as Django 1.2.4 and
Django 1.1.3 to correct a pair of security issues.
* Beta announcement: http://www.djangoproject.com/weblog/2010/dec/22/13-beta-1/
* Security announcement:
http://www.djangoproject.com/weblog/2010/dec/22/security/
All affected
I've just opened ticket #14937[1] with a patch implementing what
seemed -- last time around -- to be the consensus fix for the ongoing
fracas that is the list of "state" choices in contrib.localflavor.us.
The patch attempts to avoid international incidents by use of
relatively fine-grained sets of
On Thu, Nov 18, 2010 at 4:38 AM, Valery wrote:
> guys, now also all the MongoDB Python developers are waiting for your
> signals about Python 3.
That's... a really bad idea.
Our Python 3 migration process, at this point, is more or less
dictated by two things:
1. WSGI on Python 3
2. Distributio
The first alpha preview package for Django 1.3 is now available.
* Release notes: http://docs.djangoproject.com/en/dev/releases/1.3-alpha-1/
* Download instructions: http://www.djangoproject.com/download/
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You
On Tue, Oct 26, 2010 at 7:23 PM, Alex Gaynor wrote:
> It depends what you mean by "MySQL" compatible. If by that you mean
> that it's importable as mysqldb and implements the exact API it should
> work out of the box, more or less. However, if by that you mean it
> implements PEP-249 you really
On Thu, Oct 21, 2010 at 3:50 AM, Waldemar Kornewald
wrote:
> It's not even future-proof. We're heading towards larger client-side
> web apps which means there will be HTML5 offline manifests and apps
> consisting of more than 50 files. Even the combination of
> django_compressor with staticfiles c
On Thu, Oct 21, 2010 at 1:29 AM, Ivan Sagalaev
wrote:
> Can someone of core committers clarify this: is it now recommended to write
> all views as classes?
Django cares about whether your views meet the following criteria:
1. Is a callable object.
2. When called, accepts an instance of HttpReque
101 - 200 of 1014 matches
Mail list logo
