[Django Code] #4111: Warning References stored in memory when DEBUG=True
#4111: Warning References stored in memory when DEBUG=True -+-- Reporter: David Cramer <[EMAIL PROTECTED]> | Owner: adrian Status: new | Component: Database wrapper Version: SVN |Keywords: Stage: Unreviewed| Has_patch: 0 -+-- Django is storing references to the "Warning" exception (from the SQL engine) in memory when DEBUG mode is turned on. I believe this is not intended as it raises memory usage considerably and I can't see it's use anywhere. -- Ticket URL: <http://code.djangoproject.com/ticket/4111> Django Code <http://code.djangoproject.com/> 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 Code] #4112: Broken Link on 0.96 Database API Reference Page
#4112: Broken Link on 0.96 Database API Reference Page ---+ Reporter: meisel | Owner: jacob Status: new | Component: Django Web site Version: 0.96|Keywords: Stage: Unreviewed | Has_patch: 0 ---+ The link from the 0.96 Database API reference page to the 0.96 Model reference page is broken. It links to /documentation/0.96/model_api/, but the correct page is /documentation/0.96/model-api/ (note the dash instead of underscore). -- Ticket URL: <http://code.djangoproject.com/ticket/4112> Django Code <http://code.djangoproject.com/> 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 Code] #4113: FileField.upload_to issues
#4113: FileField.upload_to issues
--+-
Reporter: August Bigelow <[EMAIL PROTECTED]> | Owner: adrian
Status: new| Component: Core framework
Version: 0.96 |Keywords:
Stage: Unreviewed | Has_patch: 0
--+-
From my experience, the current setup for the FileField and ImageField
attribute "upload_to" is too inflexible. While save_FIELD_file is very
quick and easy, telling the core where to put that file is not. I think
giving another class contribution could make things much more flexible.
I believe usage akin to this would work sufficiently:
{{{
#!python
class TestModel(Model):
file = FileField()
some_number = 145
t = TestModel()
t.set_file_upload_to("desired/path/%s/" % some_number)
}}}
Giving the programmer the ability to change the destination folder on the
fly would allow for more dynamic destinations. You'd be able to use IDs
from other objects and use them here.
--
Ticket URL: <http://code.djangoproject.com/ticket/4113>
Django Code <http://code.djangoproject.com/>
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 Code] #4107: [patch] Localization stuff
#4107: [patch] Localization stuff +--- Reporter: Baptiste <[EMAIL PROTECTED]> |Owner: hugo Status: new |Component: Internationalization Version: SVN | Resolution: Keywords:|Stage: Accepted Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Changes (by mtredinnick): * stage: Unreviewed => Accepted Comment: Are you marking the byte amount strings (e.g. "%f KB") for translation just so that the numbers are presented in the correct locale (1,234 vs. 1.234)? The strings KB, GB, etc, should not be marked for translation, since they are international abbreviations, hence it would be good to leave them out of the PO file to avoid confusion If you could clarify what your intention is here, I'll fix it up when I commit this. No need to generate another patch. -- Ticket URL: <http://code.djangoproject.com/ticket/4107#comment:2> Django Code <http://code.djangoproject.com/> 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 Code] #4108: [patch] french PO file
#4108: [patch] french PO file +--- Reporter: Baptiste <[EMAIL PROTECTED]> |Owner: hugo Status: new |Component: Internationalization Version: SVN | Resolution: Keywords:|Stage: Ready for checkin Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Changes (by mtredinnick): * needs_better_patch: => 0 * stage: Unreviewed => Ready for checkin * needs_tests: => 0 * needs_docs: => 0 Comment: Localflavours will be used outside of the local language (in some cases there isn't just one local language, after all). What if you are designing a site for French people travelling to Germany? You'll need a list of French states and I'll want to translate them into the terms commonly used in France for those regions. It's the same reason country and language names are marked for translation -- you aren't going to use Deutschland as the name of the country on a French language website. -- Ticket URL: <http://code.djangoproject.com/ticket/4108#comment:1> Django Code <http://code.djangoproject.com/> 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 Code] #4108: [patch] french PO file
#4108: [patch] french PO file +--- Reporter: Baptiste <[EMAIL PROTECTED]> |Owner: hugo Status: new |Component: Internationalization Version: SVN | Resolution: Keywords:|Stage: Ready for checkin Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Comment (by mtredinnick): Err .. replace "French states" with "German states" in the above. We are going for German states in the French language in that example. I need more coffee. :-( -- Ticket URL: <http://code.djangoproject.com/ticket/4108#comment:2> Django Code <http://code.djangoproject.com/> 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 Code] #3324: FloatFields are converted to decimal and simplejson cannot serialize
#3324: FloatFields are converted to decimal and simplejson cannot serialize --+- Reporter: [EMAIL PROTECTED] |Owner: jacob Status: reopened|Component: Serialization Version: SVN | Resolution: Keywords: json decimal|Stage: Ready for checkin Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 --+- Changes (by [EMAIL PROTECTED]): * cc: [EMAIL PROTECTED] (added) Comment: It would be nice to return a Decimal on deserialization, rather than returning a float as is done by the current patch. -- Ticket URL: <http://code.djangoproject.com/ticket/3324#comment:14> Django Code <http://code.djangoproject.com/> 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 Code] #4107: [patch] Localization stuff
#4107: [patch] Localization stuff +--- Reporter: Baptiste <[EMAIL PROTECTED]> |Owner: hugo Status: new |Component: Internationalization Version: SVN | Resolution: Keywords:|Stage: Accepted Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Comment (by Baptiste <[EMAIL PROTECTED]>): Actually, KB is not as international as you think :[[ BR ]] eg., in France, a "Byte" is an "octet" (even if it is not exactly the same thing, that is the word we use). So for us, "KB" is an English notation, we write "Ko". Some people may understand, just like they would understand "yes" or "no", but this is still not French. -- Ticket URL: <http://code.djangoproject.com/ticket/4107#comment:3> Django Code <http://code.djangoproject.com/> 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 Code] #4108: [patch] french PO file
#4108: [patch] french PO file +--- Reporter: Baptiste <[EMAIL PROTECTED]> |Owner: hugo Status: new |Component: Internationalization Version: SVN | Resolution: Keywords:|Stage: Ready for checkin Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Comment (by Baptiste <[EMAIL PROTECTED]>): Okay, fine. Damned, translating that is going to be awful :D -- Ticket URL: <http://code.djangoproject.com/ticket/4108#comment:3> Django Code <http://code.djangoproject.com/> 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 Code] #4114: ForeignKey and OneToOneField should take the verbose_name of target field by default
#4114: ForeignKey and OneToOneField should take the verbose_name of target field
by default
---+
Reporter: anonymous | Owner: adrian
Status: new | Component: Database wrapper
Version: SVN |Keywords: ForeignKey OneToOneField verbose_name
Stage: Unreviewed | Has_patch: 1
---+
In order to get a user-friendly and localize-ready field name in the Admin
site, {{{ForeignKey}}} and {{{OneToOneField}}} should take the
{{{verbose_name}}} of target field by default. Otherwise you'll have to
write something like this:
{{{
Foo = ForeignKey(Bar, verbose_name=Bar._meta.verbose_name)
}}}
That would violate the DRY principle.
Here's a patch for Django svn revision 5056, which modifies
{{{django/db/models/fields/related.py}}}.
--
Ticket URL: <http://code.djangoproject.com/ticket/4114>
Django Code <http://code.djangoproject.com/>
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 Code] #852: psycopg.ProgrammingError exceptions leave the connection to the DB in an unusable state
#852: psycopg.ProgrammingError exceptions leave the connection to the DB in an unusable state -+-- Reporter: [EMAIL PROTECTED] |Owner: adrian Status: closed |Component: Database wrapper Version: | Resolution: wontfix Keywords: |Stage: Unreviewed Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 -+-- Comment (by [EMAIL PROTECTED]): Since the only way to exit the bad state is to do a rollback, shouldnt Django do a rollback by default if it encounters a programming error by psycopg? This would eliminate the need to do everything in a try: except: . My 2c. Rahul Pilani -- Ticket URL: <http://code.djangoproject.com/ticket/852#comment:25> Django Code <http://code.djangoproject.com/> 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 Code] #4115: contrib.thumbnails
#4115: contrib.thumbnails +--- Reporter: SmileyChris | Owner: adrian Status: new | Component: Contrib apps Version: SVN |Keywords: Stage: Unreviewed | Has_patch: 1 +--- The idea has been bantered about in the dev group, so I thought I'd put together something to start the ball rolling at least. -- Ticket URL: <http://code.djangoproject.com/ticket/4115> Django Code <http://code.djangoproject.com/> 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 Code] #4116: Bad cross-links in 0.95 tutorial
#4116: Bad cross-links in 0.95 tutorial --+- Reporter: [EMAIL PROTECTED] | Owner: jacob Status: new| Component: Documentation Version: 0.95 |Keywords: Stage: Unreviewed | Has_patch: 0 --+- On page http://www.djangoproject.com/documentation/0.95/tutorial01/: Link "part 2 of this tutorial" (at the bottom of the page) links to http://www.djangoproject.com/documentation/tutorial2/ but should link to http://www.djangoproject.com/documentation/0.95/tutorial02/ Similarly for "next part" links in parts 2 and 3. -- Ticket URL: <http://code.djangoproject.com/ticket/4116> Django Code <http://code.djangoproject.com/> 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 Code] #3370: [patch] newforms: form.save() raises UnicodeEncodeError when form contains any non latin characters
#3370: [patch] newforms: form.save() raises UnicodeEncodeError when form contains any non latin characters -+-- Reporter: [EMAIL PROTECTED] |Owner: adrian Status: new|Component: django.newforms Version: SVN| Resolution: Keywords: newforms utf8 |Stage: Design decision needed Has_patch: 1 | Needs_docs: 0 Needs_tests: 1 | Needs_better_patch: 1 -+-- Changes (by anonymous): * cc: [EMAIL PROTECTED] (added) Comment: -- Ticket URL: <http://code.djangoproject.com/ticket/3370#comment:18> Django Code <http://code.djangoproject.com/> 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 Code] #4094: when using finnish, databrowse with calendars does not translate the month back to english resulting in an error
#4094: when using finnish, databrowse with calendars does not translate the month back to english resulting in an error ---+ Reporter: lawgon <[EMAIL PROTECTED]> |Owner: adrian Status: new |Component: django.contrib.databrowse Version: SVN | Resolution: Keywords: |Stage: Accepted Has_patch: 0| Needs_docs: 0 Needs_tests: 0| Needs_better_patch: 0 ---+ Comment (by lawgon <[EMAIL PROTECTED]>): same problem in polish - so it must be i18n generic issue -- Ticket URL: <http://code.djangoproject.com/ticket/4094#comment:2> Django Code <http://code.djangoproject.com/> 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 Code] #4115: contrib.thumbnails
#4115: contrib.thumbnails ---+ Reporter: SmileyChris |Owner: adrian Status: new |Component: Contrib apps Version: SVN | Resolution: Keywords: |Stage: Unreviewed Has_patch: 1| Needs_docs: 0 Needs_tests: 0| Needs_better_patch: 0 ---+ Changes (by bin): * needs_better_patch: => 0 * needs_tests: => 0 * needs_docs: => 0 Comment: Good initiative Chris. Some time ago I gave a shot at creating a set of generic views to interface with PIL in a RESTful manner. Maybe it's a nice idea to consider adding generic views to your contrib. Regards, bin -- Ticket URL: <http://code.djangoproject.com/ticket/4115#comment:1> Django Code <http://code.djangoproject.com/> 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 Code] #4117: Attributes for Widgets composed of more than one HTML element
#4117: Attributes for Widgets composed of more than one HTML element
+---
Reporter: Iwan Vosloo | Owner: adrian
Status: new | Component: django.newforms
Version: SVN |Keywords: attrs, RadioSelect, MultiWidget
Stage: Unreviewed | Has_patch: 0
+---
As suggested in #3870, I'm adding this ticket.
With widgets (such as {{RadioSelect}} or {{MultiWidget}}) that are
rendered as several HTML elements/inputs one sometimes need a way to
attach HTML attributes to the widget as a whole so that you can style its
constituent parts using a stylesheet.
Please see the reason for this request in http://groups.google.com/group/
django-developers/browse_thread/thread/e55be1c11893c069
A naïve implementation would be that if you construct the widget with
attrs= keyword argument, they should be used as HTML attributes on a
suitable element (as in #4080). It seems, however, as if the norm is as
in #3870.
I believe a design decision is needed here: #4080 does one thing with
attrs, #3870 does another thing with attrs. For general styling, I think
#4080 is the way to go, but it appeared to me that #3870 makes sense in
other cases. (For example if you want to set readonly attribute on the
entire widget, it should be set on all inputs it is composed of).
-i
--
Ticket URL: <http://code.djangoproject.com/ticket/4117>
Django Code <http://code.djangoproject.com/>
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 Code] #952: [patch] Allow for database client encoding configuration from project settings
#952: [patch] Allow for database client encoding configuration from project settings ---+ Reporter: [EMAIL PROTECTED] |Owner: adrian Status: reopened |Component: Database wrapper Version: SVN | Resolution: Keywords: |Stage: Design decision needed Has_patch: 1| Needs_docs: 0 Needs_tests: 0| Needs_better_patch: 1 ---+ Changes (by anonymous): * cc: [EMAIL PROTECTED] (removed) * cc: [EMAIL PROTECTED], [EMAIL PROTECTED] (added) Comment: -- Ticket URL: <http://code.djangoproject.com/ticket/952#comment:60> Django Code <http://code.djangoproject.com/> 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 Code] #4022: Problem with select fields and foreign keys
#4022: Problem with select fields and foreign keys
+---
Reporter: [EMAIL PROTECTED] |Owner: jacob
Status: reopened |Component: Uncategorized
Version: 0.96 | Resolution:
Keywords:|Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
+---
Changes (by [EMAIL PROTECTED]):
* status: closed => reopened
* resolution: worksforme =>
Comment:
Ok, so I've made a very simple app to demonstrate the problem (no custom
manipulators or anything). Hopefully my formatting will work this time :).
models.py
{{{
from django.db import models
class Foo(models.Model):
name = models.CharField(maxlength = 100)
def __str__(self):
return self.name
class Admin:
pass
class Bar(models.Model):
field1 = models.ForeignKey(Foo)
field2 = models.CharField(maxlength = 1, choices = (('1', 'first
choice'), ('2', 'second choice')))
}}}
views.py
{{{
from django.shortcuts import render_to_response
from django import forms
from myapp.formtest.models import Bar
def create(request):
errors = new_data = {}
manipulator = Bar.AddManipulator()
if request.POST:
new_data = request.POST.copy()
errors = manipulator.get_validation_errors(new_data)
if not errors:
manipulator.do_html2python(new_data)
manipulator.save(new_data)
request.session['message'] = 'Bar Created'
return HttpResponseRedirect('/formtest')
form = forms.FormWrapper(manipulator, new_data, errors)
return render_to_response('formtest/bar_form.html', {'form': form})
}}}
And finally, my bar_form.html
{{{
{% if form.error_dict %}
Please correct the error below.
{% endif %}
Field1: {{ form.field1 }}
Field2: {{ form.field2 }}
}}}
Both field1 and field2 are required. So if only one of the two fields is
set on the form, it won't save and will return an error. If field2 is set,
it remains set when the page returns with an error message. However, if
field1 (the foreign key field) is set (but not field2) the page returns
with an error, but with neither fields set. So field1 gets reset.
--
Ticket URL: <http://code.djangoproject.com/ticket/4022#comment:4>
Django Code <http://code.djangoproject.com/>
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 Code] #4118: dead link
#4118: dead link ---+ Reporter: anonymous | Owner: jacob Status: new | Component: Documentation Version: 0.96|Keywords: Stage: Unreviewed | Has_patch: 0 ---+ http://www.djangoproject.com/documentation/0.96/db_api/ -- Ticket URL: <http://code.djangoproject.com/ticket/4118> Django Code <http://code.djangoproject.com/> 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 Code] #4119: Incorrect HTTP-Date format in expire field of HTTP Header
#4119: Incorrect HTTP-Date format in expire field of HTTP Header ---+ Reporter: Ciantic | Owner: adrian Status: new | Component: Contrib apps Version: SVN |Keywords: http-date header Stage: Unreviewed | Has_patch: 1 ---+ Currently the Django uses `datetime.strftime` to format it's ''HTTP- Date'', because strftime is localized function it should not be used for it. Changing locales to something else than English will break Django's session system on some browsers at the current state. Using `datetime.ctime` instead makes Django's HTTP-Date format automatically correct and it is not anymore locale dependent. `ctime` function also automatically handles the GMT conversion if needed, that is why the patch also changes the `utcnow` to `now`. It conforms the HTTP Specification clearly as in here [http://www.w3.org/Protocols/rfc2616/ rfc2616-sec3.html#sec3.3 HTTP Specs] is stated (the third choice). This fixes only expire field in `django.contrib.session.middleware` but the problem might be elsewhere too (mostly where HTTP-Date is used). Common rule is that `strftime` is not meant for fixed date formats. -- Ticket URL: <http://code.djangoproject.com/ticket/4119> Django Code <http://code.djangoproject.com/> 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 Code] #4119: Incorrect HTTP-Date format in expire field of HTTP Header
#4119: Incorrect HTTP-Date format in expire field of HTTP Header +--- Reporter: Ciantic |Owner: adrian Status: new |Component: Contrib apps Version: SVN | Resolution: Keywords: http-date header |Stage: Unreviewed Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Changes (by Ciantic): * needs_better_patch: => 0 * needs_tests: => 0 * needs_docs: => 0 Comment: Sorry about the duplicate patch, but apparently the first patch had wrong path. -- Ticket URL: <http://code.djangoproject.com/ticket/4119#comment:1> Django Code <http://code.djangoproject.com/> 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 Code] #4120: some admin Javascript cleanups
#4120: some admin Javascript cleanups ---+ Reporter: arvin | Owner: jacob Status: new | Component: Uncategorized Version: SVN |Keywords: javascript admin Stage: Unreviewed | Has_patch: 1 ---+ Here are the pure javascript cleanups from ticket 4045. -- Ticket URL: <http://code.djangoproject.com/ticket/4120> Django Code <http://code.djangoproject.com/> 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 Code] #4045: some admin Javascript fixes and cleanups
#4045: some admin Javascript fixes and cleanups --+- Reporter: arvin |Owner: adrian Status: new |Component: Admin interface Version: SVN | Resolution: Keywords: admin calendar |Stage: Accepted Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 1 --+- Comment (by arvin): The patch with the pure cleanup is in ticket #4120. Since a patch with the pure changes would conflict I thinks it's best I make a new patch against the SVN for this ticket when the other thing is through. -- Ticket URL: <http://code.djangoproject.com/ticket/4045#comment:3> Django Code <http://code.djangoproject.com/> 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 Code] #4120: some admin Javascript cleanups
#4120: some admin Javascript cleanups +--- Reporter: arvin |Owner: adrian Status: new |Component: Admin interface Version: SVN | Resolution: Keywords: javascript admin |Stage: Unreviewed Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Changes (by anonymous): * owner: jacob => adrian * needs_better_patch: => 0 * component: Uncategorized => Admin interface * needs_tests: => 0 * needs_docs: => 0 Comment: -- Ticket URL: <http://code.djangoproject.com/ticket/4120#comment:1> Django Code <http://code.djangoproject.com/> 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 Code] #4119: Incorrect HTTP-Date format in expire field of HTTP Header
#4119: Incorrect HTTP-Date format in expire field of HTTP Header +--- Reporter: Ciantic |Owner: adrian Status: new |Component: Contrib apps Version: SVN | Resolution: Keywords: http-date header |Stage: Unreviewed Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Comment (by Ciantic): One addition, the orginal "%a, %d-%b-%Y %H:%M:%S GMT" even in plain English is incorrect. It does not conform any of those three in [http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.3 HTTP Specs]. So if this patch is not added then patch with strftime fixed is needed. -- Ticket URL: <http://code.djangoproject.com/ticket/4119#comment:2> Django Code <http://code.djangoproject.com/> 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 Code] #4013: bad links on previous versions of tutorial pages
#4013: bad links on previous versions of tutorial pages -+-- Reporter: [EMAIL PROTECTED] |Owner: jacob Status: new|Component: Django Web site Version: SVN| Resolution: Keywords: Tutorial |Stage: Accepted Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 -+-- Changes (by SmileyChris): * summary: bad link on 0.96 tutorial 01 page => bad links on previous versions of tutorial pages Comment: -- Ticket URL: <http://code.djangoproject.com/ticket/4013#comment:6> Django Code <http://code.djangoproject.com/> 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 Code] #4116: Bad cross-links in 0.95 tutorial
#4116: Bad cross-links in 0.95 tutorial -+-- Reporter: [EMAIL PROTECTED] |Owner: jacob Status: closed |Component: Documentation Version: 0.95 | Resolution: duplicate Keywords: |Stage: Unreviewed Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 -+-- Changes (by SmileyChris): * status: new => closed * needs_better_patch: => 0 * resolution: => duplicate * needs_tests: => 0 * needs_docs: => 0 Comment: Dupe of #4013 -- Ticket URL: <http://code.djangoproject.com/ticket/4116#comment:1> Django Code <http://code.djangoproject.com/> 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 Code] #4018: Allow callable values as initial for newforms-fields
#4018: Allow callable values as initial for newforms-fields -+-- Reporter: David Danier <[EMAIL PROTECTED]> |Owner: adrian Status: new| Component: django.newforms Version: SVN| Resolution: Keywords: lazydate newforms initial callable | Stage: Ready for checkin Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 -+-- Changes (by SmileyChris): * needs_better_patch: => 0 * stage: Unreviewed => Ready for checkin * needs_tests: => 0 * needs_docs: => 0 Comment: Thanks David. Probably only other suggestion is that it could do with a test or two, but it's a simple enough patch that I won't let that hold up the process. -- Ticket URL: <http://code.djangoproject.com/ticket/4018#comment:1> Django Code <http://code.djangoproject.com/> 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 Code] #4119: Incorrect HTTP-Date format in expire field of HTTP Header
#4119: Incorrect HTTP-Date format in expire field of HTTP Header +--- Reporter: Ciantic |Owner: adrian Status: new |Component: Contrib apps Version: SVN | Resolution: Keywords: http-date header |Stage: Ready for checkin Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Changes (by Simon G. <[EMAIL PROTECTED]>): * stage: Unreviewed => Ready for checkin Comment: -- Ticket URL: <http://code.djangoproject.com/ticket/4119#comment:3> Django Code <http://code.djangoproject.com/> 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 Code] #4115: contrib.thumbnails
#4115: contrib.thumbnails ---+ Reporter: SmileyChris |Owner: adrian Status: new |Component: Contrib apps Version: SVN | Resolution: Keywords: |Stage: Design decision needed Has_patch: 1| Needs_docs: 0 Needs_tests: 0| Needs_better_patch: 0 ---+ Changes (by Simon G. <[EMAIL PROTECTED]>): * stage: Unreviewed => Design decision needed Comment: -- Ticket URL: <http://code.djangoproject.com/ticket/4115#comment:2> Django Code <http://code.djangoproject.com/> 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 Code] #4106: Typo (important) in datastructures.py - MultiValueDict
#4106: Typo (important) in datastructures.py - MultiValueDict ---+ Reporter: Amr Mostafa |Owner: adrian Status: new |Component: Core framework Version: SVN | Resolution: Keywords: |Stage: Ready for checkin Has_patch: 1| Needs_docs: 0 Needs_tests: 0| Needs_better_patch: 0 ---+ Changes (by Gary Wilson <[EMAIL PROTECTED]>): * needs_better_patch: => 0 * stage: Unreviewed => Ready for checkin * needs_tests: => 0 * needs_docs: => 0 Comment: -- Ticket URL: <http://code.djangoproject.com/ticket/4106#comment:1> Django Code <http://code.djangoproject.com/> 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 Code] #4105: [Patch] New tag to generate URLs for media files
#4105: [Patch] New tag to generate URLs for media files
---+
Reporter: Amr Mostafa |Owner: adrian
Status: new |Component: Template system
Version: SVN | Resolution:
Keywords: |Stage: Unreviewed
Has_patch: 1| Needs_docs: 0
Needs_tests: 0| Needs_better_patch: 0
---+
Changes (by [EMAIL PROTECTED]):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
For this sort of thing I just use a context processor to add the MEDIA_URL
setting to my templates. The code would then become:
{{{}}}
See the patch on ticket #1278, or James Bennett's
[http://www.b-list.org/weblog/2007/04/12/django-template-utilities
template_utils] for an example of this.
Note: Since this is dependent on having a RequestContext for the context
processors to be applied, I also have have a % media_url %
template tag to accomplish the same thing in templates that aren't able to
use a RequestContext (e.g. emails).
Note 2: On a somewhat related sidenote, I also have % css % and
% javascript % tags that I use to do css/js imports automatically
that take template inheritance into account, so I can add additional
imports to child templates. This is kind of a specialist case though, and
outside the scope of the Django core.
--
Ticket URL: <http://code.djangoproject.com/ticket/4105#comment:1>
Django Code <http://code.djangoproject.com/>
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 Code] #4121: DateTime, Date, Time, MonthDay, YearMonth for general usage
#4121: DateTime, Date,Time, MonthDay, YearMonth for general usage ---+ Reporter: Ciantic | Owner: adrian Status: new | Component: Core framework Version: SVN |Keywords: Stage: Unreviewed | Has_patch: 1 ---+ Currently Django does not let one to use the great functions `django.utils.translation.get_date_formats`, `get_partial_date_formats` in any handy way. The following method adds all DateTime, Date, Time, MonthDay, YearMonth for general usage. Names come from common naming: * `c` Datetime, appropriate date and time representation (for example same name in strftime) * `x` Date, appropriate date representation. e.g. '2007-04-23' (for example same name in strftime) * `X` Datetime, appropriate date and time representation. e.g. '2007-04- 23 4:13' (for example same name in strftime) * `k` Month day, appropriate month day representation. e.g. 'January 5' (I Invented the "k" naming) * `K` Year month, appropriate year month representation. e.g. '2007 January' (I invented the "K" naming) This allows one to use all of the above in `date` filter and in `now` tag. -- Ticket URL: <http://code.djangoproject.com/ticket/4121> Django Code <http://code.djangoproject.com/> 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 Code] #4121: DateTime, Date, Time, MonthDay, YearMonth for general usage
#4121: DateTime, Date,Time, MonthDay, YearMonth for general usage ---+ Reporter: Ciantic |Owner: adrian Status: new |Component: Core framework Version: SVN | Resolution: Keywords: |Stage: Unreviewed Has_patch: 1| Needs_docs: 0 Needs_tests: 0| Needs_better_patch: 0 ---+ Changes (by Ciantic): * needs_better_patch: => 0 * needs_tests: => 0 * needs_docs: => 0 Comment: Fix to the body of document: * c Datetime, appropriate date and time representation e.g. '2007-04- 23 4:13' (for example same name in strftime) * x Date, appropriate date representation. e.g. '2007-04-23' (for example same name in strftime) * X Time, appropriate time representation. e.g. '4:13' (for example same name in strftime) * k Month day, appropriate month day representation. e.g. 'January 5' (I Invented the "k" naming) * K Year month, appropriate year month representation. e.g. '2007 January' (I invented the "K" naming) -- Ticket URL: <http://code.djangoproject.com/ticket/4121#comment:1> Django Code <http://code.djangoproject.com/> 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 Code] #4105: [Patch] New tag to generate URLs for media files
#4105: [Patch] New tag to generate URLs for media files ---+ Reporter: Amr Mostafa |Owner: adrian Status: new |Component: Template system Version: SVN | Resolution: Keywords: |Stage: Unreviewed Has_patch: 1| Needs_docs: 0 Needs_tests: 0| Needs_better_patch: 0 ---+ Comment (by [EMAIL PROTECTED]): Oops I somehow neglected to notice the attached patch, so ignore the links re: context processors :-) I don't know if it's necessary to check for the existence of the media file though, as I would assume you'd only be trying to include files that you know exist. -- Ticket URL: <http://code.djangoproject.com/ticket/4105#comment:2> Django Code <http://code.djangoproject.com/> 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 Code] #4122: Chilean localflavor, national identity number.
#4122: Chilean localflavor, national identity number. -+-- Reporter: marijn <[EMAIL PROTECTED]> | Owner: adrian Status: new | Component: django.contrib.localflavor Version: SVN |Keywords: Stage: Unreviewed| Has_patch: 1 -+-- Added a patch a localflavor for a field with the Chilean national personal identity number (RUT). A list of valid RUTs can be found here: [https://palena.sii.cl/cvc/dte/ee_empresas_emisoras.html] -- Ticket URL: <http://code.djangoproject.com/ticket/4122> Django Code <http://code.djangoproject.com/> 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 Code] #4123: firstof template tag doesn't accept strings with spaces
#4123: firstof template tag doesn't accept strings with spaces
--+-
Reporter: Wesley Fok <[EMAIL PROTECTED]> | Owner: adrian
Status: new| Component: Template
system
Version: SVN|Keywords:
Stage: Unreviewed | Has_patch: 0
--+-
When firstof is passed a quoted string with a space, ex. {% firstof var1
var2 var3 "fallback string" %}, it splits the string and reads the pieces
as False. If the string is the last element in the firstof tag, then the
whole thing returns False and firstof returns a blank string.
--
Ticket URL: <http://code.djangoproject.com/ticket/4123>
Django Code <http://code.djangoproject.com/>
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 Code] #1796: [patch] "Cannot resolve keyword ___ into field" error when working with ManyToMany relation
#1796: [patch] "Cannot resolve keyword ___ into field" error when working with
ManyToMany relation
-+--
Reporter: anonymous |Owner: mtredinnick
Status: reopened |Component: Database wrapper
Version: SVN| Resolution:
Keywords: |Stage: Accepted
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-+--
Comment (by Yann VR):
I've uncommented the line Øyvind indicated but same problem for me.
It works fine using the shell, (reqroute_proto is the m2m key):
{{{
>>> from mt.models import MtReqroute
>>> entry=MtReqroute.objects.get(pk=1)
>>> entry.reqroute_proto.all()
[, ]
}}}
Now on the server, trying to retrieve the data through
a flattened manipulator:
Fails "Cannot resolve keyword 'mtreqroute' into field"
{{{
Traceback (most recent call last):
File "/home/yannvr/C4/django/core/handlers/base.py" in get_response
77. response = callback(request, *callback_args, **callback_kwargs)
File "/home/yannvr/C4/django/contrib/auth/decorators.py" in _checklogin
14. return view_func(request, *args, **kwargs)
File "/var/www/MT/mt/views/routes.py" in edit_route
54. new_data = manipulator.flatten_data()
File "/home/yannvr/C4/django/db/models/manipulators.py" in flatten_data
248. new_data.update(f.flatten_data(fol, obj))
File "/home/yannvr/C4/django/db/models/fields/related.py" in flatten_data
700. instance_ids = [instance._get_pk_val() for instance in getattr(obj,
self.name).all()]
File "/var/www/MT/django/db/models/query.py" in __iter__
108. return iter(self._get_data())
File "/var/www/MT/django/db/models/query.py" in _get_data
470. self._result_cache = list(self.iterator())
File "/var/www/MT/django/db/models/query.py" in iterator
174. select, sql, params = self._get_sql_clause()
File "/var/www/MT/django/db/models/query.py" in _get_sql_clause
484. joins2, where2, params2 = self._filters.get_sql(opts)
File "/var/www/MT/django/db/models/query.py" in get_sql
648. joins2, where2, params2 = val.get_sql(opts)
File "/var/www/MT/django/db/models/query.py" in get_sql
699. return parse_lookup(self.kwargs.items(), opts)
File "/var/www/MT/django/db/models/query.py" in parse_lookup
833. joins2, where2, params2 = lookup_inner(path, lookup_type, value,
opts, opts.db_table, None)
File "/var/www/MT/django/db/models/query.py" in lookup_inner
940. raise TypeError, "Cannot resolve keyword '%s' into field" % name
}}}
The middleware running on my server are:
MIDDLEWARE_CLASSES = (
'django.middleware.common.CommonMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.middleware.doc.XViewMiddleware',
)
The moment is goes wrong is when trying to lookup
for that field
{{{
File "/var/www/MT/django/db/models/query.py" in __iter__
108. return iter(self._get_data())
self= Error in formatting:Cannot resolve keyword 'mtreqroute' into field
}}}
--
Ticket URL: <http://code.djangoproject.com/ticket/1796#comment:58>
Django Code <http://code.djangoproject.com/>
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 Code] #4124: Hierarchical Many-To-One relation presentation in admin page
#4124: Hierarchical Many-To-One relation presentation in admin page
---+
Reporter: anonymous | Owner: adrian
Status: new | Component: Admin interface
Version: 0.96|Keywords: Hierarchical Many-To-One admin
Stage: Unreviewed | Has_patch: 0
---+
Models:
{{{
Person --> Group --> Department
n:1 n:1
}}}
Using ''edit_inline'' in Person and Group, but only the first layer is
displayed, we can't see the Person's fields in Department.
--
Ticket URL: <http://code.djangoproject.com/ticket/4124>
Django Code <http://code.djangoproject.com/>
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 Code] #4121: DateTime, Date, Time, MonthDay, YearMonth for general usage
#4121: DateTime, Date,Time, MonthDay, YearMonth for general usage ---+ Reporter: Ciantic |Owner: adrian Status: new |Component: Core framework Version: SVN | Resolution: Keywords: |Stage: Design decision needed Has_patch: 1| Needs_docs: 0 Needs_tests: 0| Needs_better_patch: 0 ---+ Changes (by mtredinnick): * stage: Unreviewed => Design decision needed Comment: -- Ticket URL: <http://code.djangoproject.com/ticket/4121#comment:2> Django Code <http://code.djangoproject.com/> 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 Code] #4018: Allow callable values as initial for newforms-fields
#4018: Allow callable values as initial for newforms-fields -+-- Reporter: David Danier <[EMAIL PROTECTED]> |Owner: adrian Status: new| Component: django.newforms Version: SVN| Resolution: Keywords: lazydate newforms initial callable | Stage: Accepted Has_patch: 1 | Needs_docs: 0 Needs_tests: 1 | Needs_better_patch: 0 -+-- Changes (by mtredinnick): * needs_tests: 0 => 1 * stage: Ready for checkin => Accepted Comment: Yep, needs tests before it can go. The easy patches are the easiest ones to write tests for. There is no excuse. -- Ticket URL: <http://code.djangoproject.com/ticket/4018#comment:2> Django Code <http://code.djangoproject.com/> 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 Code] #4125: datastructures EasyQuerySet (+ small fixes)
#4125: datastructures EasyQuerySet (+ small fixes) +--- Reporter: SmileyChris | Owner: adrian Status: new | Component: Contrib apps Version: SVN |Keywords: Stage: Unreviewed | Has_patch: 1 +--- Here's a working implementation to make the calendar views work properly. It also fixes a couple of small annoyances I had: * provide `base_site.html` to override * show "X objects for field" when on an object list page -- Ticket URL: <http://code.djangoproject.com/ticket/4125> Django Code <http://code.djangoproject.com/> 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 Code] #4107: [patch] Localization stuff
#4107: [patch] Localization stuff
+---
Reporter: Baptiste <[EMAIL PROTECTED]> |Owner: hugo
Status: closed|Component:
Internationalization
Version: SVN | Resolution:
fixed
Keywords:|Stage:
Accepted
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
+---
Comment (by anonymous):
The admindocs directory does not exist on trunk -- only on the newforms-
admin branch. Please open another ticket with that change (and put {{{[
newforms-admin]}}} at the start of the title). We don't want to mix
patches for trunk and patches from branches in one ticket, because they
are handled by different people.
--
Ticket URL: <http://code.djangoproject.com/ticket/4107#comment:5>
Django Code <http://code.djangoproject.com/>
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 Code] #4107: [patch] Localization stuff
#4107: [patch] Localization stuff +--- Reporter: Baptiste <[EMAIL PROTECTED]> |Owner: hugo Status: closed|Component: Internationalization Version: SVN | Resolution: fixed Keywords:|Stage: Accepted Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Comment (by mtredinnick): Oops... last comment was by me. -- Ticket URL: <http://code.djangoproject.com/ticket/4107#comment:6> Django Code <http://code.djangoproject.com/> 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 Code] #4108: [patch] french PO file
#4108: [patch] french PO file
+---
Reporter: Baptiste <[EMAIL PROTECTED]> |Owner: hugo
Status: new |Component:
Translations
Version: SVN | Resolution:
Keywords:|Stage:
Accepted
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
+---
Changes (by mtredinnick):
* component: Internationalization => Translations
* stage: Ready for checkin => Accepted
Comment:
I can't commit this yet: there is a format string error at line 1333.
Please remember to run {{{bin/compile-messages.py -l fr}}} on the PO file
before submitting to catch these. I guess it might be that you are
accidently translating the newforms-admin branch instead of trunk -- we
aren't applying translation patches to branches, so please only submit
patches against trunk.
Move back to "ready for checkin" once the error has been fixed so that we
know it's ready.
--
Ticket URL: <http://code.djangoproject.com/ticket/4108#comment:4>
Django Code <http://code.djangoproject.com/>
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 Code] #4126: TypeError when edit_inline and Multiple ForeignKeys to same model breaks the admin
#4126: TypeError when edit_inline and Multiple ForeignKeys to same model breaks
the admin
---+
Reporter: dan <[EMAIL PROTECTED]> | Owner: jacob
Status: new | Component: Uncategorized
Version: SVN |Keywords: m2m intermediary
Stage: Unreviewed | Has_patch: 0
---+
This is ''almost'' a duplicate of #1939, however, I am getting a
!TypeError instead of a !KeyError.
Minimal example (a commenter to #2522 had the same use case in mind):
{{{
from django.db import models
class Node(models.Model):
name = models.CharField('Name', maxlength=30, unique=True)
def __str__(self):
return self.name
class Admin:
pass
class Link(models.Model):
from_node=models.ForeignKey(Node, related_name='has_links_to',
edit_inline=True)
to_node=models.ForeignKey(Node, related_name='has_links_from',
core=True)
strength=models.FloatField('Strength', max_digits=3, decimal_places=2,
core=True)
}}}
Trying to add a Node through the Admin gives this traceback (SVN r5061):
{{{
Traceback (most recent call last):
File "C:\cygwin\home\Dan\src\django_src\django\template\__init__.py" in
render_node
723. result = node.render(context)
File "C:\cygwin\home\Dan\src\django_src\django\template\defaulttags.py" in
render
125. nodelist.append(node.render(context))
File
"C:\cygwin\home\Dan\src\django_src\django\contrib\admin\templatetags\admin_modify.py"
in render
170. bound_related_object = relation.bind(context['form'], original,
bound_related_object_class)
File "C:\cygwin\home\Dan\src\django_src\django\db\models\related.py" in
bind
129. return bound_related_object_class(self, field_mapping, original)
TypeError at /admin/ntwk/node/add/
'bool' object is not callable
}}}
--
Ticket URL: <http://code.djangoproject.com/ticket/4126>
Django Code <http://code.djangoproject.com/>
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 Code] #4018: Allow callable values as initial for newforms-fields
#4018: Allow callable values as initial for newforms-fields -+-- Reporter: David Danier <[EMAIL PROTECTED]> |Owner: adrian Status: new| Component: django.newforms Version: SVN| Resolution: Keywords: lazydate newforms initial callable | Stage: Accepted Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 -+-- Changes (by David Danier <[EMAIL PROTECTED]>): * needs_tests: 1 => 0 Comment: Replying to [comment:2 mtredinnick]: > Yep, needs tests before it can go. The easy patches are the easiest ones to write tests for. There is no excuse. So the new patch includes some tests ;-) -- Ticket URL: <http://code.djangoproject.com/ticket/4018#comment:3> Django Code <http://code.djangoproject.com/> 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 Code] #4099: Version 0.96 does not work with psycopg2-2.0.6b2
#4099: Version 0.96 does not work with psycopg2-2.0.6b2 -+-- Reporter: [EMAIL PROTECTED] |Owner: mtredinnick Status: new|Component: Database wrapper Version: 0.96 | Resolution: Keywords: |Stage: Accepted Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 -+-- Comment (by [EMAIL PROTECTED]): I've found same problem and submitted this to psycopg collector. There is an answer from them. Take a look: http://initd.org/tracker/psycopg/ticket/178#comment:1 -- Ticket URL: <http://code.djangoproject.com/ticket/4099#comment:2> Django Code <http://code.djangoproject.com/> 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 Code] #3472: Convince send_mail to not base64-encode the email
#3472: Convince send_mail to not base64-encode the email ---+ Reporter: Matthias Urlichs <[EMAIL PROTECTED]> |Owner: adrian Status: new |Component: django.core.mail Version: SVN | Resolution: Keywords: base64, send_mail|Stage: Ready for checkin Has_patch: 1| Needs_docs: 0 Needs_tests: 0| Needs_better_patch: 0 ---+ Comment (by [EMAIL PROTECTED]): Perhaps the mime encoding type should be configured in the settings. Quoted-printable might not be the best choice for non-latin languages, while base64 may cause spam filter issues. There is a [http://trac.edgewall.org/ticket/1754 ticket discussing this issue] on trac's trac. -- Ticket URL: <http://code.djangoproject.com/ticket/3472#comment:6> Django Code <http://code.djangoproject.com/> 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 Code] #4107: [patch] Localization stuff
#4107: [patch] Localization stuff +--- Reporter: Baptiste <[EMAIL PROTECTED]> |Owner: hugo Status: closed|Component: Internationalization Version: SVN | Resolution: fixed Keywords:|Stage: Accepted Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Comment (by Baptiste <[EMAIL PROTECTED]>): Thanks for the commit. Okay for the admindocs, sorry for the mistake, but I often forget that I am using newforms-admin ;-) -- Ticket URL: <http://code.djangoproject.com/ticket/4107#comment:7> Django Code <http://code.djangoproject.com/> 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 Code] #4108: [patch] french PO file
#4108: [patch] french PO file +--- Reporter: Baptiste <[EMAIL PROTECTED]> |Owner: hugo Status: new |Component: Translations Version: SVN | Resolution: Keywords:|Stage: Ready for checkin Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Changes (by Baptiste <[EMAIL PROTECTED]>): * stage: Accepted => Ready for checkin Comment: Sorry for the error, I'll now use compile-messages before uploading the patches ; I didn't know that tool. -- Ticket URL: <http://code.djangoproject.com/ticket/4108#comment:5> Django Code <http://code.djangoproject.com/> 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 Code] #4105: [Patch] New tag to generate URLs for media files
#4105: [Patch] New tag to generate URLs for media files ---+ Reporter: Amr Mostafa |Owner: adrian Status: new |Component: Template system Version: SVN | Resolution: Keywords: |Stage: Unreviewed Has_patch: 1| Needs_docs: 0 Needs_tests: 0| Needs_better_patch: 0 ---+ Comment (by Amr Mostafa): Thanks for taking a look ;-), It's perfectly possible to do this in the userland (with Django, what isn't anyway ;-) but I believe that this's something normally expected from Django itself, and is needed by almost everybody. Implementation as a tag is more natural to the user IMHO. I thought the existence check is useful because: * It will save your server from the 404 hits (I assume user would also have other resources than CSS/Javascript, e.g. images). * It's easier to spot the empty strings than it's to spot typos when you view-source your template when you suspect something is wrong. Thanks again, I'd love to get more feedback! -- Ticket URL: <http://code.djangoproject.com/ticket/4105#comment:3> Django Code <http://code.djangoproject.com/> 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 Code] #4127: broken link to QuerySet DB API in 0.96 documentation
#4127: broken link to QuerySet DB API in 0.96 documentation -+-- Reporter: [EMAIL PROTECTED] | Owner: jacob Status: new | Component: Django Web site Version: 0.96 |Keywords: wiki broken link Stage: Unreviewed| Has_patch: 0 -+-- Hi, reading your excelent doc today I found that link from page http://www.djangoproject.com/documentation/0.96/generic_views/ to DB AAI (http://www.djangoproject.com/documentation/0.96/db_api/) near "Most generic views require the queryset key, which is a QuerySet instance; see the database API docs for more information about Queryset objects." does not work. You have undescore insted of hyphen in your wiki link. Best regards robert -- Ticket URL: <http://code.djangoproject.com/ticket/4127> Django Code <http://code.djangoproject.com/> 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 Code] #4121: DateTime, Date, Time, MonthDay, YearMonth for general usage
#4121: DateTime, Date,Time, MonthDay, YearMonth for general usage ---+ Reporter: Ciantic |Owner: adrian Status: new |Component: Core framework Version: SVN | Resolution: Keywords: |Stage: Design decision needed Has_patch: 1| Needs_docs: 0 Needs_tests: 0| Needs_better_patch: 0 ---+ Comment (by Ciantic): I see this patch or some modification of this patch as necessity. Representations of full formats in own locale is not in wide use and people don't even seem to know about them. Most of programs just happily uses incorrect ways to format datetimes in their templates and views, e.g. hardcoded finnish format "23.4.2007 13:25" or English format. But because Django '''already supports localed representations''' why not to give easy way to use them? One possibility is to create ''templatetags'' (similar as now tag) and ''filters'' (similar as date filter) for each of those ''hidden features'' of Django. But I see it is more sane and natural to add these ''hidden features'' to the actual Formatters so using them is most common (e.g. syntax is similar as strftime's syntax). Please note, that Formatters '''already consists these types of full formats''' like: * `r` RFC 822 formatted date. 'Thu, 21 Dec 2000 16:01:07 +0200' So adding these common full formats to formatters does not collide with any "no full formats here" type of idea, which also backs up the idea adding these to the Formatters directly, rather than creating own templatetags and filters. -- Ticket URL: <http://code.djangoproject.com/ticket/4121#comment:3> Django Code <http://code.djangoproject.com/> 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 Code] #4099: psycopg2-2.0.6b2 does not allow lists in cursor.execute
#4099: psycopg2-2.0.6b2 does not allow lists in cursor.execute
-+--
Reporter: [EMAIL PROTECTED] |Owner: mtredinnick
Status: new|Component: Database wrapper
Version: 0.96 | Resolution:
Keywords: |Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-+--
Changes (by mtredinnick):
* summary: Version 0.96 does not work with psycopg2-2.0.6b2 =>
psycopg2-2.0.6b2 does not allow lists in
cursor.execute
Comment:
What a shame. That's a bad design choice on psycopg's part. There is no
good technical reason to allow tuples and not lists in that
{{{cursor.execute()}}} --- any sequence-like object should work.
We're going to have to work around their choice then. Fortunately, it
shouldn't be too hard. Changing title to reflect the real problem.
--
Ticket URL: <http://code.djangoproject.com/ticket/4099#comment:3>
Django Code <http://code.djangoproject.com/>
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 Code] #4128: Django 0.96 installation problem in Windows XP.
#4128: Django 0.96 installation problem in Windows XP. ---+ Reporter: [EMAIL PROTECTED] | Owner: adrian Status: new | Component: Admin interface Version: 0.96|Keywords: Install problem, Django 0.96, Windows XP Stage: Unreviewed | Has_patch: 1 ---+ Hello good folks, A short description - Django 0.96 does not install on Windows XP. The command "setup.py install" ( or "setup.py build" ) does not work... it gives the following error output: running install running build running build_py error: package directory '\django' does not exist I hacked around a bit and found the problem in the setup.py file. The original relevant portion is: # Compile the list of packages available, because distutils doesn't have # an easy way to do this. packages, data_files = [], [] root_dir = os.path.dirname(__file__) len_root_dir = len(root_dir) django_dir = os.path.join(root_dir, 'django') I reckoned that the "root directory" was not being recognised properly... so I made the following change: # Compile the list of packages available, because distutils doesn't have # an easy way to do this. packages, data_files = [], [] root_dir = "C:\\Django-0.96\\Django-0.96\\" (NOTE: I manually added the 'root' directory pertinent to my system) len_root_dir = len(root_dir) django_dir = os.path.join(root_dir, 'django') The above worked like magic without any hassles. So what's up guys, is this a bug or what? BTW, I had the latest installer tool : setuptools-0.6c5-py2.5.exe installed in my system. Thanks and Regards, Timmy Jose (a.k.a z0ltan) -- Ticket URL: <http://code.djangoproject.com/ticket/4128> Django Code <http://code.djangoproject.com/> 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 Code] #4128: Django 0.96 installation problem in Windows XP.
#4128: Django 0.96 installation problem in Windows XP.
+---
Reporter: [EMAIL PROTECTED]|Owner: adrian
Status: new |Component:
Tools
Version: 0.96 | Resolution:
Keywords: Install problem, Django 0.96, Windows XP |Stage:
Accepted
Has_patch: 1 | Needs_docs:
0
Needs_tests: 0 | Needs_better_patch:
0
+---
Changes (by mtredinnick):
* needs_better_patch: => 0
* component: Admin interface => Tools
* needs_tests: => 0
* needs_docs: => 0
* stage: Unreviewed => Accepted
Old description:
> Hello good folks,
> A short description - Django 0.96 does not install on Windows XP.
> The command "setup.py install" ( or "setup.py build" ) does not work...
> it gives the following error output:
>
> running install
> running build
> running build_py
> error: package directory '\django' does not exist
>
> I hacked around a bit and found the problem in the setup.py file. The
> original relevant portion is:
>
> # Compile the list of packages available, because distutils doesn't have
> # an easy way to do this.
> packages, data_files = [], []
> root_dir = os.path.dirname(__file__)
> len_root_dir = len(root_dir)
> django_dir = os.path.join(root_dir, 'django')
>
>
> I reckoned that the "root directory" was not being recognised properly...
> so I made the following change:
>
> # Compile the list of packages available, because distutils doesn't have
> # an easy way to do this.
> packages, data_files = [], []
> root_dir = "C:\\Django-0.96\\Django-0.96\\" (NOTE: I manually added
> the 'root' directory pertinent to my system)
> len_root_dir = len(root_dir)
> django_dir = os.path.join(root_dir, 'django')
>
> The above worked like magic without any hassles. So what's up guys, is
> this a bug or what? BTW, I had the latest installer tool :
> setuptools-0.6c5-py2.5.exe installed in my system.
>
> Thanks and Regards,
>
> Timmy Jose (a.k.a z0ltan)
New description:
Hello good folks,
A short description - Django 0.96 does not install on Windows XP.
The command "setup.py install" ( or "setup.py build" ) does not work... it
gives the following error output:
running install
running build
running build_py
error: package directory '\django' does not exist
I hacked around a bit and found the problem in the setup.py file. The
original relevant portion is:
{{{
#!python
# Compile the list of packages available, because distutils doesn't have
# an easy way to do this.
packages, data_files = [], []
root_dir = os.path.dirname(__file__)
len_root_dir = len(root_dir)
django_dir = os.path.join(root_dir, 'django')
}}}
I reckoned that the "root directory" was not being recognised properly...
so I made the following change:
{{{
#!python
# Compile the list of packages available, because distutils doesn't have
# an easy way to do this.
packages, data_files = [], []
root_dir = "C:\\Django-0.96\\Django-0.96\\" (NOTE: I manually added
the 'root' directory pertinent to my system)
len_root_dir = len(root_dir)
django_dir = os.path.join(root_dir, 'django')
}}}
The above worked like magic without any hassles. So what's up guys, is
this a bug or what? BTW, I had the latest installer tool :
setuptools-0.6c5-py2.5.exe installed in my system.
Thanks and Regards,
Timmy Jose (a.k.a z0ltan)
Comment:
(Fixed up wiki-formatting in summary.)
Can you print out what the value of {{{__file__}}} is when you run
setup.py? Just put in a print statement before the line that sets
{{{root_dir}}}. I'm trying to work out if {{{__file__}}} is not set
correctly or if {{{os.path.dirname()}}} is returning the wrong thing.
--
Ticket URL: <http://code.djangoproject.com/ticket/4128#comment:1>
Django Code <http://code.djangoproject.com/>
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 Code] #4128: Django 0.96 installation problem in Windows XP.
#4128: Django 0.96 installation problem in Windows XP.
+---
Reporter: [EMAIL PROTECTED]|Owner: adrian
Status: new |Component:
Tools
Version: 0.96 | Resolution:
Keywords: Install problem, Django 0.96, Windows XP |Stage:
Accepted
Has_patch: 1 | Needs_docs:
0
Needs_tests: 0 | Needs_better_patch:
0
+---
Old description:
> Hello good folks,
> A short description - Django 0.96 does not install on Windows XP.
> The command "setup.py install" ( or "setup.py build" ) does not work...
> it gives the following error output:
>
> running install
> running build
> running build_py
> error: package directory '\django' does not exist
>
> I hacked around a bit and found the problem in the setup.py file. The
> original relevant portion is:
>
> {{{
> #!python
> # Compile the list of packages available, because distutils doesn't have
> # an easy way to do this.
> packages, data_files = [], []
> root_dir = os.path.dirname(__file__)
> len_root_dir = len(root_dir)
> django_dir = os.path.join(root_dir, 'django')
> }}}
>
> I reckoned that the "root directory" was not being recognised properly...
> so I made the following change:
>
> {{{
> #!python
> # Compile the list of packages available, because distutils doesn't have
> # an easy way to do this.
> packages, data_files = [], []
> root_dir = "C:\\Django-0.96\\Django-0.96\\" (NOTE: I manually added
> the 'root' directory pertinent to my system)
> len_root_dir = len(root_dir)
> django_dir = os.path.join(root_dir, 'django')
> }}}
>
> The above worked like magic without any hassles. So what's up guys, is
> this a bug or what? BTW, I had the latest installer tool :
> setuptools-0.6c5-py2.5.exe installed in my system.
>
> Thanks and Regards,
>
> Timmy Jose (a.k.a z0ltan)
New description:
Hello good folks,
A short description - Django 0.96 does not install on Windows XP.
The command "setup.py install" ( or "setup.py build" ) does not work... it
gives the following error output:
{{{
running install
running build
running build_py
error: package directory '\django' does not exist
}}}
I hacked around a bit and found the problem in the setup.py file. The
original relevant portion is:
{{{
#!python
# Compile the list of packages available, because distutils doesn't have
# an easy way to do this.
packages, data_files = [], []
root_dir = os.path.dirname(__file__)
len_root_dir = len(root_dir)
django_dir = os.path.join(root_dir, 'django')
}}}
I reckoned that the "root directory" was not being recognised properly...
so I made the following change:
{{{
#!python
# Compile the list of packages available, because distutils doesn't have
# an easy way to do this.
packages, data_files = [], []
root_dir = "C:\\Django-0.96\\Django-0.96\\" (NOTE: I manually added
the 'root' directory pertinent to my system)
len_root_dir = len(root_dir)
django_dir = os.path.join(root_dir, 'django')
}}}
The above worked like magic without any hassles. So what's up guys, is
this a bug or what? BTW, I had the latest installer tool :
setuptools-0.6c5-py2.5.exe installed in my system.
Thanks and Regards,
Timmy Jose (a.k.a z0ltan)
Comment (by mtredinnick):
--
Ticket URL: <http://code.djangoproject.com/ticket/4128#comment:2>
Django Code <http://code.djangoproject.com/>
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 Code] #4128: Django 0.96 installation problem in Windows XP.
#4128: Django 0.96 installation problem in Windows XP. +--- Reporter: [EMAIL PROTECTED]|Owner: adrian Status: new |Component: Tools Version: 0.96 | Resolution: Keywords: Install problem, Django 0.96, Windows XP |Stage: Accepted Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Comment (by Simon G. <[EMAIL PROTECTED]>): Duplicate of #4082 and #3245. I've closed those others as this looks like it has more info. -- Ticket URL: <http://code.djangoproject.com/ticket/4128#comment:3> Django Code <http://code.djangoproject.com/> 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 Code] #4082: build_py error: package directory '\django' does not exist
#4082: build_py error: package directory '\django' does not exist -+-- Reporter: [EMAIL PROTECTED] |Owner: jacob Status: closed |Component: Documentation Version: 0.96 | Resolution: duplicate Keywords: windows setup |Stage: Unreviewed Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 -+-- Comment (by Simon G. <[EMAIL PROTECTED]>): Closed in favor of #4128 -- Ticket URL: <http://code.djangoproject.com/ticket/4082#comment:2> Django Code <http://code.djangoproject.com/> 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 Code] #3245: setup.py error on windows when installing from a second level directory
#3245: setup.py error on windows when installing from a second level directory +--- Reporter: dall |Owner: adrian Status: reopened |Component: Uncategorized Version:| Resolution: Keywords: windows installation |Stage: Accepted Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Comment (by Simon G. <[EMAIL PROTECTED]>): #4182 appears to be a duplicate. -- Ticket URL: <http://code.djangoproject.com/ticket/3245#comment:7> Django Code <http://code.djangoproject.com/> 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 Code] #4129: Named urls break view prefix.
#4129: Named urls break view prefix.
--+-
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new| Component: Core framework
Version: SVN|Keywords: named, urls, view, prefix
Stage: Unreviewed | Has_patch: 0
--+-
The following code results in a ViewDoesNotExist exception for
'archive_index' (assuming "info_dict" contains the needed parameters):
{{{
urlpatterns = patterns('django.views.generic.date_based',
url(r'^articles/?$', 'archive_index', info_dict, name="article-
archive-index")
)
}}}
This works fine:
{{{
urlpatterns = patterns('',
url(r'^articles/?$', 'django.views.generic.date_based.archive_index',
info_dict, name="article-archive-index")
)
}}}
View prefixes do not seem to work for custom views either when used in
conjunction with named urls.
--
Ticket URL: <http://code.djangoproject.com/ticket/4129>
Django Code <http://code.djangoproject.com/>
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 Code] #1796: [patch] "Cannot resolve keyword ___ into field" error when working with ManyToMany relation
#1796: [patch] "Cannot resolve keyword ___ into field" error when working with ManyToMany relation -+-- Reporter: anonymous |Owner: mtredinnick Status: reopened |Component: Database wrapper Version: SVN| Resolution: Keywords: |Stage: Accepted Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 -+-- Comment (by Ben Slavin <[EMAIL PROTECTED]>): Just got bit by this one again. It only appeared in modpython, not in the shell, and not using the built- in server (runserver). I've attached a patch that forces preemptive model loading in the modpython handler. As with the management shell patch, this should be considered a temporary workaround. -- Ticket URL: <http://code.djangoproject.com/ticket/1796#comment:59> Django Code <http://code.djangoproject.com/> 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 Code] #4129: Named urls break view prefix.
#4129: Named urls break view prefix. -+-- Reporter: [EMAIL PROTECTED] |Owner: adrian Status: new|Component: Core framework Version: SVN| Resolution: Keywords: named, urls, view, prefix |Stage: Unreviewed Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 -+-- Changes (by mtredinnick): * needs_better_patch: => 0 * needs_tests: => 0 * needs_docs: => 0 Comment: What do you have to do to cause this error? You explain what error is raised, but what are you doing when it is raised -- using reverse()? Doing a normal url lookup? Other? -- Ticket URL: <http://code.djangoproject.com/ticket/4129#comment:1> Django Code <http://code.djangoproject.com/> 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 Code] #4129: Named urls break view prefix.
#4129: Named urls break view prefix. -+-- Reporter: [EMAIL PROTECTED] |Owner: adrian Status: new|Component: Core framework Version: SVN| Resolution: Keywords: named, urls, view, prefix |Stage: Unreviewed Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 -+-- Comment (by anonymous): Replying to [comment:1 mtredinnick]: > What do you have to do to cause this error? You explain what error is raised, but what are you doing when it is raised -- using reverse()? Doing a normal url lookup? Other? The error is raised when accessing the URL normally. I have not tested doing a reverse lookup as the primary functionality seems to be broken. -- Ticket URL: <http://code.djangoproject.com/ticket/4129#comment:2> Django Code <http://code.djangoproject.com/> 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 Code] #4004: Need a newforms.FloatField field
#4004: Need a newforms.FloatField field --+- Reporter: tonnzor <[EMAIL PROTECTED]> |Owner: anonymous Status: assigned|Component: django.newforms Version: SVN | Resolution: Keywords: |Stage: Accepted Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 --+- Changes (by tonnzor <[EMAIL PROTECTED]>): * owner: adrian => anonymous * status: new => assigned * has_patch: 0 => 1 Comment: Patch seems a bit complicated, but it supports `max_digits` and `decimal_places` parameters (similar to `django.db.models.FloatField`) Error messages might be improved. The patch contains test suite too. -- Ticket URL: <http://code.djangoproject.com/ticket/4004#comment:2> Django Code <http://code.djangoproject.com/> 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 Code] #4004: Need a newforms.FloatField field
#4004: Need a newforms.FloatField field --+- Reporter: tonnzor <[EMAIL PROTECTED]> |Owner: anonymous Status: assigned|Component: django.newforms Version: SVN | Resolution: Keywords: |Stage: Accepted Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 --+- Comment (by tonnzor <[EMAIL PROTECTED]>): I have a patch, but see no field to attach it to this ticket :( -- Ticket URL: <http://code.djangoproject.com/ticket/4004#comment:3> Django Code <http://code.djangoproject.com/> 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 Code] #4130: When mistyping a field name in an ORM call, the error message could be a lot more helpful.
#4130: When mistyping a field name in an ORM call, the error message could be a lot more helpful. --+- Reporter: [EMAIL PROTECTED] | Owner: adrian Status: new| Component: Core framework Version: SVN|Keywords: Stage: Unreviewed | Has_patch: 0 --+- If I make a mistake when creating a filter call, the error message simply says, "Cannot resolve keyword 'pollls' into field". More helpful is to show what the possible fields are: "Cannot resolve keyword 'pollls' into field, choices are: polls, cats, dogs" Attached is a patch that changes the message in this way. -- Ticket URL: <http://code.djangoproject.com/ticket/4130> Django Code <http://code.djangoproject.com/> 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 Code] #4130: [patch] When mistyping a field name in an ORM call, the error message could be a lot more helpful.
#4130: [patch] When mistyping a field name in an ORM call, the error message could be a lot more helpful. -+-- Reporter: [EMAIL PROTECTED] |Owner: adrian Status: new|Component: Core framework Version: SVN| Resolution: Keywords: |Stage: Unreviewed Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 -+-- Changes (by anonymous): * needs_better_patch: => 0 * summary: When mistyping a field name in an ORM call, the error message could be a lot more helpful. => [patch] When mistyping a field name in an ORM call, the error message could be a lot more helpful. * needs_tests: => 0 * needs_docs: => 0 Comment: -- Ticket URL: <http://code.djangoproject.com/ticket/4130#comment:1> Django Code <http://code.djangoproject.com/> 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 Code] #4130: When mistyping a field name in an ORM call, the error message could be a lot more helpful.
#4130: When mistyping a field name in an ORM call, the error message could be a lot more helpful. -+-- Reporter: [EMAIL PROTECTED] |Owner: adrian Status: new|Component: Core framework Version: SVN| Resolution: Keywords: |Stage: Unreviewed Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 -+-- Changes (by mtredinnick): * has_patch: 0 => 1 * summary: [patch] When mistyping a field name in an ORM call, the error message could be a lot more helpful. => When mistyping a field name in an ORM call, the error message could be a lot more helpful. Comment: anonymous: Please don't change titles to include the word [patch]. It wastes space. We have a checkbox for that purpose (indicating patches, not wasting space). -- Ticket URL: <http://code.djangoproject.com/ticket/4130#comment:2> Django Code <http://code.djangoproject.com/> 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 Code] #4131: [patch] addslashes isn't sufficient to protect literal strings in embedded JavaScript code
#4131: [patch] addslashes isn't sufficient to protect literal strings in
embedded
JavaScript code
---+
Reporter: Ned Batchelder <[EMAIL PROTECTED]> | Owner: adrian
Status: new | Component: Template
system
Version: SVN |Keywords:
Stage: Unreviewed | Has_patch: 0
---+
When creating literal strings in embedded JavaScript code, the addslashes
filter is used to escape characters significant to JavaScript:
var x = "{{x|addslashes}}";
blah(x);
But if the variable x includes the string "", then this script
block is ended too early, and the page is broken.
Attached is a patch that also escapes the http://code.djangoproject.com/ticket/4131>
Django Code <http://code.djangoproject.com/>
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 Code] #4124: Hierarchical Many-To-One relation presentation in admin page
#4124: Hierarchical Many-To-One relation presentation in admin page --+- Reporter: anonymous |Owner: adrian Status: new |Component: Admin interface Version: 0.96| Resolution: Keywords: Hierarchical Many-To-One admin |Stage: Design decision needed Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 --+- Changes (by Gary Wilson <[EMAIL PROTECTED]>): * needs_better_patch: => 0 * stage: Unreviewed => Design decision needed * needs_tests: => 0 * needs_docs: => 0 Comment: -- Ticket URL: <http://code.djangoproject.com/ticket/4124#comment:1> Django Code <http://code.djangoproject.com/> 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 Code] #4128: Django 0.96 installation problem in Windows XP.
#4128: Django 0.96 installation problem in Windows XP. +--- Reporter: [EMAIL PROTECTED]|Owner: adrian Status: closed|Component: Tools Version: 0.96 | Resolution: duplicate Keywords: Install problem, Django 0.96, Windows XP |Stage: Accepted Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Changes (by Gary Wilson <[EMAIL PROTECTED]>): * status: new => closed * resolution: => duplicate Comment: Closing this since #3245 was re-opened and Malcolm has mentioned there that this was probably fixed as of [4912]. If someone can confirm this, please comment on #3245 and resolve that ticket as fixed. -- Ticket URL: <http://code.djangoproject.com/ticket/4128#comment:4> Django Code <http://code.djangoproject.com/> 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 Code] #3245: setup.py error on windows when installing from a second level directory
#3245: setup.py error on windows when installing from a second level directory +--- Reporter: dall |Owner: adrian Status: reopened |Component: Uncategorized Version:| Resolution: Keywords: windows installation |Stage: Accepted Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Comment (by Gary Wilson <[EMAIL PROTECTED]>): Replying to [comment:7 Simon G. <[EMAIL PROTECTED]>]: > #4182 appears to be a duplicate. I believe you mean #4128. -- Ticket URL: <http://code.djangoproject.com/ticket/3245#comment:8> Django Code <http://code.djangoproject.com/> 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 Code] #4115: contrib.thumbnails
#4115: contrib.thumbnails ---+ Reporter: SmileyChris |Owner: adrian Status: new |Component: Contrib apps Version: SVN | Resolution: Keywords: |Stage: Design decision needed Has_patch: 1| Needs_docs: 0 Needs_tests: 0| Needs_better_patch: 0 ---+ Changes (by brosner <[EMAIL PROTECTED]>): * cc: [EMAIL PROTECTED] (added) Comment: -- Ticket URL: <http://code.djangoproject.com/ticket/4115#comment:3> Django Code <http://code.djangoproject.com/> 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 Code] #4132: Polish translation update
#4132: Polish translation update --+- Reporter: Michal Chruszcz <[EMAIL PROTECTED]> | Owner: hugo Status: new| Component: Translations Version: SVN|Keywords: polish Stage: Unreviewed | Has_patch: 0 --+- Updated and cleaned up Polish translation of django.po. Conforms current version of SVN trunk. -- Ticket URL: <http://code.djangoproject.com/ticket/4132> Django Code <http://code.djangoproject.com/> 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 Code] #4129: Named urls break view prefix.
#4129: Named urls break view prefix. -+-- Reporter: [EMAIL PROTECTED] |Owner: adrian Status: new|Component: Core framework Version: SVN| Resolution: Keywords: named, urls, view, prefix |Stage: Unreviewed Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 -+-- Comment (by Gary Wilson <[EMAIL PROTECTED]>): You will see this error if you try performing a normal URL lookup by browsing to `.../articles/` since the prefix parameter from the `patterns()` call doesn't get passed along to the the `url()` call. The prefix only gets passed along when using url conf tuples. -- Ticket URL: <http://code.djangoproject.com/ticket/4129#comment:3> Django Code <http://code.djangoproject.com/> 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 Code] #4129: Named urls break view prefix.
#4129: Named urls break view prefix. -+-- Reporter: [EMAIL PROTECTED] |Owner: adrian Status: new|Component: Core framework Version: SVN| Resolution: Keywords: named, urls, view, prefix |Stage: Unreviewed Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 -+-- Comment (by [EMAIL PROTECTED]): Is that the intended functionality that url prefixes and named urls are incompatible? If so, it should be reflected in the documentation. Right now the docs show the url prefix empty but make no mention of it not working with the url() function. I haven't looked at the source yet, and do not know the complexity involved, but I would like to see the two play nicely together. -- Ticket URL: <http://code.djangoproject.com/ticket/4129#comment:4> Django Code <http://code.djangoproject.com/> 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 Code] #4130: When mistyping a field name in an ORM call, the error message could be a lot more helpful.
#4130: When mistyping a field name in an ORM call, the error message could be a lot more helpful. -+-- Reporter: [EMAIL PROTECTED] |Owner: adrian Status: new|Component: Core framework Version: SVN| Resolution: Keywords: |Stage: Unreviewed Has_patch: 1 | Needs_docs: 0 Needs_tests: 1 | Needs_better_patch: 0 -+-- Changes (by Karen Tracey <[EMAIL PROTECTED]>): * needs_tests: 0 => 1 Comment: FYI there are a couple of tests in tests/modeltests/lookup/models.py that test for this error message. They will need to be changed if the error message changes. -- Ticket URL: <http://code.djangoproject.com/ticket/4130#comment:3> Django Code <http://code.djangoproject.com/> 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 Code] #4127: broken link to QuerySet DB API in 0.96 documentation
#4127: broken link to QuerySet DB API in 0.96 documentation +--- Reporter: [EMAIL PROTECTED] |Owner: jacob Status: new |Component: Django Web site Version: 0.96 | Resolution: Keywords: wiki broken link |Stage: Ready for checkin Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Changes (by Gary Wilson <[EMAIL PROTECTED]>): * needs_better_patch: => 0 * stage: Unreviewed => Ready for checkin * needs_tests: => 0 * needs_docs: => 0 Comment: -- Ticket URL: <http://code.djangoproject.com/ticket/4127#comment:1> Django Code <http://code.djangoproject.com/> 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 Code] #4112: Broken Link on 0.96 Database API Reference Page
#4112: Broken Link on 0.96 Database API Reference Page --+- Reporter: meisel |Owner: jacob Status: new |Component: Django Web site Version: 0.96| Resolution: Keywords: |Stage: Ready for checkin Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 --+- Changes (by Gary Wilson <[EMAIL PROTECTED]>): * needs_better_patch: => 0 * stage: Unreviewed => Ready for checkin * needs_tests: => 0 * needs_docs: => 0 Comment: -- Ticket URL: <http://code.djangoproject.com/ticket/4112#comment:1> Django Code <http://code.djangoproject.com/> 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 Code] #3096: Filtering choices in admin list view don't respond to limit_choices_to parameter
#3096: Filtering choices in admin list view don't respond to limit_choices_to
parameter
-+--
Reporter: Archatas (aidas.bendoraitis at gmail.com) |
Owner: adrian
Status: new|
Component: Admin interface
Version: SVN|
Resolution:
Keywords: |
Stage: Accepted
Has_patch: 1 |
Needs_docs: 0
Needs_tests: 0 |
Needs_better_patch: 0
-+--
Comment (by Archatas):
I found one case, where it fails: that is when Q() objects instead of
dictionaries are used to limit the choices. Here is the simple fix:
{{{
if f.rel.limit_choices_to:
if type(f.rel.limit_choices_to).__name__ == "dict":
self.lookup_choices =
f.rel.to._default_manager.filter(**f.rel.limit_choices_to)
else:
self.lookup_choices =
f.rel.to._default_manager.filter(f.rel.limit_choices_to)
else:
self.lookup_choices = f.rel.to._default_manager.all()
}}}
--
Ticket URL: <http://code.djangoproject.com/ticket/3096#comment:5>
Django Code <http://code.djangoproject.com/>
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 Code] #4104: Webdesgin link from 0.96 docs is wrong
#4104: Webdesgin link from 0.96 docs is wrong --+- Reporter: [EMAIL PROTECTED] |Owner: jacob Status: closed |Component: Documentation Version: 0.96| Resolution: duplicate Keywords: |Stage: Unreviewed Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 --+- Changes (by Gary Wilson <[EMAIL PROTECTED]>): * status: new => closed * needs_better_patch: => 0 * resolution: => duplicate * needs_tests: => 0 * needs_docs: => 0 Comment: dup of #4043. -- Ticket URL: <http://code.djangoproject.com/ticket/4104#comment:1> Django Code <http://code.djangoproject.com/> 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 Code] #4118: dead link
#4118: dead link -+-- Reporter: anonymous |Owner: jacob Status: closed |Component: Documentation Version: 0.96 | Resolution: duplicate Keywords: |Stage: Unreviewed Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 -+-- Changes (by Gary Wilson <[EMAIL PROTECTED]>): * status: new => closed * needs_better_patch: => 0 * resolution: => duplicate * needs_tests: => 0 * needs_docs: => 0 Comment: the link this page was on wasn't mentioned, but is probably a dup of #4033. -- Ticket URL: <http://code.djangoproject.com/ticket/4118#comment:1> Django Code <http://code.djangoproject.com/> 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 Code] #4133: documentation links using underscore instead of dash
#4133: documentation links using underscore instead of dash +--- Reporter: Gary Wilson <[EMAIL PROTECTED]> | Owner: jacob Status: new | Component: Django Web site Version: SVN |Keywords: Stage: Unreviewed | Has_patch: 0 +--- Combining other tickets here for a more general problem, and a couple problems that weren't reported yet. There are various links that are using an underscore instead of a dash: || Originating page || Broken link || || http://www.djangoproject.com/documentation/0.95/serialization/ || http://www.djangoproject.com/documentation/0.95/db_api/ || || http://www.djangoproject.com/documentation/0.96/model-api/ || http://www.djangoproject.com/documentation/0.95/db_api/ || || http://www.djangoproject.com/documentation/0.96/generic_views/ || http://www.djangoproject.com/documentation/0.95/db_api/ || || http://www.djangoproject.com/documentation/0.96/faq/ || http://www.djangoproject.com/documentation/0.96/model_api/ || || http://www.djangoproject.com/documentation/0.96/tutorial01/ || http://www.djangoproject.com/documentation/0.96/django_admin/ || -- Ticket URL: <http://code.djangoproject.com/ticket/4133> Django Code <http://code.djangoproject.com/> 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 Code] #4033: broken link to 0.96 db-api
#4033: broken link to 0.96 db-api +--- Reporter: [EMAIL PROTECTED] |Owner: jacob Status: closed|Component: Django Web site Version: 0.96 | Resolution: duplicate Keywords: url db-api db_api |Stage: Ready for checkin Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Changes (by Gary Wilson <[EMAIL PROTECTED]>): * status: new => closed * resolution: => duplicate Comment: dup of #4133 -- Ticket URL: <http://code.djangoproject.com/ticket/4033#comment:2> Django Code <http://code.djangoproject.com/> 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 Code] #4133: documentation links using underscore instead of dash
#4133: documentation links using underscore instead of dash ---+ Reporter: Gary Wilson <[EMAIL PROTECTED]> |Owner: jacob Status: new |Component: Django Web site Version: SVN | Resolution: Keywords: |Stage: Ready for checkin Has_patch: 0| Needs_docs: 0 Needs_tests: 0| Needs_better_patch: 0 ---+ Changes (by Gary Wilson <[EMAIL PROTECTED]>): * needs_better_patch: => 0 * stage: Unreviewed => Ready for checkin * needs_tests: => 0 * needs_docs: => 0 Comment: Another: || Originating page || Broken link || || http://www.djangoproject.com/documentation/0.96/tutorial01/ || http://www.djangoproject.com/documentation/0.96/db_api/ || -- Ticket URL: <http://code.djangoproject.com/ticket/4133#comment:1> Django Code <http://code.djangoproject.com/> 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 Code] #4112: Broken Link on 0.96 Database API Reference Page
#4112: Broken Link on 0.96 Database API Reference Page --+- Reporter: meisel |Owner: jacob Status: closed |Component: Admin interface Version: 0.96| Resolution: duplicate Keywords: |Stage: Ready for checkin Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 --+- Changes (by Gary Wilson <[EMAIL PROTECTED]>): * status: new => closed * resolution: => duplicate * component: Django Web site => Admin interface Comment: dup of #4133 -- Ticket URL: <http://code.djangoproject.com/ticket/4112#comment:2> Django Code <http://code.djangoproject.com/> 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 Code] #4127: broken link to QuerySet DB API in 0.96 documentation
#4127: broken link to QuerySet DB API in 0.96 documentation +--- Reporter: [EMAIL PROTECTED] |Owner: jacob Status: new |Component: Django Web site Version: 0.96 | Resolution: Keywords: wiki broken link |Stage: Ready for checkin Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Comment (by Gary Wilson <[EMAIL PROTECTED]>): dup of #4133 -- Ticket URL: <http://code.djangoproject.com/ticket/4127#comment:2> Django Code <http://code.djangoproject.com/> 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 Code] #4133: documentation links using underscore instead of dash
#4133: documentation links using underscore instead of dash ---+ Reporter: Gary Wilson <[EMAIL PROTECTED]> |Owner: jacob Status: new |Component: Django Web site Version: SVN | Resolution: Keywords: |Stage: Ready for checkin Has_patch: 0| Needs_docs: 0 Needs_tests: 0| Needs_better_patch: 0 ---+ Comment (by Gary Wilson <[EMAIL PROTECTED]>): Another: || Originating page || Broken link || || http://www.djangoproject.com/documentation/0.96/db-api/ || http://www.djangoproject.com/documentation/0.96/model_api/ || -- Ticket URL: <http://code.djangoproject.com/ticket/4133#comment:2> Django Code <http://code.djangoproject.com/> 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 Code] #4133: documentation links using underscore instead of dash
#4133: documentation links using underscore instead of dash ---+ Reporter: Gary Wilson <[EMAIL PROTECTED]> |Owner: jacob Status: new |Component: Django Web site Version: SVN | Resolution: Keywords: |Stage: Accepted Has_patch: 0| Needs_docs: 0 Needs_tests: 0| Needs_better_patch: 0 ---+ Changes (by Gary Wilson <[EMAIL PROTECTED]>): * stage: Ready for checkin => Accepted Comment: -- Ticket URL: <http://code.djangoproject.com/ticket/4133#comment:3> Django Code <http://code.djangoproject.com/> 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 Code] #4133: documentation links using underscore instead of dash
#4133: documentation links using underscore instead of dash ---+ Reporter: Gary Wilson <[EMAIL PROTECTED]> |Owner: jacob Status: new |Component: Django Web site Version: SVN | Resolution: Keywords: |Stage: Ready for checkin Has_patch: 1| Needs_docs: 0 Needs_tests: 0| Needs_better_patch: 0 ---+ Changes (by Gary Wilson <[EMAIL PROTECTED]>): * has_patch: 0 => 1 * stage: Accepted => Ready for checkin Comment: A patch for future documentation freezing, and we need redirects for the 0.95 and 0.96 docs. -- Ticket URL: <http://code.djangoproject.com/ticket/4133#comment:4> Django Code <http://code.djangoproject.com/> 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 Code] #4127: broken link to QuerySet DB API in 0.96 documentation
#4127: broken link to QuerySet DB API in 0.96 documentation +--- Reporter: [EMAIL PROTECTED] |Owner: jacob Status: closed|Component: Django Web site Version: 0.96 | Resolution: duplicate Keywords: wiki broken link |Stage: Ready for checkin Has_patch: 0 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 +--- Changes (by Gary Wilson <[EMAIL PROTECTED]>): * status: new => closed * resolution: => duplicate Comment: forgot to close the ticket. -- Ticket URL: <http://code.djangoproject.com/ticket/4127#comment:3> Django Code <http://code.djangoproject.com/> 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 Code] #4130: When mistyping a field name in an ORM call, the error message could be a lot more helpful.
#4130: When mistyping a field name in an ORM call, the error message could be a lot more helpful. -+-- Reporter: [EMAIL PROTECTED] |Owner: adrian Status: new|Component: Core framework Version: SVN| Resolution: Keywords: |Stage: Unreviewed Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 -+-- Changes (by anonymous): * needs_tests: 1 => 0 Comment: -- Ticket URL: <http://code.djangoproject.com/ticket/4130#comment:4> Django Code <http://code.djangoproject.com/> 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 Code] #2070: [patch] Large streaming uploads
#2070: [patch] Large streaming uploads +--- Reporter: [EMAIL PROTECTED] |Owner: jacob Status: assigned |Component: Core framework Version:| Resolution: Keywords: streaming, upload, large |Stage: Accepted Has_patch: 1 | Needs_docs: 1 Needs_tests: 0 | Needs_better_patch: 1 +--- Changes (by Brian Koebbe <[EMAIL PROTECTED]>): * cc: [EMAIL PROTECTED] (added) Comment: -- Ticket URL: <http://code.djangoproject.com/ticket/2070#comment:109> Django Code <http://code.djangoproject.com/> 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 Code] #4134: [patch] raw_id_admin support direct visible repr of chosen object
#4134: [patch] raw_id_admin support direct visible repr of chosen object ---+ Reporter: anonymous | Owner: jacob Status: new | Component: Uncategorized Version: SVN |Keywords: Stage: Unreviewed | Has_patch: 0 ---+ the current raw_id_admin ability of 0.96 does not show you the value you selected. this is only visible after saving. also it does not show a change to the field only the new id number in the box, but the old repr of the object stays until save. i know this is entirely refactored in svn for the upcoming release with newformsadmin. but i thought to still share this patch with u, for other people wanting to use raw_id_admin in the 0.96 release. this patch changes 2 files in django/contrib/admin, to pass the extra information needed to add or change the title of the selected object in the field. -- Ticket URL: <http://code.djangoproject.com/ticket/4134> Django Code <http://code.djangoproject.com/> 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 Code] #4134: [patch] raw_id_admin support direct visible repr of chosen object
#4134: [patch] raw_id_admin support direct visible repr of chosen object --+- Reporter: anonymous |Owner: adrian Status: new |Component: Admin interface Version: 0.96| Resolution: Keywords: admin raw_id_admin |Stage: Unreviewed Has_patch: 1 | Needs_docs: 0 Needs_tests: 0 | Needs_better_patch: 0 --+- Changes (by anonymous): * cc: [EMAIL PROTECTED] (added) * needs_better_patch: => 0 * component: Uncategorized => Admin interface * needs_tests: => 0 * owner: jacob => adrian * version: SVN => 0.96 * keywords: => admin raw_id_admin * needs_docs: => 0 * has_patch: 0 => 1 Comment: -- Ticket URL: <http://code.djangoproject.com/ticket/4134#comment:1> Django Code <http://code.djangoproject.com/> 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 Code] #4135: Dead links in Tutorial for 0.96
#4135: Dead links in Tutorial for 0.96 ---+ Reporter: anonymous | Owner: jacob Status: new | Component: Documentation Version: SVN |Keywords: Stage: Unreviewed | Has_patch: 0 ---+ Instead of http://www.djangoproject.com/documentation/0.96/tutorial3/ it should be http://www.djangoproject.com/documentation/0.96/tutorial03/ -- Ticket URL: <http://code.djangoproject.com/ticket/4135> Django Code <http://code.djangoproject.com/> 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 Code] #4136: NULL fields and Unique keys
#4136: NULL fields and Unique keys -+-- Reporter: David Cramer <[EMAIL PROTECTED]> | Owner: adrian Status: new | Component: Database wrapper Version: 0.96 |Keywords: Stage: Unreviewed| Has_patch: 0 -+-- When Django sends an update to MySQL for a NULL field it does not insert it as NULL (when you are in the admin). e.g. You have an openid_key field, which is the url of the users openid url. This url has to be unique and should be marked as such for db integrity. You go into the admin and edit a user, they have no openid_key. You save the user. All is fine. You go into the admin and edit a different user, they have no openid_key. You save the user. SQL throws a fit about the key needs to be unique. Django tried to insert "" instead of NULL for this field. -- Ticket URL: <http://code.djangoproject.com/ticket/4136> Django Code <http://code.djangoproject.com/> 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 -~--~~~~--~~--~--~---
