Re: Upgrading a django 1.2 Alpha site to 1.10 final site, passwords don't work

Thank you Tim, the pointer was just I needed. If anyone runs into this issue you will also need to update the auth_user table to allow NULLs in the last_login date. See this defect for details https://code.djangoproject.com/ticket/24679 -- You received this message because you are subscribed

Re: Upgrading a django 1.2 Alpha site to 1.10 final site, passwords don't work

Django 1.10 can still support SHA1, but it's not enabled by default. Please read https://docs.djangoproject.com/en/dev/releases/1.10/#removed-weak-password-hashers-from-the-default-password-hashers-setting and https://docs.djangoproject.com/en/stable/topics/auth/passwords/. On Friday, Septembe

Upgrading a django 1.2 Alpha site to 1.10 final site, passwords don't work

Hello All, I'm new to django and python. A project that was last maintained in 2009 was bestowed upon me because the underlying OS is approaching end-of-life. I've read the first few chapters the Django book and the first 10 chapters of Django Unleashed. I've got the project and supporting li

Sessionid in plain text Django 1.2 error emails

Hi, Is there any simple way of taking the sessionid out of the django error emails that get sent in plain text when there's a 500? We're using django 1.2. Thanks, Bjorn -- You received this message because you are subscribed to the Google Groups "Django users"

How does the multiple database concept work after django 1.2

Hi all , My app has started breaking after moving to django 1.3 . I don't really understand why? I am working using site framework and given model definition through app_label. The only majot change as I can see is that I use UUID Fields rather than AutoField. Now somehow i see that my app is try

Re: Need help getting this snippet to work in Django 1.2...

On Mon, Jun 13, 2011 at 9:44 AM, Micky Hulse wrote: > Ooh, great tip! That looks very useful and possibly a little more > simple/straight-forward than using a form field. Too easy! https://gist.github.com/1023327 Thanks for the help Martin and Alex, I really appreciate it! :) Have an awesome d

Re: Need help getting this snippet to work in Django 1.2...

Hi Alex! Thanks for the reply, I really appreciate it. :) On Sun, Jun 12, 2011 at 9:01 PM, Alex Kamedov wrote: > It'll be better to use validators with IntegerField > In this case you can specify allowed year range. Ooh, great tip! That looks very useful and possibly a little more simple/straigh

Re: Need help getting this snippet to work in Django 1.2...

It'll be better to use validators with IntegerField https://docs.djangoproject.com/en/1.3/ref/models/fields/#validators https://docs.djangoproject.com/en/1.3/ref/validators/ In this case you can specify allowed year range. On Sat, Jun 11, 2011 at 9:25 AM, mhulse wrote: > Hi Martin! Thanks so m

Re: Need help getting this snippet to work in Django 1.2...

Hi Martin! Thanks so much for the help, I really appreciate it. :) > The snippet is a form field, not a model field. Well, that would explain things! Lol. When I read this in the instructions: "Usage eg: yob = BirthYearField(label="What year were you born?")" I thought that was a model field.

Re: Need help getting this snippet to work in Django 1.2...

I think this is not how it works. The snippet is a form field, not a model field. Basically I think you should use an IntegerField (you just want to store a year, right?). Then somehow you need to override the widget or so and make sure that in the admin that form will be used for that IntegerField

Need help getting this snippet to work in Django 1.2...

I feel like this should be simple... I would like to replace this model field: date = models.DateField(_(u'Year'), unique=True) ...with this snippet: http://djangosnippets.org/snippets/508/ I have spent the last couple hours banging my head on my keyboard... During the course of my tests, at

Re: [Django 1.2] Admin ForeignKey edit link?

On Wed, Jun 8, 2011 at 12:51 PM, Micky Hulse wrote: > Looks like ticket #13165 is the way to go, but I thought I would ask > the group before I consider applying the patch. Ooops, here's the link to the ticket: -- You received this message because

[Django 1.2] Admin ForeignKey edit link?

Hi, Looks like ticket #13165 is the way to go, but I thought I would ask the group before I consider applying the patch. I would love to have an "edit" pencil link for my model's FKs. Other than applying the patch, are there any good work-arounds out there? I was considering extending/overridin

Re: django 1.1 performance versus django 1.2 performance

Don't know whether this is relevant or not but the Python Software Foundation has just decided to establish a facility that allows speed comparison of different Python releases. The thinking behind this is (at least) twofold: 1) People will more easily be able to determine which is the best Python

Re: Django 1.2 Dropped Sessions when single view contains registration and login authentication

- Original Message - > From: "benp" > To: "Django users" > Sent: Monday, April 25, 2011 8:54:15 AM > Subject: Django 1.2 Dropped Sessions when single view contains registration > and login authentication > I've seen other Django developers h

Re: django 1.1 performance versus django 1.2 performance

But what changed in 1.2 vs. 1.1 that caused cloning to become slower? Is it fixes for correctness that were missing? And if 1.3 is slower than 1.2, why the slow down there? If the slowness is for a good reason (correctness is about the only one I can think of that is really valid), then fine. But

Re: django 1.1 performance versus django 1.2 performance

> Is there a way to identify which queries use cloning? Every filter, exclude, order_by, select_related and some other calls clones it. Slicing too. > Is there a way rewrite those queries to avoid cloning overhead? You can rewrite qs.filter(a=1).exclude(b=2) as qs.filter(Q(a=1) & !Q(b=2)) or qs

Re: django 1.1 performance versus django 1.2 performance

Is there a way to identify which queries use cloning? Is there a way rewrite those queries to avoid cloning overhead? (If many of the queries use cloning then migrating one of my django apps to 1.2.x may not be right for me.) On Apr 25, 9:39 am, djeff wrote: > Russ, > > Thanks for the response

Re: django 1.1 performance versus django 1.2 performance

Russ, Thanks for the response. You have confirmed what I'm seeing in the profile dump. The cloning of a queryset is expensive and it is more expensive in 1.2 than with 1.1. I really appreciate the feedback. Jeff Fischer -- You received this message because you are subscribed to the Googl

Django 1.2 Dropped Sessions when single view contains registration and login authentication

Hi, This issue has been raised on Stack Overflow many times without any resolution. The gist is that all of the views in my site are protected by the @login_required decorator except for a splash page and a registration page (which is only accessible by going through the splash page and passing

Re: django 1.1 performance versus django 1.2 performance

I am experiencing considerable performance problems with ORM requests, too. In django 1.2.3. And I found two slow procedures: first is queryset cloning (sql.Query objects deepcopying is actually slow) and second - sql generation (especially, generating list of fields). Both could be a result of ad

Re: django 1.1 performance versus django 1.2 performance

On Apr 23, 11:54 am, Torsten Bronger wrote: > Does anybody have estimates or figures concerning the impact of > middleware?  I love the middleware framework and I make extensive > use of it but sometimes I'm afraid it slows down every request > significantly, especially if you have a project wit

Re: django 1.1 performance versus django 1.2 performance

Hallöchen! Russell Keith-Magee writes: > [...] > > No - there isn't a plan to address this, because it isn't clear > what "this" is. > > While it is known that there has been a slowdown between versions, > that slowdown has been accompanied by a massive increase in > functionality -- for example,

Re: django 1.1 performance versus django 1.2 performance

> On Fri, Apr 22, 2011 at 9:22 PM, Shawn Milochik wrote: >> >> This was mentioned in Eric Florenzano's talk at DjangoCon 2010. Each >> version has gotten slower. >> >> I haven't heard anything about the cause or plans to fix this, though. >> If you've got a good test suite you can always use tools

Re: django 1.1 performance versus django 1.2 performance

Is there a plan in place to address this? On Fri, Apr 22, 2011 at 9:22 PM, Shawn Milochik wrote: > This was mentioned in Eric Florenzano's talk at DjangoCon 2010. Each > version has gotten slower. > > I haven't heard anything about the cause or plans to fix this, though. > If you've got a good t

Re: django 1.1 performance versus django 1.2 performance

This was mentioned in Eric Florenzano's talk at DjangoCon 2010. Each version has gotten slower. I haven't heard anything about the cause or plans to fix this, though. If you've got a good test suite you can always use tools like Python's profile module to track down slowdowns in your Django code a

django 1.1 performance versus django 1.2 performance

Hey, We are in the process of migrating from Django 1.1 to Django 1.2.5 and I'm investigating a performance slowdown in our unit tests. We see about a 30% slowdown when running our unit test suite with 1.2.5 versus 1.1. I was just wondering if anyone else had noticed something similar to this.

Re: Google app engine django 1.2 localization

Mar 12, 2011 at 2:55 PM, Nick Rosencrantz wrote: > > > Dear Group, Here's a question I try to solve, Maybe you know what's > > the change between GAE+django 0.96 and GAE+django 1.2 with respect to > > localization? Putting .po and .mo files in APP_NAME/conf ... used to >

Re: Google app engine django 1.2 localization

power of opensource_* On Sat, Mar 12, 2011 at 2:55 PM, Nick Rosencrantz wrote: > Dear Group, Here's a question I try to solve, Maybe you know what's > the change between GAE+django 0.96 and GAE+django 1.2 with respect to > localization? Putting .po a

Google app engine django 1.2 localization

Dear Group, Here's a question I try to solve, Maybe you know what's the change between GAE+django 0.96 and GAE+django 1.2 with respect to localization? Putting .po and .mo files in APP_NAME/conf ... used to work and upgraded to django 1.2 it won't work anymore. Having upgraded from

Re: django 1.2 + Google app engine + templatetags

Solved. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this gr

django 1.2 + Google app engine + templatetags

Hi I run django 1.2 with GAE and I'm trying to get templatetags working and I keep getting the following error: 'rss' is not a valid tag library: Could you tell what's up with this? The django snippet I tried yo add is http://djangosnippets.org/snippets/311/ and I added the f

Re: Google App Engine supports Django 1.2!

Hi, you can start here: http://code.google.com/appengine/articles/django-nonrel.html http://code.google.com/appengine/articles/appengine_helper_for_django.html http://www.allbuttonspressed.com/blog/django hth, Cheers Strap On Feb 14, 7:15 pm, Gath wrote: > Please give me a pointer/link to a tuto

Re: Google App Engine supports Django 1.2!

Please give me a pointer/link to a tutorial on how i can use GAE with django. Thanks, Gath. On Feb 14, 7:12 am, Sarang wrote: > Thanks for the clarification. Yes, I am using django-nonrel which installed > 1.3.0 alpha 1 for me. > > Regards, > Sarang -- You received this message because you are

Re: Google App Engine supports Django 1.2!

Thanks for the clarification. Yes, I am using django-nonrel which installed 1.3.0 alpha 1 for me. Regards, Sarang -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscrib

Re: Google App Engine supports Django 1.2!

No, it does not support the datastore. Now you do not have to distribute your own zipfile of Django 1.2.5. The word 'supports' does not refer to Django integration with the GAE api's, but rather that this new version is available on the server. Django 1.2.5 was added so that you can load it v

Re: Google App Engine supports Django 1.2!

Thats nice! Does this version of Django support the datastore too? The current Django I am using w/ GAE is 1.3.0 Alpha 1 and I am wondering if switching to the latest GAE SDK would be an issue. Regards, Sarang -- You received this message because you are subscribed to the Google Groups "Djang

Google App Engine supports Django 1.2!

http://code.google.com/p/googleappengine/wiki/SdkReleaseNotes Almost in time for Django 1.3's release. ;o) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from t

Django 1.2 and keyless many to many on legacy databases

1.1): http://djangosnippets.org/snippets/962/ but got no luck in patching it so that it could work with django 1.2 (and I need the later for permission management and multi database support). Also I can't see how I could do it with a through table since django doesn't support composite keys. Regar

Re: tracking down a login issue (django 1.2)

On Tue, Sep 14, 2010 at 3:09 AM, Cindy wrote: > OK, I have figured this out myself -- is there somewhere I should put > in a bug report? Almost certainly yes -- but based on the details you provide, it isn't clear that the right place is Django's Trac instance. Django doesn't provide an LDAP auth

Re: tracking down a login issue (django 1.2)

OK, I have figured this out myself -- is there somewhere I should put in a bug report? It seems that if you are using the ldap authentication backend, setting AUTH_LDAP_FIND_GROUP_PERMS can result in generating sql that tries to look up group membership in an empty set. When this value is true, d

Re: url_name from resolve in Django 1.2

It seems it's impossible for now. So let me change the question. How to use the already compiled (by Django) url_patterns so i dont have to import and compile the ROOT_URLCONF on every hit of my function? Regards On 9 Wrz, 22:52, SlafS wrote: > Hi there! > > Is there any way to obtain a name

Django 1.2 and unittest2 - does this hack work?

I'm using Django 1.2.3 with Python 2.6. I would like to use the new fancy unittest asserts available in Python 2.7. These have been backported to Python 2.6 as the unittest2 module (http://www.voidspace.org.uk/python/articles/unittest2.shtml). But at the same time, I would like to use test fixtures

tracking down a login issue (django 1.2)

I'm not completely certain what is going on here, but somewhere in the authentication stuff, a bad MySQL query is being generated: ListType TupleType args [] charset 'utf8' db exc exc_info query '\n SELECT ct.`app_label`, p.`codename`\n FROM `auth_permission` p, `auth_group_permissions` gp, `

tracking down a login issue (django 1.2)

I'm not completely certain what is going on here, but somewhere in the authentication stuff, a bad MySQL query is being generated: ListType TupleType args [] charset 'utf8' db exc exc_info query '\n SELECT ct.`app_label`, p.`codename`\n FROM `auth_permission` p, `auth_group_permissions` gp, `

url_name from resolve in Django 1.2

Hi there! Is there any way to obtain a name of an url that Django URL dispatcher matched by resolving (or anything else) e.g. '/path/to/my/page/'? For now resolve returns a tuple :/. I assume that it will be available in 1.3 according to http://docs.djangoproject.com/en/dev/topics/http/urls/#dj

Re: Django 1.2 modelformset_factory fails with meta: widgets

rewrite the __init__., redefining the form element in this place. The error must to dissapear. class FormMyForm(ModelForm): def __init__(self, *args, **kwargs): super(FormMyForm, self).__init__(*args, **kwargs) self.fields[''] = forms.CharField(widget=forms.TextInput(attrs=

Re: Django 1.2 modelformset_factory fails with meta: widgets

Thanks! I'll give that a try. On Aug 13, 8:55 am, Matthew R wrote: > I got hit by this same bug and here's the workaround I used, for > future reference. Basically you need to specify a formfield_callback > kwarg to modelformset_factory that just passes along any kwargs it > receives (namely, in

Re: prepopulated_fields do not work at all Django 1.2

appens when something goes > > wrong. > > > On 29 août, 23:58, Goran wrote: > > > > I have strange problem, on my development server everything is fine > > > but I'm use Django 1.1 but on the production server (Django 1.2) > > > prepop

Re: prepopulated_fields do not work at all Django 1.2

Django and any third-part app - at > least you'd have a chance to find out what happens when something goes > wrong. > > On 29 août, 23:58, Goran wrote: > > > I have strange problem, on my development server everything is fine > > but I'm use Dja

Re: prepopulated_fields do not work at all Django 1.2

t server everything is fine > but I'm use Django 1.1 but on the production server (Django 1.2) > prepopulated_fields don't work. Does anyone have the same problem? Any > suggestion? > > class UniverzitetAdmin(admin.ModelAdmin): >     prepopulated_fields = {"

prepopulated_fields do not work at all Django 1.2

I have strange problem, on my development server everything is fine but I'm use Django 1.1 but on the production server (Django 1.2) prepopulated_fields don't work. Does anyone have the same problem? Any suggestion? class UniverzitetAdmin(admin.ModelAdmin): prepopulated_fiel

Re: how to turn off CSRF in django 1.2?

#x27; > ?http://docs.djangoproject.com/en/1.0/ref/contrib/csrf/#how-to-use-it > > On 26 August 2010 16:33, Alan wrote: > > > > > > > Ops, sorry, but I don't have this line > > django.middleware.csrf.CsrfViewMiddleware, as I said, it's a project > >

Re: how to turn off CSRF in django 1.2?

On 08/26/2010 05:33 PM, Alan wrote: Ops, sorry, but I don't have this line django.middleware.csrf.CsrfViewMiddleware, as I said, it's a project done in 1.0.2. and I want it to run on my django 1.2 but without any reference to Csrf, since the server where the portal is runs 1.0.2 yet.

Re: Django 1.2 unittests: Second time through, things get weird

On Fri, Aug 27, 2010 at 1:43 AM, Elf_Sternberg wrote: > Is anyone seeing this?  I have this function at the top of my > unittest: > > def create_user(name): >    username = name.replace(' ', '').lower() >    return User.objects.create_user(username, username + '@a.com', > 'password') > > And then

Re: Django 1.2 unittests: Second time through, things get weird

On Thu, Aug 26, 2010 at 1:43 PM, Elf_Sternberg wrote: > Is anyone seeing this? I have this function at the top of my > unittest: > > def create_user(name): >username = name.replace(' ', '').lower() >return User.objects.create_user(username, username + '@a.com', > 'password') > > And then

Django 1.2 unittests: Second time through, things get weird

Is anyone seeing this? I have this function at the top of my unittest: def create_user(name): username = name.replace(' ', '').lower() return User.objects.create_user(username, username + '@a.com', 'password') And then (this is ultimately the code I derived to examine this behavior): cl

Re: how to turn off CSRF in django 1.2?

7;s a project > done in 1.0.2. and I want it to run on my django 1.2 but without any > reference to Csrf, since the server where the portal is runs 1.0.2 > yet. > > On 26 Aug, 15:54, João Rodrigues wrote: > > go to your settings.py and comment out > > django.middl

Re: how to turn off CSRF in django 1.2?

Ops, sorry, but I don't have this line django.middleware.csrf.CsrfViewMiddleware, as I said, it's a project done in 1.0.2. and I want it to run on my django 1.2 but without any reference to Csrf, since the server where the portal is runs 1.0.2 yet. On 26 Aug, 15:54, João Rodrigues wrot

Re: how to turn off CSRF in django 1.2?

t; I developed in a system that uses django 1.2, but the server is still > > django 1.0.2. > > > Upgrading for a moment is not possible. Unless someone knows a nice > > simple alternative, in order to keep my web portal compatible between > > 1.0.2 and 1.2, I would like to

Re: how to turn off CSRF in django 1.2?

go to your settings.py and comment out django.middleware.csrf.CsrfViewMiddleware in your MIDDLEWARE_CLASSES On 26 August 2010 10:33, Alan wrote: > Hi there, > > I developed in a system that uses django 1.2, but the server is still > django 1.0.2. > > Upgrading for a mome

Re: how to turn off CSRF in django 1.2?

n.org/writing/django-apps-with-buildout/) As you wish these two methods worked pretty well, on my side i like buildout cause it's easier to maintain. On Thu, Aug 26, 2010 at 1:07 PM, Sven Bröckling wrote: > Hi Alan, > >> I developed in a system that uses django 1.2, but the ser

Re: how to turn off CSRF in django 1.2?

Hi Alan, > I developed in a system that uses django 1.2, but the server is still > django 1.0.2. > Upgrading for a moment is not possible. Unless someone knows a nice > simple alternative, in order to keep my web portal compatible between > 1.0.2 and 1.2, I would like to switch

how to turn off CSRF in django 1.2?

Hi there, I developed in a system that uses django 1.2, but the server is still django 1.0.2. Upgrading for a moment is not possible. Unless someone knows a nice simple alternative, in order to keep my web portal compatible between 1.0.2 and 1.2, I would like to switch off CSRF on my developing

Re: Django 1.2 modelformset_factory fails with meta: widgets

I got hit by this same bug and here's the workaround I used, for future reference. Basically you need to specify a formfield_callback kwarg to modelformset_factory that just passes along any kwargs it receives (namely, in this case, the 'widget' argument) to Field.formfield(): def create_formfield

Re: Issue with loading fixtures in tests with multi database in Django 1.2

Hi Russ, I opened #14068. I can not think of an easy fix as those I would choose will have side effects on other multi database settings. If the core team can come with a design decision on the fix, I'll be happy to implement it. Regards, Xavier. Le 5 août 2010 à 13:31, Russell Keith-Magee a é

Re: Announces django-guardian: per object permissions for Django 1.2

On Thu, Aug 5, 2010 at 3:32 AM, lukaszb wrote: > Thanks for the comment! I really do think that this "backends ready && > included" parts of Django are extremely useful (and fun to extend if > needed). > > About the admin, I haven't really get into admin integration yet as I > cannot answer this:

Re: Issue with loading fixtures in tests with multi database in Django 1.2

On Thu, Aug 5, 2010 at 3:44 PM, Xavier Ordoquy wrote: > Hi Russ, > > Indeed, my investigations have lead me to #14025 which fixed the major issue. > > If I remember correctly the corrupted file part was due to the fact that I > was still using an "old style" fixture filename - ie .json instead of

Re: Announces django-guardian: per object permissions for Django 1.2

> > Hi all, > > > > I'd like to announce django-guardian - very basic yet usable per > > > object permissions > > > implementation for Django 1.2, using new authorization backend > > > facilities. > > > > It was created during 2 days sprint, co

Re: Issue with loading fixtures in tests with multi database in Django 1.2

Hi Russ, Indeed, my investigations have lead me to #14025 which fixed the major issue. If I remember correctly the corrupted file part was due to the fact that I was still using an "old style" fixture filename - ie .json instead of ..json with data on both databases. If you find it useful, I ca

Re: Issue with loading fixtures in tests with multi database in Django 1.2

On Thu, Jul 29, 2010 at 6:02 PM, Xavier Ordoquy wrote: > Hi there. > > I'm currently working on a project where I use a legacy database with a > django one. > I've setup the multi database support and it seems to work pretty well. > However, I'm getting an issue with testing. > > I need a fixture

Re: Announces django-guardian: per object permissions for Django 1.2

01:34, Russell Keith-Magee wrote: > On Wed, Aug 4, 2010 at 7:20 AM, lukaszb wrote: > > Hi all, > > > I'd like to announce django-guardian - very basic yet usable per > > object permissions > > implementation for Django 1.2, using new authorization backend >

Re: Announces django-guardian: per object permissions for Django 1.2

(i.e. Team model with fk to Group among other fields). Let me know if you have different experience. On 4 Sie, 15:26, derek wrote: > On Aug 4, 1:20 am, lukaszb wrote: > > > > > > > Hi all, > > > I'd like to announce django-guardian - very basic yet usable per >

Re: Announces django-guardian: per object permissions for Django 1.2

On Aug 4, 1:20 am, lukaszb wrote: > Hi all, > > I'd like to announce django-guardian - very basic yet usable per > object permissions > implementation for Django 1.2, using new authorization backend > facilities. > > It was created during 2 days sprint, code have bee

Re: Announces django-guardian: per object permissions for Django 1.2

On Wed, Aug 4, 2010 at 7:20 AM, lukaszb wrote: > Hi all, > > I'd like to announce django-guardian - very basic yet usable per > object permissions > implementation for Django 1.2, using new authorization backend > facilities. > > It was created during 2 days sprint

Announces django-guardian: per object permissions for Django 1.2

Hi all, I'd like to announce django-guardian - very basic yet usable per object permissions implementation for Django 1.2, using new authorization backend facilities. It was created during 2 days sprint, code have been released and may be found at http://github.com/lukaszb/django-gua

Re: Django 1.2 modelformset_factory fails with meta: widgets

Can anyone confirm that passing in a form with Meta.widgets set to modelformset_factory() does in fact work? I've tried stripping my code down to the basics and still get the same exception. Debugging Django code doesn't help me because it fails during a lamda function that I don't quite understan

Issue with loading fixtures in tests with multi database in Django 1.2

Hi there. I'm currently working on a project where I use a legacy database with a django one. I've setup the multi database support and it seems to work pretty well. However, I'm getting an issue with testing. I need a fixture to load data to both the legacy and Django's databases. In order to m

Re: Django 1.2 modelformset_factory fails with meta: widgets

Traceback: File "C:\Python25\lib\site-packages\django\core\handlers\base.py" in get_response 100. response = callback(request, *callback_args, **callback_kwargs) File "C:\Documents and Settings\goodrich\PycharmProjects\CCC\Aggregator \newsmail\views.py" in manage_articles 17

Re: Django 1.2 modelformset_factory fails with meta: widgets

On Jul 28, 7:08 pm, Jason wrote: > For example: > > class ArticleForm(ModelForm): >     class Meta: >         model = Article >         widgets = { >              'pub_date': SplitSelectDateTimeWidget(), >              'expire_date': CalendarWidget(attrs={'class':'date- > pick'}) >         } > > A

Django 1.2 modelformset_factory fails with meta: widgets

For example: class ArticleForm(ModelForm): class Meta: model = Article widgets = { 'pub_date': SplitSelectDateTimeWidget(), 'expire_date': CalendarWidget(attrs={'class':'date- pick'}) } And in a view function: ... ArticleFormSet = modelfo

Re: Using DATE_FORMAT in django 1.2

On Sun, Jun 6, 2010 at 9:57 AM, Tomas Zulberti wrote: > On Jun 5, 8:11 pm, Karen Tracey wrote: > > On Sat, Jun 5, 2010 at 6:17 PM, Tomas Zulberti > wrote: > > > So my question is: is this a bug, or I am doing something wrong (I am > > > sure I might be doing something grong but I don't know whe

Re: Using DATE_FORMAT in django 1.2

On Jun 5, 8:11 pm, Karen Tracey wrote: > On Sat, Jun 5, 2010 at 6:17 PM, Tomas Zulberti wrote: > > So my question is: is this a bug, or I am doing something wrong (I am > > sure I might be doing something grong but I don't know where). > > I ran into the same behavior this afternoon. I think it

Re: Using DATE_FORMAT in django 1.2

On Sat, Jun 5, 2010 at 6:17 PM, Tomas Zulberti wrote: > So my question is: is this a bug, or I am doing something wrong (I am > sure I might be doing something grong but I don't know where). > I ran into the same behavior this afternoon. I think it is a bug: http://code.djangoproject.com/ticket/

Using DATE_FORMAT in django 1.2

Hi. I have the following values in the settings.py: USE_L10N = True DATETIME_FORMAT = '%d/%m/%Y' When the date is printed it prints: "Nov. 24, 1983". The date is: datetime.date(1983, 11, 24). As far as I was able to follow the code, in the django/utils/ formats.py, the it uses the the get_format f

Re: Django 1.2.1 doesn't work with South but 1.2 works? How to find the previous version Django 1.2?

South is working fine for me with Django 1.2 as well. What errors are you getting? There's a south discussion group that may be more productive for this conversation though. On Jun 1, 9:29 pm, flyinglegs wrote: > I am having some trouble with South database migration using Fabric. I

Re: Django 1.2.1 doesn't work with South but 1.2 works? How to find the previous version Django 1.2?

Djago 1.2.1 works fine for me with South. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.co

Re: Django 1.2.1 doesn't work with South but 1.2 works? How to find the previous version Django 1.2?

y difference is that the machine that's working is using Django > 1.2, and the others are using Django 1.2.1. > > Somehow I couldn't find the Django 1.2 tarball on the website, any > idea why it was pulled? Does anybody else have trouble using Django > 1.2.1 with South 0.7.

Django 1.2.1 doesn't work with South but 1.2 works? How to find the previous version Django 1.2?

I am having some trouble with South database migration using Fabric. I tried several machines, one works and the other 3 doesn't work. The only difference is that the machine that's working is using Django 1.2, and the others are using Django 1.2.1. Somehow I couldn't find the Dja

Re: Problem installing django 1.2 on Mac OS 10.6.3

My bad. Turns out it was a problem with multiple versions of python installed. Fixed it. On May 23, 7:43 pm, Tor Nordam wrote: > Hello, > > I run into a problem when installing django 1.2 on my Mac. I follow > the recipe on the web page, i.e. I download django-1.2.tar.gz, unpa

Problem installing django 1.2 on Mac OS 10.6.3

Hello, I run into a problem when installing django 1.2 on my Mac. I follow the recipe on the web page, i.e. I download django-1.2.tar.gz, unpack it, and install by running sudo python setup.py install. After installing, django seems to work fine, but if I delete the directory I installed it from

Re: ANN: Django 1.1.2 and Django 1.2 released

On May 18, 12:39 am, rahul jain wrote: > Awesome job...but I discovered just one problem. Select all missing from > admin panel. So now i cannot select all the objects if i want to from admin > panel. It was fine on django 1.1. Its not fine on django 1.2 nor in the > developm

Re: ANN: Django 1.1.2 and Django 1.2 released

Awesome job...but I discovered just one problem. Select all missing from admin panel. So now i cannot select all the objects if i want to from admin panel. It was fine on django 1.1. Its not fine on django 1.2 nor in the development versions. --RJ On Mon, May 17, 2010 at 7:11 PM, Joshua Partogi

Re: ANN: Django 1.1.2 and Django 1.2 released

I have just read through the release notes, and really amazed how django 1.2 has evolved from 1.1. Kudos to everyone that is involved and put all effort into delivering django 1.2 Kind regards, Joshua On May 18, 9:46 am, Continuation wrote: > Congrats to the Django team. > > Thank

Re: CSRF protection in admin in Django 1.2

(AdminSite): csrf_protection = False I guess I'll open a ticket for it. Paul. On May 18, 10:47 am, Spaceman Paul wrote: > Hi, I just upgraded to Django 1.2 and am having some problems. > > My project contains several customised django.contrib.admin sites that > offer hig

CSRF protection in admin in Django 1.2

Hi, I just upgraded to Django 1.2 and am having some problems. My project contains several customised django.contrib.admin sites that offer highly stripped down subsets of admin functionality. These customised sites do not use authentication and are expected to be POSTed to both by users and by

Re: ANN: Django 1.1.2 and Django 1.2 released

Congrats to the Django team. Thanks for the great job. Really appreciate all your work. On May 17, 2:19 pm, James Bennett wrote: > We're pleased today to announce the release of both Django 1.1.2 -- > the second bugfix release in the 1.1 series -- and the long-awaited > Django

ANN: Django 1.1.2 and Django 1.2 released

We're pleased today to announce the release of both Django 1.1.2 -- the second bugfix release in the 1.1 series -- and the long-awaited Django 1.2. More information is available over at djangoproject.com: * Django 1.1.2 release announcement: http://www.djangoproject.com/weblog/2010/may/1

Re: Tests fail with django-1.2-rc1

Am Dienstag 11 Mai 2010, 16:38:40 schrieb Russell Keith-Magee: > On Tue, May 11, 2010 at 10:21 PM, Dirk Eschler wrote: > > Hello, > > > > i'm in the process of upgrading a project to django-1.2-rc1. While the > > project specific tests passed with django-1.1.1, t

Re: Tests fail with django-1.2-rc1

On Tue, May 11, 2010 at 10:21 PM, Dirk Eschler wrote: > Hello, > > i'm in the process of upgrading a project to django-1.2-rc1. While the project > specific tests passed with django-1.1.1, they all fail now with django-1.2-rc1 > (see example below). Any idea what's going

  1   2   >