Re: How to run all tests in INSTALLED_APPS with the new test runner 1.6?

And actually as of Django 1.8, the contrib tests aren't shipped inside each application directory, so they won't be discovered even if you switch to the old test runner. On Wednesday, October 7, 2015 at 11:21:54 AM UTC-4, jordi.gutie...@ecometrica.org wrote: > > On Wednesday, October 7, 2015 at

Re: formset concurrency control

I think the problem is also described in https://code.djangoproject.com/ticket/15574. Probably if we had a simple solution, that ticket wouldn't be open for 5 years. :-) On Thursday, October 8, 2015 at 12:48:34 PM UTC-4, Daniel Roseman wrote: > > Can you explain further why you think the pk is n

Re: Upgrade path for Django 1.4.9 to Django 1.6.0

The docs have some tips (but not much besides what James already offered): https://docs.djangoproject.com/en/dev/howto/upgrade-version/ On Friday, October 9, 2015 at 8:17:21 PM UTC-4, James Schneider wrote: > > > > In the past when I have upgraded my Django Projects to a new version of > Django

Re: django.contrib.auth 1.8 failed if user.pk not int

Here's the commit and ticket: https://github.com/django/django/commit/0f7f5bc9 https://code.djangoproject.com/ticket/24161 I think you'll probably have to fix this in your app, but if a change in Django will help, let me know. Possibly your user model needs a CharField for its primary key. On

Re: django.contrib.auth 1.8 failed if user.pk not int

certain magic method to_python() in > django.db.models.fields > Traceback is seen. > > суббота, 10 октября 2015 г., 6:25:50 UTC+5 пользователь Tim Graham написал: >> >> Here's the commit and ticket: >> >> https://github.com/django/django/commit/0f7f5bc9 >&

Re: Errors in tests when working through contribution tutorial

Hi Lee, I think the issue is that the tests don't pass on Python 3.5 at the commit where the contributing was tutorial was authored. I suppose we'll have to update it to use a more recent patch or at least mention this caveat for now. On Monday, October 12, 2015 at 5:12:20 PM UTC-7, Lee Cartwri

Re: running migrate through views itself

You can execute management commands from Python code using call_command(): https://docs.djangoproject.com/en/stable/ref/django-admin/#running-management-commands-from-your-code It seems a bit risky to me to expose functionality to your users that allow them to change your database schema as a re

Re: Help with UnaccentExtension migration

That migration file looks correct to me. How did you determine the query didn't get run? Are you logging all queries? On Sunday, October 11, 2015 at 9:30:19 AM UTC-7, pusateri wrote: > > I was trying to enable the unaccent postgresql extension using a database > migration as hinted here: > > > h

Re: Get unversioned static file url while using CachedStaticFilesStorage

If you used the "as var" syntax: {% static "myapp/css/base.css" as admin_base_css %}, then you could write a custom template filter that removes the version suffix and then apply it to that variable. On Sunday, October 11, 2015 at 11:28:10 AM UTC-7, Dheerendra Rathor wrote: > > Hello all, > > I

Re: ManyToMany doesn't support validators?

The rationale is described in https://code.djangoproject.com/ticket/19671. On Tuesday, October 13, 2015 at 7:06:16 AM UTC-7, Mike Herring wrote: > > Doc here: > > https://docs.djangoproject.com/en/1.8/ref/models/fields/#django.db.models.ManyToManyField > > ManyToManyField does not support validato

Re: Django 1.8: subclass AbstractUser, App 'auth' doesn't have a 'myuser' model.

Do you want to use the custom user model or not? What extra tables are created? On Tuesday, October 13, 2015 at 1:31:03 PM UTC-7, Norberto Bensa wrote: > > Hello, > > I'm re-posting this. > > Note that I already tried AUTH_USER_MODEL = "myauth.MyUser', and while > that makes the problem disapp

Re: ValueError: save() prohibited to prevent data loss due to unsaved related object

Do you have code that worked before (didn't result in data loss) but doesn't work now? If so, it could be a bug in Django. On Friday, October 16, 2015 at 8:30:07 PM UTC-4, Mike Dewhirst wrote: > > I think I understand this error and I like what it does. My question is > ... > > What is the nece

[ANNOUNCE] Django 1.9 beta 1 released

We've made the second release on the way to Django's next major release, Django 1.9! With a month and a half until the scheduled final release, we'll need timely testing from the community to ensure an on-time and stable release. Check out the blog post: https://www.djangoproject.com/weblog/201

Re: ValueError: save() prohibited to prevent data loss due to unsaved related object

Could you provide a minimal example project that reproduces the error? On Tuesday, October 20, 2015 at 2:42:57 AM UTC-4, Mike Dewhirst wrote: > > On 18/10/2015 5:18 PM, Mike Dewhirst wrote: > > On 18/10/2015 6:28 AM, Tim Graham wrote: > >> Do you have code that worked bef

Re: save() prohibited to prevent data loss due to unsaved related object 'committee'

What does the Committee.save() method look like? You have no problem if you remove that method? On Tuesday, October 20, 2015 at 2:22:24 PM UTC-4, Yaniv Mirel wrote: > > I've found out that this error is happening because I also have a def > save() function on the committee model. > So I am not s

Re: save() prohibited to prevent data loss due to unsaved related object 'committee'

ug = 'committee-%s' % self.id > > And yes, after removing that save function everything works fine. > > On Tuesday, October 20, 2015 at 9:32:20 PM UTC+3, Tim Graham wrote: >> >> What does the Committee.save() method look like? You have no problem if >> you re

Re: solution to static file loading issue on 1.8

Hi Becka, You've provided the default value for STATICFILES_FINDERS so putting that in your settings shouldn't make a difference. An example of STATICFILES_DIRS is given at: https://docs.djangoproject.com/en/1.8/howto/static-files/ If you have a suggestion about how to improve the docs that wo

Re: solution to static file loading issue on 1.8

sibilities, this is > what removed the error. > > Thanks! > > On Friday, October 23, 2015 at 10:25:23 AM UTC-7, Tim Graham wrote: >> >> Hi Becka, >> >> You've provided the default value for STATICFILES_FINDERS so putting that >> in your setti

Re: Reverse relation lookups with multidb

I don't think this has anything to do with multi-db. I'm not sure what that query is trying to accomplish. Can you simply use: ProfielenUserprofile.objects.values('profielnaam') You can't use values() across a reverse ForeignKey ("foo_set") as this might return multiple values. On Saturday,

Re: Reverse relation lookups with multidb

It would be helpful if you could create a minimal example project (without unnecessary fields and methods) with a test that passes on Django 1.6 but fails on Django 1.8. On Saturday, October 24, 2015 at 9:13:42 AM UTC-4, probleem support wrote: > > this worked fine in django 1.6.1 but fails in

Re: looking for a basic model form example

Have you tried: https://docs.djangoproject.com/en/1.8/topics/forms/ - for form basics https://docs.djangoproject.com/en/1.8/topics/forms/modelforms/ - for model form specifics If you can explain your confusion in any more detail, it might help us improve the documentation. I'm not sure what yo

Re: Relation fields do not support nested lookups

A minimal project that reproduces the error would be helpful. Please avoid duplicating your post on django-users and in Trac (until it's a confirmed bug in Django). Thanks! On Tuesday, October 27, 2015 at 8:53:20 AM UTC-4, probleem support wrote: > > He all, > > Does anyone know why i can't do a

Re: Reverse relation lookups with multidb

As noted on the ticket, it looks like you're missing an app in INSTALLED_APPS. On Tuesday, October 27, 2015 at 10:55:51 AM UTC-4, probleem support wrote: > > test project proving my point > https://github.com/gerdkoetje/dualdbtest > -- You received this message because you are subscribed to the

Re: Relation fields do not support nested lookups

As noted on the ticket, it looks like you're missing an app in INSTALLED_APPS. On Tuesday, October 27, 2015 at 10:55:21 AM UTC-4, probleem support wrote: > > test project proving my point > https://github.com/gerdkoetje/dualdbtest > -- You received this message because you are subscribed to the

Re: Flakey tests and django.db.utils.InterfaceError: connection already closed

A test project that reproduces the problem would be helpful. On Tuesday, October 27, 2015 at 9:14:13 AM UTC-4, Christopher R. wrote: > > Have you been able to fix the problem? I am encountering the same issue on > both Django 1.8.4 and 1.8.5. > > Any help would be appreciated. > > On Thursday, Oc

Re: Django admin add related object doesn't open popup window?

Please check the JavaScript console in your browser to see if there are any errors. On Tuesday, October 27, 2015 at 11:18:18 AM UTC-4, j.coss...@gmail.com wrote: > > Thanks, I succesfully disabled the add related button, as a temporary > patch. > > Any ideas of why the pop-up isn't working? >

Re: Reverse relation lookups with multidb

In order to use models and their relations you have to include them in INSTALLED_APPS regardless of which database they are stored in. This is noted in the 1.7 release notes: https://docs.djangoproject.com/en/1.8/releases/1.7/#app-registry-consistency Maybe you don't want your local project to

Re: Test problems after upgrading to 1.8

It seems a bit difficult to debug from what you provided so far. One idea: do you have migrations for all your apps? If you could put together a minimal project that reproduces the problem that would be useful. On Wednesday, October 28, 2015 at 4:19:25 AM UTC-4, o_r wrote: > > I've recently upg

Re: include template which extends something else

I think that's a limitation described in the {% include %} docs: https://docs.djangoproject.com/en/1.8/ref/templates/builtins/#include. See the "Note" box where it says: The include tag should be considere

Re: Missing default callable breaks migration

Please read https://docs.djangoproject.com/en/stable/topics/migrations/#historical-models In particular, "References to functions in field options such as upload_to and limit_choices_to and model manager declarations with managers having use_in_migrations = True are serialized in migrations, so

Re: include template which extends something else

_template > html? > > Hope I achieved to explain the problem well enough... > > 2015-10-28 16:39 GMT+01:00 Tim Graham >: > >> I think that's a limitation described in the {% include %} docs: >> https://docs.djangoproject.com/en/1.8/ref/templates/builtins/

Re: Wherenode?

GitHub has a nice feature that allows you to search a repository: https://github.com/django/django/search?utf8=%E2%9C%93&q=WhereNode On Wednesday, October 28, 2015 at 1:32:40 PM UTC-4, varun naganathan wrote: > > Can anybody please explain what a django WhereNode is? Also provide any > possible

Re: Running migrations on the non-default database fails

I think this bit from the Django 1.8 release notes might help: * The migration operations RunPython and RunSQL

Re: mssql databASE CONNECTION to Django

django-mssql doesn't support Django 1.8 yet: https://django-mssql.readthedocs.org/en/latest/changelog.html On Thursday, October 29, 2015 at 9:36:38 PM UTC-4, Sid wrote: > > *Hi all,* > I am trying to connect database which is in server to django, but it is > showing many errors like(platform i a

Re: mssql databASE CONNECTION to Django

Please read the documentation: https://django-mssql.readthedocs.org/en/latest/quickstart.html On Friday, October 30, 2015 at 9:53:42 AM UTC-4, Sid wrote: > > so which version will be compatible... > > On Friday, October 30, 2015 at 7:54:26 AM UTC-4, Tim Graham wrote: >> >&

Re: mssql databASE CONNECTION to Django

Sorry, I haven't used the library myself and can't provide any additional help. On Friday, October 30, 2015 at 10:31:35 AM UTC-4, Sid wrote: > > sorry tim I know I am asking a dumb question...can you please tell me what > is the best way to make it work please if possibe...because I am struck >

Re: Does the bulk delete check the permissions correctly?

I think there are a number of open tickets related to this. See https://code.djangoproject.com/ticket/23869 and the first comment that links to related issues. Feel free to offer a patch if you are able. On Friday, October 30, 2015 at 3:04:21 PM UTC-4, Szymon Pyżalski wrote: > > Hello! > > Acco

[ANNOUNCE] Django bugfix release issued: 1.8.6

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2015/nov/04/bugfix-release-issued/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send a

Re: Spatialite for GeoDjango can't be loaded on Ubuntu Wily Werewolf

Thanks for the report. I'd encourage you to use the geodjango mailing list to raise this issue. On Saturday, November 7, 2015 at 12:03:10 AM UTC+1, Berthier Lemieux wrote: > > Hi! > > When I try to use django.contrib.gis.db.backends.spatialite as my db engine > on Ubuntu Wily Werewolf (15.10),

Re: Bug: Manually changing "_meta.db_table" for model causes "missing FROM-clause entry for table" error

I'm not sure that type of monkeypatching of Model._meta.db_table is meant to be supported. You could try to bisect Django's commit history to find the commit that changed the behavior. My guess it that it might have to do with some internal caching such that your monkeypatch no longer has any e

Re: Model Meta option default_related_name not setting related_query_name

I guess it would be backwards incompatible if we changed the behavior now, wouldn't it? On Friday, November 13, 2015 at 1:40:27 PM UTC-5, Alejandro Do Nascimento wrote: > > django...@googlegroups.com > > Hello, > > I have a doubt, In a model I'm using the Meta option * > default_related_name*

[ANNOUNCE] Django 1.9 release candidate 1 released

We're closing in on the final Django 1.9 release, so it's release candidate time! Details are up on the Django project blog: https://www.djangoproject.com/weblog/2015/nov/16/django-19rc1-released/ -- You received this message because you are subscribed to the Google Groups "Django users" grou

Re: [Django 1.8.6] How to dump sql from models

For Django 1.9+, I don't think there's a built-in way to do so. Until that feature makes its way into Django (if it ever does), it might not be difficult to reimplement those commands to the extent that you need them as a third-party app. See https://groups.google.com/d/topic/django-developers/

Re: Form/widget Media urls not using the hashed names from ManifestStaticStorage?

There's a ticket about it: https://code.djangoproject.com/ticket/21221 I think it's likely to be fixed in Django 1.10. In the meantime, you have to wrap the Media urls with django.contrib.staticfiles.templatetags.staticfiles.static. On Wednesday, November 18, 2015 at 12:51:28 PM UTC-5, Bart van

Re: Django admin add related object doesn't open popup window?

C-5, Jorge Fernandez-de-Cossio-Diaz wrote: > > I pressed F12 on Firefox, and played around to see if I could find > anything. But I didn't see anything that looked like an error. But I'm not > sure what I am looking for. What else can I do? > > > On Tuesday, October

Re: Escaping of help_text in form fields

It's expected behavior and mentioned in the model field help_text docs, but not form field help_text docs. I'll fix that. https://docs.djangoproject.com/en/stable/ref/models/fields/#django.db.models.Field.help_text On Tuesday, November 24, 2015 at 9:34:18 AM UTC-5, not...@gmail.com wrote: > > Hi

[ANNOUNCE] Django security releases issued (1.7.11, 1.8.7, and 1.9rc2)

Today the Django team issued multiple releases -- Django 1.7.11, 1.8.7, and 1.9rc2 -- as part of our security process. These releases address a security issue, and we encourage all users to upgrade as soon as possible. More details can be found on our blog: https://www.djangoproject.com/weblog/

Re: RemoteUserMiddleware stay logged in

Does the PersistentRemoteUserMiddleware added in Django 1.9 help? https://docs.djangoproject.com/en/1.9/howto/auth-remote-user/#using-remote-user-on-login-pages-only On Monday, November 30, 2015 at 3:36:00 PM UTC-5, Dan Davis wrote: > > So, where I work we have a CAS server we like to use. We l

Re: Clear view cache using @cache_page

I don't know of a simple way. Here's something I wrote to achieve that on djangoproject.com (invalidating a cached blog post on save): https://github.com/django/djangoproject.com/blob/90e92fd18543f95685c24f84dc5e1269a5acc38a/blog/models.py#L105-L116 Adding something to Django to help with this s

Re: Django 1.9 cache.get_or_set issue while using DummyCache backend

It seems to be an omission in the implementation. Feel free to create a Trac ticket and offer a patch if you can. For future reference, please don't cross post between django-users (appropriate place for "is it a bug?" questions) and django-developers. Thanks! On Tuesday, December 1, 2015 at 7

[ANNOUNCE] Django 1.9 released

Django 1.9 is now available: https://www.djangoproject.com/weblog/2015/dec/01/django-19-released/ With the release of Django 1.9, Django 1.7 has reached end-of-life. Django 1.7.11 is the final release of the 1.7 series and all users are encouraged to upgrade to Django 1.8+ as soon as possible s

Re: Tests not passing in suite but pass individually

It will be easier to help if you can provide a sample project that reproduces the error. On Wednesday, December 2, 2015 at 3:01:31 AM UTC-5, Siddhi Divekar wrote: > > Hi, > > Am seeing that test case in suite are failing but passing when ran > individually. > I have gone through most of the thre

Re: Tests not passing in suite but pass individually

stomer_list), 0) > > def test_create_customer(self): > '''Handle customer create.''' > customer_list = CustomerDb.objects.all() > self.assertEqual(len(customer_list), 1) > > test_create_customer runs first, test_customer

Re: [ANNOUNCE] Django 1.9 released

^ > > SyntaxError: invalid syntax > > Successfully installed django > > Cleaning up... > > > > Anyone else see this error? This was in an new virtualenv. > > It's mentioned in the release notes (specifically at > https://

Re: Tests not passing in suite but pass individually

modify and delete operations in DB. > -- > Traceback (most recent call last): > File "/home/sidhesh/workspace/sztp/orca/tests/tmp.py", line 26, in > test_customer_create_modify_delete > self.assertEq

Re: Video Erich Holschercom on django under the hood ?

Here's a link with all the videos from this year's conference: https://opbeat.com/events/duth/ On Thursday, December 3, 2015 at 1:34:40 PM UTC-5, Carlos Leite wrote: > > Hello everyone, i'm brazilian django user, not so used to wirte here > > last weekend I watched a video about DJango and D

Re: How to add myself as a developer for hire in the wiki?

You can login using a Trac or GitHub account, then click "Edit this page" at the bottom of the page. On Wednesday, December 9, 2015 at 5:47:42 AM UTC-5, James Lin wrote: > > https://code.djangoproject.com/wiki/DevelopersForHire > > Cheers. > -- You received this message because you are subscrib

Re: Tests not passing in suite but pass individually

,* > *#'TEST': {* > *#'NAME': 'testdb',* > *#},* > }, > 'sztp': { > 'ENGINE': 'django.db.backends.postgresql_psycopg2', > 'NAME': 'sztpdb', >

Re: Tests not passing in suite but pass individually

fails. I think its better not to keep on modifying the > router. > > Is there anything wrong with the app database definition below. > > 'orca': { > 'ENGINE': 'django.db.backends.postgresql_psycopg2', > 'NAME'

Re: How to add myself as a developer for hire in the wiki?

Feel free to remove such entries if you like. On Wednesday, December 9, 2015 at 1:40:58 PM UTC-5, larry@gmail.com wrote: > > On Wed, Dec 9, 2015 at 7:41 AM, Tim Graham > wrote: > > You can login using a Trac or GitHub account, then click "Edit this > page" at

Re: git exclude files

I don't know of a use case where virtualenvs are stored in source control. I wouldn't recommend putting the virtual environment in your project folder either. If you use a tool like virtualenvwrapper [1] you can store all your virtualenvs in a single directory on your system to make managing the

Re: Django 1.9 ./manage.py migrate error

Does your application have migrations? Quoting the 1.9 release notes, "Automatic syncing of apps without migrations is removed. Migrations are compulsory for all apps unless you pass the --run-syncdb opt

Re: Populating default data into sql tables using sql file inside the sql folder of app is not working

You can use migrations and the RunSQL operation. https://docs.djangoproject.com/en/stable/ref/migration-operations/#runsql On Saturday, December 12, 2015 at 8:59:08 AM UTC-5, naveen tamanam wrote: > > In older django versions I use to load the default values using sql files > which are in the fo

Re: Django 1.9 ./manage.py migrate error

cember 12, 2015 at 11:53:37 AM UTC-5, Xuton Ion wrote: > > No, I haven't added any migrations. > > I did try with --run-syncdb though, and still had the same error though > > On Saturday, 12 December 2015 16:26:15 UTC+2, Tim Graham wrote: >> >> Does your applicat

Re: Gsoc 2016 contribution

Hi Yash, Learning our contributing process and having a solid track record of contributing patches will enhance your chances of writing a successful application. If you don't have any Django experience, start with our tutorial: https://docs.djangoproject.com/en/dev/intro/tutorial01/ After you

Re: Error while customising Django User

If you didn't start your project with a custom user, it's non-trivial to start using one. Please see https://code.djangoproject.com/ticket/25313. On Friday, December 18, 2015 at 6:55:16 AM UTC-5, Web Architect wrote: > > Hi, > > I am new to Django and still under the process of learning. We are u

Re: Error while customising Django User

eries seem out of the way as I am new to Django. > > Thanks. > > On Friday, December 18, 2015 at 8:24:57 PM UTC+5:30, Tim Graham wrote: >> >> If you didn't start your project with a custom user, it's non-trivial to >> start using one. Please see https://cod

Re: TemplateDoesNotExist Again

Could you check if it's still an issue on Django 1.9? There were several improvements to template loading in that release [1]. If it is, could you provide a sample project with the exact case to be improved? [1] https://docs.djangoproject.com/en/1.9/releases/1.9/#filesystem-based-template-loade

Re: Question re django.forms.models.BaseModelFormSet.save_existing_objects()

Hi Mike, see if the documentation at the bottom of https://docs.djangoproject.com/en/stable/topics/forms/formsets/#django.forms.formsets.BaseFormSet.can_delete helps. On Monday, December 21, 2015 at 4:00:36 AM UTC-5, James Schneider wrote: > > > > That is true. However, if commit was False that

Re: django 1.9 - application does not

There's a bug in Django 1.9 that hides the actual exception when you use runserver. Try adding runserver --nothreading to see the actual exception. It will be fixed in Django 1.9.1 which will likely be released next week. On Thursday, December 24, 2015 at 10:23:03 AM UTC-5, Sergiy Khohlov wrote:

Re: pip install django

There was a bug in pypi earlier today. On Thursday, December 24, 2015 at 9:50:09 AM UTC-5, Gil wrote: > > Same problem from EU. > > On Thursday, December 24, 2015 at 3:10:15 PM UTC+1, john...@gmail.com > wrote: >> >> Is failing from several machines this morning. >> >> >pip install django --upgr

[ANNOUNCE] Django bugfix releases issued: 1.9.1 and 1.8.8

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2016/jan/02/bugfix-releases-issued/ On a related note: Python 3.2 users, please be advised that we've decided to drop support for Python 3.2 in Django 1.8.x at the end of 2016. We won't break things intenti

Re: Is it a bad idea to start a project using Django 1.7 at this moment?

Yes, it's a bad idea. Django 1.7 is unsupported and no longer receives security updates. Please use at least the Django 1.8 series (the latest is 1.8.8 as of now) which is a long-term support release and will receive security updates until April 2018 as described at https://www.djangoproject.co

Re: "last_login", null=True not migrated

You initial migration must have a state with the field as null=False so that Django can detect it has changed between migration 1 and 2. It sounds like you may have gotten that incorrect. On Tuesday, January 5, 2016 at 9:00:05 AM UTC-5, Norberto Bensa wrote: > > BTW, I just discovered: > > $ ./m

Re: RuntimeError: maximum recursion depth exceeded in cmp

I've never seen that before. I think you'll need to provide a sample project that reproduces it so that someone can take a look. On Thursday, January 28, 2016 at 7:45:31 AM UTC-5, Deepak Singh wrote: > > Hi, > > During (python manage.py runserver) command I am getting following error > >

[ANNOUNCE] Django releases issued: 1.9.2 (security) and 1.8.9 (bugfix)

Today the Django team issued 1.9.2 as part of our security process. This releases address a security issue, and we encourage all users to upgrade as soon as possible. The Django 1.8.9 release fixes several bugs in 1.8.8 but no security issues as the issue fixed in 1.9.2 doesn't affect older ver

Re: ProgrammingError django_content_type already exists

I think https://docs.djangoproject.com/en/stable/ref/django-admin/#cmdoption-migrate--fake-initial should help. On Wednesday, February 3, 2016 at 9:16:36 AM UTC-5, M Hashmi wrote: > > I've been stuck on this issue for a while now. If anyone have concrete > solution please let me know. > I subs

Re: Handling cookies that contain illegal values

This is caused by a security fix in Python (which Django uses for cookie parsing). I think the issue can be fixed without cause security problems but I'm not sure. Please follow https://code.djangoproject.com/ticket/26158 and related Python tickets. On Friday, February 5, 2016 at 3:13:14 AM UTC

Re: After upgrading from 1.8.8 to 1.9.2 migration applies succesfully but ends with an error

Last time I checked, mysql.connector hasn't issued a release that's compatible with Django 1.9. On Monday, February 8, 2016 at 7:37:36 AM UTC-5, Richard la Croix wrote: > > I just upgraded from 1.8.8 to 1.9.2 and using Python version 3.4.3. > > The included Django migrations (admin.0002_logentry_

Re: WeakMethod import error in Django 1.9 with python 3.3

As noted in the Django 1.9 release notes, "Django 1.9 requires Python 2.7, 3.4, or 3.5." On Tuesday, February 9, 2016 at 5:49:41 AM UTC-5, Mohammad Asif wrote: > > Hello, > > I'm using django 1.9.1 with python 3.3. > Whenever I'm running manage.py runserver, I'm getting following error. > > * Fil

Re: Django saved instance model WITH ERROR

It's expected behavior. If you don't want to save an invalid instance, then don't call save() after you call full_clean() and encounter errors. As documented [1], calling save() itself don't do any validation. [1] https://docs.djangoproject.com/en/stable/ref/models/instances/#validating-objects

Re: manage.py --keepdb VS DataMigration as Initial Data

You might be running into the same problem reported in https://code.djangoproject.com/ticket/25251#comment:3 On Thursday, February 11, 2016 at 1:16:20 PM UTC-5, Carlos Leite wrote: > > Hi there, > > I'm running a Django==1.8 app > I read in the docs [1], to consider doing a data migration to lo

Re: Django is creating duplicate queries for prefetch_related

Maybe https://code.djangoproject.com/ticket/25546 fixes it? This will be in Django 1.10. On Friday, February 12, 2016 at 10:18:22 PM UTC-5, Dheerendra Rathor wrote: > > Hello, > > Recently I was monitoring db queries created by Django and a particular > block was behaving unusual. > Here is the

Re: Migrations in Django 1.9: verbose_name and verbose_name_plural

The only thing that comes to mind is a paragraph in the 1.8 release notes, "When the leave_locale_alone attribute is False, translations are now deactivated instead of

Re: De Morgan's Law and QuerySet semantics

I didn't read closely enough to completely understand but i'll mention that Q object behavior is one of the trickiest bits of the ORM. Some of the relevant reading might be: * https://github.com/django/django/pull/4385 * https://github.com/django/django/pull/6005 Anssi would be the person to ta

Re: Migrations in Django 1.9: verbose_name and verbose_name_plural

it's about urls, not migrations. > I've a few RemovedInDjango110Warnings related to urls due to 3rd parties > packages (django.conf.urls.patterns() is deprecated, Support for string > view arguments to url() is deprecated) > > > Il giorno domenica 14 febbraio 2016 03:5

Re: Tutorial 5 (Testing) seems to have an error

It looks like you have a Python path problem or that your project isn't structured correctly such that the model is being registered twice. Does that mean anything to you? I'm not sure if you are also new to Python or just to Django. On Monday, February 15, 2016 at 11:16:51 AM UTC-5, Eric Livin

Re: Migrations in Django 1.9: verbose_name and verbose_name_plural

the related view is WizardCreateView >> <https://github.com/divio/django-cms/blob/f1e04a539d9df7df19fc4412b8f80f3ea471ea3e/cms/wizards/views.py#L42-L171> >> . >> >> Cheers >> Marco >> >> Il giorno lunedì 15 febbraio 2016 15:31:34 UTC+1, Tim Graham ha scr

Re: Github v code.djangoproject for bug reports

Please read https://code.djangoproject.com/newticket for an explanation of what type of issue should be reported where. On Thursday, February 18, 2016 at 10:41:54 AM UTC-5, Malik Rumi wrote: > > Does it matter if a bug is reported to one and not the other? Is there any > difference between the

Re: datetime.date is not json serializable

datetime isn't JSON serializable by default. Django includes a custom encoder which handles datetime and some other types. You can use it like this: from django.core.serializers.json import DjangoJSONEncoder data = json.dumps(data, cls=DjangoJSONEncoder) On Friday, February 19, 2016 at 3:02:48

Re: TypeError: view must be a callable or a list/tuple in the case of include()

You need to import your views and reference the callable as described at https://docs.djangoproject.com/en/stable/topics/http/urls/#example. Referencing the view by string using patterns() is deprecated: https://docs.djangoproject.com/en/stable/releases/1.8/#django-conf-urls-patterns On Friday,

Re: Possible Bug when using exclude on a GenericForeignKey / GenericRelation query.

The crash is probably a bug: https://code.djangoproject.com/ticket/26261 On Friday, August 14, 2015 at 5:01:30 PM UTC-4, Daniel H wrote: > > Hi everyone. > > I've been using django for almost a year now, but it's my first time > posting here. > > Anyway, I'm encountering an error which I think mi

[ANNOUNCE] Django security releases issued: 1.9.3 and 1.8.10

Today the Django team issued 1.9.3 and 1.8.10 as part of our security process. This releases address two security issues, and we encourage all users to upgrade as soon as possible. Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2016/mar/01/security-rele

Re: [ANNOUNCE] Django security releases issued: 1.9.3 and 1.8.10

ding django 1.8.9 to 1.8.10 my i18n/setlang/ went crazy > "TypeError: must be unicode not str" when using {% url 'set_language' %} by > going back to 1.8.9 solved the issue. > > El martes, 1 de marzo de 2016, 12:50:27 (UTC-4:30), Tim Graham escribió: >> >> T

Re: Show labels next to ManyToMany raw_id_fields

ticket is: https://code.djangoproject.com/ticket/26313 On Tuesday, February 17, 2009 at 4:52:25 PM UTC-5, Alex Gaynor wrote: > > > > On Tue, Feb 17, 2009 at 4:50 PM, João Olavo Baião de Vasconcelos < > joao...@gmail.com > wrote: > >> On Tue, Feb 17, 2009 at 5:15 PM, Alex Gaynor > > wrote: >> >>> S

Re: Problem Django.19 upgrade and circular imports

No ideas off the top of my head. You could try bisecting to find the commit in Django where the behavior changed. https://docs.djangoproject.com/en/dev/internals/contributing/triaging-tickets/#bisecting-a-regression On Thursday, March 3, 2016 at 6:29:38 PM UTC-5, Andres Osinski wrote: > > Hi eve

[ANNOUNCE] Django bugfix releases issued: 1.9.4 and 1.8.11

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2016/mar/05/bugfix-releases/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an emai

Re: Google App Engine in 2016

Djangae is a database backend for App Engine that's under active development: https://github.com/potatolondon/djangae On Monday, March 7, 2016 at 10:33:16 AM UTC-5, Silvan Spross wrote: > > Hi everybody > > Does anyone use Google App Engine to run a "real" Django application? I > want to give Go

Re: Password hasher for vBulletin?

Take a look at https://docs.djangoproject.com/en/stable/topics/auth/passwords/#password-upgrading-without-requiring-a-login Instead of SHA1PasswordHasher().encode() you'll want to use vBulletin's hashing algorithm. On Tuesday, March 15, 2016 at 11:54:32 AM UTC-4, jorr...@gmail.com wrote: > > I'

Re: Password hasher for vBulletin?

y crap, you guys have really thought of everything! Love it! > > Unfortunately this doesn't work on all users because some salts contain > the *$* character which gives the *assert salt and '$' not in salt* > error. Is there a workaround for this? > > > On Tue

<    1   2   3   4   5   6   >