Re: [Django] #9670: django.core.mail.outbox doesn't exist anymore, remove from documentation

[Django]

#9670: django.core.mail.outbox doesn't exist anymore, remove from documentation
+---
  Reporter:  joelpittet | Owner:  nobody  
Status:  closed | Milestone:  post-1.0
 Component:  Documentation  |   Version:  1.0 
Resolution:  invalid|  Keywords:  django.core.mail
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => invalid
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 You need to read the documentation more carefully. mail.outbox is a test
 framework utility. It only exists in the context of a running test suite.
 It doesn't exist during general runtime. The existence of mail.outbox is
 validated by the test suite.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9670: django.core.mail.outbox doesn't exist anymore, remove from documentation

[Django]

#9670: django.core.mail.outbox doesn't exist anymore, remove from documentation
--+-
 Reporter:  joelpittet|   Owner:  nobody
   Status:  new   |   Milestone:  post-1.0  
Component:  Documentation | Version:  1.0   
 Keywords:  django.core.mail  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 I was doing some testing and searching and there are some references in
 the documentation about "assertEquals(len(mail.outbox), 1)"
   but mail.outbox is not defined in the mail module.

 http://docs.djangoproject.com/en/dev/topics/testing/#e-mail-services

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #494: Collapse in admin interface for inline related objects

[Django]

#494: Collapse in admin interface for inline related objects
-+--
  Reporter:  [EMAIL PROTECTED] | Owner:  xian   
 
Status:  new | Milestone:  post-1.0 
   
 Component:  django.contrib.admin|   Version:  newforms-admin   
   
Resolution:  |  Keywords:  edit_inline, 
nfa-someday
 Stage:  Design decision needed  | Has_patch:  0
   
Needs_docs:  0   |   Needs_tests:  0
   
Needs_better_patch:  1   |  
-+--
Changes (by amitu):

 * cc: [EMAIL PROTECTED] (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9653: Add a runservercp command which uses cherrypy as the main server (allows for multiple threads)

[Django]

#9653: Add a runservercp command which uses cherrypy as the main server (allows
for multiple threads)
--+-
  Reporter:  [EMAIL PROTECTED]  | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Uncategorized|   Version:  1.0   
Resolution:  wontfix  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by russellm):

 lakinwecker: You are correct in saying that you only need the dependency
 if you try to use the command. However, including something in core isn't
 just a matter of satisfying dependencies. There is also the matter of
 working out how this new piece fits with all the existing pieces.

 By including this in core, we would effectively be blessing a new method
 of Django deployment. We already have a bare-bones server for testing
 purposes, and this server is deliberately hobbled to discourage people
 using it for real deployments. We don't want to provide a second
 development server that we don't want people to use, especially as a
 CherryPy server almost _could_ be used for a real deployment.

 On top of this, a CherryPy webserver can survive as an external command.
 Since keeping this feature out of core doesn't actually prevent anyone
 from using it, IMHO the cost of including it exceeds the value by a
 significant margin.

 However, if you really feel strongly about this, bring it up on the
 Django-developers mailing list. If you can get support for the idea
 amongst other core developers, I'm happy to be overruled.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9639: Ukrainian translation (update)

[Django]

#9639: Ukrainian translation (update)
---+
  Reporter:  nickzam   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Translations  |   Version:  SVN   
Resolution:|  Keywords:  translation, uk, ukrainian
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by nickzam):

  * version:  1.0-beta-1 => SVN

Comment:

 ok, I removed translators names, #,fuzzy comments from file. I used
 gettext first time. So I knew nothing about #,fuzzy strings etc. Thank you
 for explanation.
 This translation applies to latest todays trunk, so I suppose for 1.0.x
 See django_uk patch.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9669: Innacurate answer in FAQ

[Django]

#9669: Innacurate answer in FAQ
+---
  Reporter:  Alex   | Owner:  brosner
Status:  assigned   | Milestone: 
 Component:  Documentation  |   Version:  1.0
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Comment (by ramiro):

 Perhaps the link could be replaced to one pointing to the
 CookBookNewformsAdminAndUser wikipage?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9669: Innacurate answer in FAQ

[Django]

#9669: Innacurate answer in FAQ
+---
  Reporter:  Alex   | Owner:  brosner
Status:  assigned   | Milestone: 
 Component:  Documentation  |   Version:  1.0
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by brosner):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * owner:  nobody => brosner
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9669: Innacurate answer in FAQ

[Django]

#9669: Innacurate answer in FAQ
---+
 Reporter:  Alex   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 http://docs.djangoproject.com/en/dev/faq/admin/#how-do-i-automatically-
 set-a-field-s-value-to-the-user-who-last-edited-the-object-in-the-admin

 This is not accurate for 1.0 and beyond.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9668: valid email address is not accepted

[Django]

#9668: valid email address is not accepted
--+-
 Reporter:  feuervogel|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.0   
 Keywords:  email, admin  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 when entering an email-address like

 [EMAIL PROTECTED]

 django-admin tells me this is not valid email address when entering it
 into an email field, but it is! there is a provider gmx (very popular in
 germany) where you can register an email-adress like this (the real
 address is not abc.@ but something different i can't tell because it's the
 address of a friend of mine).

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9653: Add a runservercp command which uses cherrypy as the main server (allows for multiple threads)

[Django]

#9653: Add a runservercp command which uses cherrypy as the main server (allows
for multiple threads)
--+-
  Reporter:  [EMAIL PROTECTED]  | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Uncategorized|   Version:  1.0   
Resolution:  wontfix  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by lakinwecker):

 Hi Guys,

 I'm not re-opening the ticket but I did want to suggest a few more options
 before fully giving up.

 I realize that dependencies are not something to be added lightly, but
 from my understanding this command won't be imported unless it's directly
 run.   So most people may never even notice the import cherrypy statement.
 This lowers the effect of the alleged dependency to almost none.  If
 someone notices the command and tries it without cherrypy installed I
 could make it print out a warning about the lack of CP and then fall back
 to the built-in server?

 So, I guess I'm saying that it's not really a full-blown dependency, it
 only becomes a dependency if/when you need to solve that niche problem
 which is when its useful. Maybe django could benefit from a set of not-
 officially supported commands that are included with django so that when
 someone needs them, they're easily available?   For instance if I push
 this out somewhere external to django the end user who wants to use it
 must install *both* this code and cherrypy.  If we included it, it would
 be just cherrypy that was required.

 Any chance I can get this reconsidered?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9645: Documentation generated with docutils 0.4 has broken css due to broken ids

[Django]

#9645: Documentation generated with docutils 0.4 has broken css due to broken 
ids
+---
  Reporter:  waltercruz | Owner:  ramiro
Status:  new| Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ramiro):

  * owner:  nobody => ramiro
  * version:  1.0 => SVN

Comment:

 See

  1. [http://bugs.python.org/issue3746 Sphinx bug report]
  2. Sphinx 0.4.x branch [http://svn.python.org/view?rev=66355=rev
 changeset] and
 
[http://svn.python.org/view/doctools/branches/0.4.x/sphinx/htmlwriter.py?rev=66355=diff=66355=66354=doctools/branches/0.4.x/sphinx/htmlwriter.py=/doctools/branches/0.4.x/sphinx/htmlwriter.py
 relevant diff], this change was included in Sphinx release 0.4.3
  3. Related(?) Django doc builder
 
[http://code.djangoproject.com/browser/django/trunk/docs/_ext/djangodocs.py#L131
 workaround]

 FWIW the modification in item 2 above was immediately
 [http://svn.python.org/view?view=rev=66356 ported] to Sphinx trunk so
 issue will also be present with unreleased Sphinx 0.5. I cat reproduce
 this with a recent Sphinx trunk checkout plus docutils 0.5.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #3400: [patch] Support for lookup separator with list_filter admin option

[Django]

#3400: [patch] Support for lookup separator with list_filter admin option
---+
  Reporter:  [EMAIL PROTECTED]  | Owner:  nobody
  
Status:  new   | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  newforms-admin 
 
Resolution:|  Keywords:  nfa-someday 
list_filter FilterSpec nfa-changelist ep2008
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  1 |  
---+
Changes (by HM):

 * cc: [EMAIL PROTECTED] (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9667: replace package versions with links to up-to-date searches on the distributions page

[Django]

#9667: replace package versions with links to up-to-date searches on the
distributions page
+---
 Reporter:  akaihola|   Owner:  nobody
   Status:  new |   Milestone:
Component:  Documentation   | Version:  SVN   
 Keywords:  distributions packages  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 Some information on the
 [http://docs.djangoproject.com/en/dev/misc/distributions/ Third-party
 distributions] documentation page is outdated. E.g. for Ubuntu it mentions
 0.96.1 available for Ubuntu 7.10 whereas the current 8.10 version of
 Ubuntu provides  a package for Django 1.0.

 The page probably won't get much better the way it's organized, since the
 process of updating must go through tickets and commits.

 Instead of mentioning specific versions of operating systems and Django
 versions provided for them, it would make sense to provide links to on-
 line resources where most up-to-date OS-specific information can be found.

 Here are some links to start with. They point to current Django packages
 for:
  * [http://packages.ubuntu.com/search?searchon=names=python-
 django all Ubuntu releases], see also [https://help.ubuntu.com/ Ubuntu
 documentation] on "Adding and Removing Software"
  * [http://packages.debian.org/search?searchon=names=python-
 django all Debian releases], see [http://www.debian.org/doc/user-manuals
 #apt-howto the APT HOWTO] for instructions
  * [http://rpmfind.net/linux/rpm2html/search.php?query=django RPM-based
 Linux distributions] (from rpmfind.net)
  * [http://packages.gentoo.org/package/django Gentoo]

 A page listing Django versions available for most current operating system
 releases fits better into the [http://code.djangoproject.com/wiki/ Django
 Wiki] since its updating process is more light-weight.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1142: Support for multiple database connections

[Django]

#1142: Support for multiple database connections
---+
  Reporter:  Simon Willison| Owner:  
darylspitzer 
Status:  assigned  | Milestone:  post-1.0   
  
 Component:  Database layer (models, ORM)  |   Version: 
  
Resolution:|  Keywords:  multiple 
database feature
 Stage:  Someday/Maybe | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

 * cc: [EMAIL PROTECTED] (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---