8 Why does this project exist?
9 ----------------------------
11 Django grew from a very practical need: World Online, a newspaper Web
12 operation, is responsible for building intensive Web applications on journalism
13 deadlines. In the fast-paced newsroom, World Online often has only a matter of
14 hours to take a complicated Web application from concept to public launch.
16 At the same time, the World Online Web developers have consistently been
17 perfectionists when it comes to following best practices of Web development.
19 In fall 2003, the World Online developers (Adrian Holovaty and Simon Willison)
20 ditched PHP and began using Python to develop its Web sites. As they built
21 intensive, richly interactive sites such as Lawrence.com, they began to extract
22 a generic Web development framework that let them build Web applications more
23 and more quickly. They tweaked this framework constantly, adding improvements
26 In summer 2005, World Online decided to open-source the resulting software,
27 Django. Django would not be possible without a whole host of open-source
28 projects -- `Apache`_, `Python`_, and `PostgreSQL`_ to name a few -- and we're
29 thrilled to be able to give something back to the open-source community.
31 .. _Apache: http://httpd.apache.org/
32 .. _Python: http://www.python.org/
33 .. _PostgreSQL: http://www.postgresql.org/
35 What does "Django" mean, and how do you pronounce it?
36 -----------------------------------------------------
38 Django is named after `Django Reinhardt`_, a gypsy jazz guitarist from the 1930s
39 to early 1950s. To this day, he's considered one of the best guitarists of all time.
41 Listen to his music. You'll like it.
43 Django is pronounced **JANG**-oh. Rhymes with FANG-oh. The "D" is silent.
45 We've also recorded an `audio clip of the pronunciation`_.
47 .. _Django Reinhardt: http://en.wikipedia.org/wiki/Django_Reinhardt
48 .. _audio clip of the pronunciation: http://red-bean.com/~adrian/django_pronunciation.mp3
53 Yes. World Online has been using Django for more than three years. Sites built
54 on Django have weathered traffic spikes of over one million hits an hour and a
55 number of Slashdottings. Yes, it's quite stable.
60 Yes. Compared to development time, hardware is cheap, and so Django is
61 designed to take advantage of as much hardware as you can throw at it.
63 Django uses a "shared-nothing" architecture, which means you can add hardware
64 at any level -- database servers, caching servers or Web/application servers.
66 The framework cleanly separates components such as its database layer and
67 application layer. And it ships with a simple-yet-powerful `cache framework`_.
69 .. _`cache framework`: ../cache/
74 Django was developed at `World Online`_, the Web department of a newspaper in
75 Lawrence, Kansas, USA.
78 Adrian is a Web developer with a background in journalism. He was lead
79 developer at World Online for 2.5 years, during which time Django was
80 developed and implemented on World Online's sites. Now he works for
81 washingtonpost.com building rich, database-backed information sites, and
82 continues to oversee Django development. He likes playing guitar (Django
83 Reinhardt style) and hacking on side projects such as `chicagocrime.org`_.
86 On IRC, Adrian goes by ``adrian_h``.
89 Jacob is a whipper-snapper from California who spends equal time coding and
90 cooking. He's lead developer at World Online and actively hacks on various
91 cool side projects. He's contributed to the Python-ObjC bindings and was
92 the first guy to figure out how to write Tivo apps in Python. Lately he's
93 been messing with Python on the PSP. He lives in Lawrence, Kansas.
95 On IRC, Jacob goes by ``jacobkm``.
98 Simon is a well-respected Web developer from England. He had a one-year
99 internship at World Online, during which time he and Adrian developed
100 Django from scratch. The most enthusiastic Brit you'll ever meet, he's
101 passionate about best practices in Web development and has maintained a
102 well-read Web-development blog for years at http://simon.incutio.com.
103 He works for Yahoo UK, where he managed to score the title "Hacker Liason."
106 On IRC, Simon goes by ``SimonW``.
109 Wilson's design-fu makes us all look like rock stars. By day, he's an
110 interactive designer for `Apple`_. Don't ask him what he's working on, or
111 he'll have to kill you. He lives in San Francisco.
113 On IRC, Wilson goes by ``wilsonian``.
115 .. _`World Online`: http://code.djangoproject.com/wiki/WorldOnline
116 .. _`Adrian Holovaty`: http://www.holovaty.com/
117 .. _`washingtonpost.com`: http://www.washingtonpost.com/
118 .. _`chicagocrime.org`: http://www.chicagocrime.org/
119 .. _`Simon Willison`: http://simon.incutio.com/
120 .. _`simon.incutio.com`: http://simon.incutio.com/
121 .. _`Jacob Kaplan-Moss`: http://www.jacobian.org/
122 .. _`Wilson Miner`: http://www.wilsonminer.com/
123 .. _`Apple`: http://www.apple.com/
125 Which sites use Django?
126 -----------------------
128 The Django wiki features a consistently growing `list of Django-powered sites`_.
129 Feel free to add your Django-powered site to the list.
131 .. _list of Django-powered sites: http://code.djangoproject.com/wiki/DjangoPoweredSites
133 Django appears to be a MVC framework, but you call the Controller the "view", and the View the "template". How come you don't use the standard names?
134 -----------------------------------------------------------------------------------------------------------------------------------------------------
136 Well, the standard names are debatable.
138 In our interpretation of MVC, the "view" describes the data that gets presented
139 to the user. It's not necessarily *how* the data *looks*, but *which* data is
140 presented. The view describes *which data you see*, not *how you see it.* It's
141 a subtle distinction.
143 So, in our case, a "view" is the Python callback function for a particular URL,
144 because that callback function describes which data is presented.
146 Furthermore, it's sensible to separate content from presentation -- which is
147 where templates come in. In Django, a "view" describes which data is presented,
148 but a view normally delegates to a template, which describes *how* the data is
151 Where does the "controller" fit in, then? In Django's case, it's probably the
152 framework itself: the machinery that sends a request to the appropriate view,
153 according to the Django URL configuration.
155 If you're hungry for acronyms, you might say that Django is a "MTV" framework
156 -- that is, "model", "template", and "view." That breakdown makes much more
159 At the end of the day, of course, it comes down to getting stuff done. And,
160 regardless of how things are named, Django gets stuff done in a way that's most
163 <Framework X> does <feature Y> -- why doesn't Django?
164 -----------------------------------------------------
166 We're well aware that there are other awesome Web frameworks out there, and
167 we're not averse to borrowing ideas where appropriate. However, Django was
168 developed precisely because we were unhappy with the status quo, so please be
169 aware that "because <Framework X>" does it is not going to be sufficient reason
170 to add a given feature to Django.
172 Why did you write all of Django from scratch, instead of using other Python libraries?
173 --------------------------------------------------------------------------------------
175 When Django was originally written a couple of years ago, Adrian and Simon
176 spent quite a bit of time exploring the various Python Web frameworks
179 In our opinion, none of them were completely up to snuff.
181 We're picky. You might even call us perfectionists. (With deadlines.)
183 Over time, we stumbled across open-source libraries that did things we'd
184 already implemented. It was reassuring to see other people solving similar
185 problems in similar ways, but it was too late to integrate outside code: We'd
186 already written, tested and implemented our own framework bits in several
187 production settings -- and our own code met our needs delightfully.
189 In most cases, however, we found that existing frameworks/tools inevitably had
190 some sort of fundamental, fatal flaw that made us squeamish. No tool fit our
193 Like we said: We're picky.
195 We've documented our philosophies on the `design philosophies page`_.
197 .. _design philosophies page: ../design_philosophies/
199 Do you have any of those nifty "screencast" things?
200 ---------------------------------------------------
202 You can bet your bottom they're on the way. But, since we're still hammering
203 out a few points, we want to make sure they reflect the final state of things
204 at Django 1.0, not some intermediary step. In other words, we don't want to
205 spend a lot of energy creating screencasts yet, because Django APIs will shift.
207 Is Django a content-management-system (CMS)?
208 --------------------------------------------
210 No, Django is not a CMS, or any sort of "turnkey product" in and of itself.
211 It's a Web framework; it's a programming tool that lets you build Web sites.
213 For example, it doesn't make much sense to compare Django to something like
214 Drupal_, because Django is something you use to *create* things like Drupal.
216 Of course, Django's automatic admin site is fantastic and timesaving -- but
217 the admin site is one module of Django the framework. Furthermore, although
218 Django has special conveniences for building "CMS-y" apps, that doesn't mean
219 it's not just as appropriate for building "non-CMS-y" apps (whatever that
222 .. _Drupal: http://drupal.org/
224 When will you release Django 1.0?
225 ---------------------------------
227 Short answer: When we're comfortable with Django's APIs, have added all
228 features that we feel are necessary to earn a "1.0" status, and are ready to
229 begin maintaining backwards compatibility.
231 The merging of Django's `magic-removal branch`_ went a long way toward Django
234 Of course, you should note that `quite a few production sites`_ use Django in
235 its current status. Don't let the lack of a 1.0 turn you off.
237 .. _magic-removal branch: http://code.djangoproject.com/wiki/RemovingTheMagic
238 .. _quite a few production sites: http://code.djangoproject.com/wiki/DjangoPoweredSites
240 How can I download the Django documentation to read it offline?
241 ---------------------------------------------------------------
243 The Django docs are available in the ``docs`` directory of each Django tarball
244 release. These docs are in ReST (ReStructured Text) format, and each text file
245 corresponds to a Web page on the official Django site.
247 Because the documentation is `stored in revision control`_, you can browse
248 documentation changes just like you can browse code changes.
250 Technically, the docs on Django's site are generated from the latest development
251 versions of those ReST documents, so the docs on the Django site may offer more
252 information than the docs that come with the latest Django release.
254 .. _stored in revision control: http://code.djangoproject.com/browser/django/trunk/docs
256 Where can I find Django developers for hire?
257 --------------------------------------------
259 Consult our `developers for hire page`_ for a list of Django developers who
260 would be happy to help you.
262 You might also be interested in posting a job to http://www.gypsyjobs.com/ .
264 .. _developers for hire page: http://code.djangoproject.com/wiki/DevelopersForHire
266 Installation questions
267 ======================
269 How do I get started?
270 ---------------------
272 #. `Download the code`_.
273 #. Install Django (read the `installation guide`_).
274 #. Walk through the tutorial_.
275 #. Check out the rest of the documentation_, and `ask questions`_ if you
278 .. _`Download the code`: http://www.djangoproject.com/download/
279 .. _`installation guide`: ../install/
280 .. _tutorial: ../tutorial01/
281 .. _documentation: ../
282 .. _ask questions: http://www.djangoproject.com/community/
284 How do I fix the "install a later version of setuptools" error?
285 ---------------------------------------------------------------
287 Just run the ``ez_setup.py`` script in the Django distribution.
289 What are Django's prerequisites?
290 --------------------------------
292 Django requires Python_ 2.3 or later. No other Python libraries are required
293 for basic Django usage.
295 For a development environment -- if you just want to experiment with Django --
296 you don't need to have a separate Web server installed; Django comes with its
297 own lightweight development server. For a production environment, we recommend
298 `Apache 2`_ and mod_python_, although Django follows the WSGI_ spec, which
299 means it can run on a variety of server platforms.
301 If you want to use Django with a database, which is probably the case, you'll
302 also need a database engine. PostgreSQL_ is recommended, because we're
303 PostgreSQL fans, and MySQL_, `SQLite 3`_, and Oracle_ are also supported.
305 .. _Python: http://www.python.org/
306 .. _Apache 2: http://httpd.apache.org/
307 .. _mod_python: http://www.modpython.org/
308 .. _WSGI: http://www.python.org/peps/pep-0333.html
309 .. _PostgreSQL: http://www.postgresql.org/
310 .. _MySQL: http://www.mysql.com/
311 .. _`SQLite 3`: http://www.sqlite.org/
312 .. _Oracle: http://www.oracle.com/
314 Do I lose anything by using Python 2.3 versus newer Python versions, such as Python 2.5?
315 ----------------------------------------------------------------------------------------
317 No. Django itself is guaranteed to work with any version of Python from 2.3
320 If you use a Python version newer than 2.3, you will, of course, be able to
321 take advantage of newer Python features in your own code, along with the speed
322 improvements and other optimizations that have been made to the Python language
323 itself. But the Django framework itself should work equally well on 2.3 as it
326 Do I have to use mod_python?
327 ----------------------------
329 Although we recommend mod_python for production use, you don't have to use it,
330 thanks to the fact that Django uses an arrangement called WSGI_. Django can
331 talk to any WSGI-enabled server. Other non-mod_python deployment setups are
332 FastCGI, SCGI or AJP. See `How to use Django with FastCGI, SCGI or AJP`_ for
335 Also, see the `server arrangements wiki page`_ for other deployment strategies.
337 If you just want to play around and develop things on your local computer, use
338 the development Web server that comes with Django. Things should Just Work.
340 .. _WSGI: http://www.python.org/peps/pep-0333.html
341 .. _How to use Django with FastCGI, SCGI or AJP: ../fastcgi/
342 .. _server arrangements wiki page: http://code.djangoproject.com/wiki/ServerArrangements
344 How do I install mod_python on Windows?
345 ---------------------------------------
347 * For Python 2.4, grab mod_python from `win32 build of mod_python for
349 * For Python 2.4, check out this `Django on Windows howto`_.
350 * For Python 2.3, grab mod_python from http://www.modpython.org/ and read
351 `Running mod_python on Apache on Windows2000`_.
352 * Also, try this (not Windows-specific) `guide to getting mod_python
355 .. _`win32 build of mod_python for Python 2.4`: http://www.lehuen.com/nicolas/index.php/2005/02/21/39-win32-build-of-mod_python-314-for-python-24
356 .. _`Django on Windows howto`: http://thinkhole.org/wp/django-on-windows/
357 .. _`Running mod_python on Apache on Windows2000`: http://groups-beta.google.com/group/comp.lang.python/msg/139af8c83a5a9d4f
358 .. _`guide to getting mod_python working`: http://www.dscpl.com.au/articles/modpython-001.html
360 Will Django run under shared hosting (like TextDrive or Dreamhost)?
361 -------------------------------------------------------------------
363 See our `Django-friendly Web hosts`_ page.
365 .. _`Django-friendly Web hosts`: http://code.djangoproject.com/wiki/DjangoFriendlyWebHosts
367 Should I use the official version or development version?
368 ---------------------------------------------------------
370 The Django developers improve Django every day and are pretty good about not
371 checking in broken code. We use the development code (from the Subversion
372 repository) directly on our servers, so we consider it stable. With that in
373 mind, we recommend that you use the latest development code, because it
374 generally contains more features and fewer bugs than the "official" releases.
379 Why do I get an error about importing DJANGO_SETTINGS_MODULE?
380 -------------------------------------------------------------
384 * The environment variable DJANGO_SETTINGS_MODULE is set to a fully-qualified
385 Python module (i.e. "mysite.settings").
387 * Said module is on ``sys.path`` (``import mysite.settings`` should work).
389 * The module doesn't contain syntax errors (of course).
391 * If you're using mod_python but *not* using Django's request handler,
392 you'll need to work around a mod_python bug related to the use of
393 ``SetEnv``; before you import anything from Django you'll need to do
396 os.environ.update(req.subprocess_env)
398 (where ``req`` is the mod_python request object).
400 I can't stand your template language. Do I have to use it?
401 ----------------------------------------------------------
403 We happen to think our template engine is the best thing since chunky bacon,
404 but we recognize that choosing a template language runs close to religion.
405 There's nothing about Django that requires using the template language, so
406 if you're attached to ZPT, Cheetah, or whatever, feel free to use those.
408 Do I have to use your model/database layer?
409 -------------------------------------------
411 Nope. Just like the template system, the model/database layer is decoupled from
412 the rest of the framework.
414 The one exception is: If you use a different database library, you won't get to
415 use Django's automatically-generated admin site. That app is coupled to the
416 Django database layer.
418 How do I use image and file fields?
419 -----------------------------------
421 Using a ``FileField`` or an ``ImageField`` in a model takes a few steps:
423 #. In your settings file, define ``MEDIA_ROOT`` as the full path to
424 a directory where you'd like Django to store uploaded files. (For
425 performance, these files are not stored in the database.) Define
426 ``MEDIA_URL`` as the base public URL of that directory. Make sure that
427 this directory is writable by the Web server's user account.
429 #. Add the ``FileField`` or ``ImageField`` to your model, making sure
430 to define the ``upload_to`` option to tell Django to which subdirectory
431 of ``MEDIA_ROOT`` it should upload files.
433 #. All that will be stored in your database is a path to the file
434 (relative to ``MEDIA_ROOT``). You'll must likely want to use the
435 convenience ``get_<fieldname>_url`` function provided by Django. For
436 example, if your ``ImageField`` is called ``mug_shot``, you can get the
437 absolute URL to your image in a template with
438 ``{{ object.get_mug_shot_url }}``.
443 How can I see the raw SQL queries Django is running?
444 ----------------------------------------------------
446 Make sure your Django ``DEBUG`` setting is set to ``True``. Then, just do
449 >>> from django.db import connection
450 >>> connection.queries
451 [{'sql': 'SELECT polls_polls.id,polls_polls.question,polls_polls.pub_date FROM polls_polls',
454 ``connection.queries`` is only available if ``DEBUG`` is ``True``. It's a list
455 of dictionaries in order of query execution. Each dictionary has the following::
457 ``sql`` -- The raw SQL statement
458 ``time`` -- How long the statement took to execute, in seconds.
460 ``connection.queries`` includes all SQL statements -- INSERTs, UPDATES,
461 SELECTs, etc. Each time your app hits the database, the query will be recorded.
463 Can I use Django with a pre-existing database?
464 ----------------------------------------------
466 Yes. See `Integrating with a legacy database`_.
468 .. _`Integrating with a legacy database`: ../legacy_databases/
470 If I make changes to a model, how do I update the database?
471 -----------------------------------------------------------
473 If you don't mind clearing data, your project's ``manage.py`` utility has an
474 option to reset the SQL for a particular application::
476 manage.py reset appname
478 This drops any tables associated with ``appname`` and recreates them.
480 If you do care about deleting data, you'll have to execute the ``ALTER TABLE``
481 statements manually in your database. That's the way we've always done it,
482 because dealing with data is a very sensitive operation that we've wanted to
483 avoid automating. That said, there's some work being done to add partially
484 automated database-upgrade functionality.
486 Do Django models support multiple-column primary keys?
487 ------------------------------------------------------
489 No. Only single-column primary keys are supported.
491 But this isn't an issue in practice, because there's nothing stopping you from
492 adding other constraints (using the ``unique_together`` model option or
493 creating the constraint directly in your database), and enforcing the
494 uniqueness at that level. Single-column primary keys are needed for things such
495 as the admin interface to work; e.g., you need a simple way of being able to
496 specify an object to edit or delete.
498 How do I add database-specific options to my CREATE TABLE statements, such as specifying MyISAM as the table type?
499 ------------------------------------------------------------------------------------------------------------------
501 We try to avoid adding special cases in the Django code to accommodate all the
502 database-specific options such as table type, etc. If you'd like to use any of
503 these options, create an `SQL initial data file`_ that contains ``ALTER TABLE``
504 statements that do what you want to do. The initial data files are executed in
505 your database after the ``CREATE TABLE`` statements.
507 For example, if you're using MySQL and want your tables to use the MyISAM table
508 type, create an initial data file and put something like this in it::
510 ALTER TABLE myapp_mytable ENGINE=MyISAM;
512 As explained in the `SQL initial data file`_ documentation, this SQL file can
513 contain arbitrary SQL, so you can make any sorts of changes you need to make.
515 .. _SQL initial data file: ../model-api/#providing-initial-sql-data
517 Why is Django leaking memory?
518 -----------------------------
520 Django isn't known to leak memory. If you find your Django processes are
521 allocating more and more memory, with no sign of releasing it, check to make
522 sure your ``DEBUG`` setting is set to ``True``. If ``DEBUG`` is ``True``, then
523 Django saves a copy of every SQL statement it has executed.
525 (The queries are saved in ``django.db.connection.queries``. See
526 `How can I see the raw SQL queries Django is running?`_.)
528 To fix the problem, set ``DEBUG`` to ``False``.
530 If you need to clear the query list manually at any point in your functions,
531 just call ``reset_queries()``, like this::
533 from django import db
539 I can't log in. When I enter a valid username and password, it just brings up the login page again, with no error messages.
540 ---------------------------------------------------------------------------------------------------------------------------
542 The login cookie isn't being set correctly, because the domain of the cookie
543 sent out by Django doesn't match the domain in your browser. Try these two
546 * Set the ``SESSION_COOKIE_DOMAIN`` setting in your admin config file
547 to match your domain. For example, if you're going to
548 "http://www.mysite.com/admin/" in your browser, in
549 "myproject.settings" you should set ``SESSION_COOKIE_DOMAIN = 'www.mysite.com'``.
551 * Some browsers (Firefox?) don't like to accept cookies from domains that
552 don't have dots in them. If you're running the admin site on "localhost"
553 or another domain that doesn't have a dot in it, try going to
554 "localhost.localdomain" or "127.0.0.1". And set
555 ``SESSION_COOKIE_DOMAIN`` accordingly.
557 I can't log in. When I enter a valid username and password, it brings up the login page again, with a "Please enter a correct username and password" error.
558 -----------------------------------------------------------------------------------------------------------------------------------------------------------
560 If you're sure your username and password are correct, make sure your user
561 account has ``is_active`` and ``is_staff`` set to True. The admin site only
562 allows access to users with those two fields both set to True.
564 How can I prevent the cache middleware from caching the admin site?
565 -------------------------------------------------------------------
567 Set the ``CACHE_MIDDLEWARE_ANONYMOUS_ONLY`` setting to ``True``. See the
568 `cache documentation`_ for more information.
570 .. _cache documentation: ../cache/#the-per-site-cache
572 How do I automatically set a field's value to the user who last edited the object in the admin?
573 -----------------------------------------------------------------------------------------------
575 At this point, Django doesn't have an official way to do this. But it's an oft-requested
576 feature, so we're discussing how it can be implemented. The problem is we don't want to couple
577 the model layer with the admin layer with the request layer (to get the current user). It's a
580 One person hacked up a `solution that doesn't require patching Django`_, but note that it's an
581 unofficial solution, and there's no guarantee it won't break at some point.
583 .. _solution that doesn't require patching Django: http://lukeplant.me.uk/blog.php?id=1107301634
585 How do I limit admin access so that objects can only be edited by the users who created them?
586 ---------------------------------------------------------------------------------------------
588 See the answer to the previous question.
590 My admin-site CSS and images showed up fine using the development server, but they're not displaying when using mod_python.
591 ---------------------------------------------------------------------------------------------------------------------------
593 See `serving the admin files`_ in the "How to use Django with mod_python"
596 .. _serving the admin files: ../modpython/#serving-the-admin-files
598 My "list_filter" contains a ManyToManyField, but the filter doesn't display.
599 ----------------------------------------------------------------------------
601 Django won't bother displaying the filter for a ``ManyToManyField`` if there
602 are fewer than two related objects.
604 For example, if your ``list_filter`` includes ``sites``, and there's only one
605 site in your database, it won't display a "Site" filter. In that case,
606 filtering by site would be meaningless.
608 How can I customize the functionality of the admin interface?
609 -------------------------------------------------------------
611 You've got several options. If you want to piggyback on top of an add/change
612 form that Django automatically generates, you can attach arbitrary JavaScript
613 modules to the page via the model's ``class Admin`` ``js`` parameter. That
614 parameter is a list of URLs, as strings, pointing to JavaScript modules that
615 will be included within the admin form via a ``<script>`` tag.
617 If you want more flexibility than simply tweaking the auto-generated forms,
618 feel free to write custom views for the admin. The admin is powered by Django
619 itself, and you can write custom views that hook into the authentication
620 system, check permissions and do whatever else they need to do.
622 If you want to customize the look-and-feel of the admin interface, read the
625 The dynamically-generated admin site is ugly! How can I change it?
626 ------------------------------------------------------------------
628 We like it, but if you don't agree, you can modify the admin site's
629 presentation by editing the CSS stylesheet and/or associated image files. The
630 site is built using semantic HTML and plenty of CSS hooks, so any changes you'd
631 like to make should be possible by editing the stylesheet. We've got a
632 `guide to the CSS used in the admin`_ to get you started.
634 .. _`guide to the CSS used in the admin`: ../admin_css/
636 How do I create users without having to edit password hashes?
637 -------------------------------------------------------------
639 If you'd like to use the admin site to create users, upgrade to the Django
640 development version, where this problem was fixed on Aug. 4, 2006.
642 You can also use the Python API. See `creating users`_ for full info.
644 .. _creating users: ../authentication/#creating-users
649 How can I get started contributing code to Django?
650 --------------------------------------------------
652 Thanks for asking! We've written an entire document devoted to this question.
653 It's titled `Contributing to Django`_.
655 .. _Contributing to Django: ../contributing/
657 I submitted a bug fix in the ticket system several weeks ago. Why are you ignoring my patch?
658 --------------------------------------------------------------------------------------------
660 Don't worry: We're not ignoring you!
662 It's important to understand there is a difference between "a ticket is being
663 ignored" and "a ticket has not been attended to yet." Django's ticket system
664 contains hundreds of open tickets, of various degrees of impact on end-user
665 functionality, and Django's developers have to review and prioritize.
667 Besides, if your feature request stands no chance of inclusion in Django, we
668 won't ignore it -- we'll just close the ticket. So if your ticket is still
669 open, it doesn't mean we're ignoring you; it just means we haven't had time to