Re: importing threading and dummy_threading

Done in https://github.com/django/django/pull/4003 On a related note, I am curious if anyone is running Django on a platform that lacks cPickle these days. We use this pattern in several places: try: from django.utils.six.moves import cPickle as pickle except ImportError: import pickle

Re: importing threading and dummy_threading

Given that it already doesn't worth without full threading in the previous LTS, I don't think we need to worry about it. On 28 January 2015 at 14:32, Tim Graham wrote: > Here's a 9 year old ticket referencing freebsd5.1... > > https://code.djangoproject.com/ticket/2052 > >

Re: importing threading and dummy_threading

Here's a 9 year old ticket referencing freebsd5.1... https://code.djangoproject.com/ticket/2052 On Wednesday, January 28, 2015 at 8:51:16 AM UTC-5, Tim Graham wrote: > > As far back as Django 1.4 (didn't check earlier), we use both these > patterns in the code: > > import threading > > try: >

importing threading and dummy_threading

As far back as Django 1.4 (didn't check earlier), we use both these patterns in the code: import threading try: import threading except ImportError: import dummy_threading as threading We also have logic in tests to skip if threading isn't available, however, I can't believe that

Re: GSOC 2015 project ideas suggestion

Hi, Thank you both of you for your response with guidelines. I found a old project Reducing coupling in Django components - *Complexity:* Hard and a newer project Improving URL dispatch - "Complexity:" Hard