Re: Exiting from a management command with a given exit status

[Johannes Schneider]

thnx,
I thought there might be a more django-like way.

On 23.01.2014 15:48, Erik Cederstrand wrote:

import sys
 sys.exit(123)



--
Johannes Schneider
Webentwicklung
johannes.schnei...@galileo-press.de
Tel.: +49.228.42150.xxx

Galileo Press GmbH
Rheinwerkallee 4 - 53227 Bonn - Germany
Tel.: +49.228.42.150.0 (Zentrale) .77 (Fax)
http://www.galileo-press.de/

Geschäftsführer: Tomas Wehren, Ralf Kaulisch, Rainer Kaltenecker
HRB 8363 Amtsgericht Bonn

--
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 email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/52E2200F.8040801%40galileo-press.de.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Exiting from a management command with a given exit status

[James Bennett]

On Fri, Jan 24, 2014 at 2:10 AM, Johannes Schneider <
johannes.schnei...@galileo-press.de> wrote:

> thnx,
> I thought there might be a more django-like way.


Using standard features of Python and its built-in libraries *is* the
"Django-like way".

-- 
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 email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAL13Cg9iiYnKAirkahuiQ5UabsizQBg-6vO4_6n8%3DkQTp9hhOA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

migrations to custom user model - complex project

[Frank Bieniek]

Hi All,
a do have to upgrade an existing
django project, it is an openid provider with around 10k users.
In order to update to django 1.6 I do need to get rid of
the good old AUTH_PROFILE_MODULE and need to switch
to CustomUserModel, and I do not want to break existing mysql constraints.

Django==1.5.5
South==0.8.4
python-openid
django-tastypie==0.10.0
django-guardian==1.1.1
django_openid_provider
django-userena==1.2.4
...
But I do not want to touch only a minimal set of files possible
and do not want to do a dumpdata load data mess.

There must be an elegant solution, someone else has already done

Any hints are welcome - I googled already, but have not found a solution
that does not break groups or other fks...


Thanks
Frank

--
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 email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/52E27464.7080304%40produktlaunch.de.
For more options, visit https://groups.google.com/groups/opt_out.

Widget attributes in ModelForm

[Timothy W. Cook]

My widget attribute settings  aren't having any effect in the render
template.

View:
class DvBooleanCreateView(CreateView):
template_name = 'dvboolean_create.html'
success_url = '/dashboard'
model = DvBoolean
form = DvBooleanCreateForm
fields =
['prj_name','data_name','lang','valid_trues','valid_falses','description','sem_attr','resource_uri','asserts',]


Form:
class DvBooleanCreateForm(ModelForm):
class Meta:
model = DvBoolean
#fields =
['prj_name','data_name','lang','valid_trues','valid_falses','description','sem_attr','resource_uri','asserts',]
widgets = {
'description': Textarea(attrs={'cols':40, 'rows':3}),
   }


The form as displayed in the browser has the default size with or without
the widgets settings in the ModelForm.

What am I missing?

Thanks,
Tim








-- 
MLHIM VIP Signup: http://goo.gl/22B0U

Timothy Cook, MSc   +55 21 94711995
MLHIM http://www.mlhim.org
Like Us on FB: https://www.facebook.com/mlhim2
Circle us on G+: http://goo.gl/44EV5
Google Scholar: http://goo.gl/MMZ1o
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook

-- 
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 email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CA%2B%3DOU3XCPx%2B%3DyRhjK%3D%3DR0w4Q5Q1t1b4A%3D%3Dr7oqEgsbexr_-qog%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Error related to googlebot?

[Doug]

I am having this same exact problem. Did you ever find a resolution? 

Thanks.
Doug

On Monday, July 12, 2010 2:10:49 PM UTC-4, Tor Nordam wrote:
>
> I'm currently writing a blog framework in django, and I have it up an 
> running (on www.presskanne.com). During the last 20 hours or so, I 
> have gotten about 60 emails with error 500 messages. They seem to 
> originate from different pages all over the site, but they all have 
> two things in common: 
>
> The tracebacks all show that the problem is in importing one 
> particular model 
>
> The clients are all either googlebot or yahoo slurp 
>
> Also, I can't reproduce any of the errors myself. When I visit the 
> offending urls, everything either seems fine, or in the case of a 
> nonexistent page, I get a nice 404 message. 
>
> So my question is if there is anything in particular which might cause 
> the page to crash when a searchbot tries to load it, but not do the 
> same for a regular user.

-- 
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 email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/08289acf-2fef-4953-b77c-153001ec8ef9%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Error related to googlebot?

[James Turley]

Are you doing any user agent sniffing anywhere? If you make a request
having spoofed your UA to match one of the offending Google/Yahoo bots, do
you get the same 500 errors? Anything in robots.txt?


On Fri, Jan 24, 2014 at 4:44 PM, Doug  wrote:

> I am having this same exact problem. Did you ever find a resolution?
>
> Thanks.
> Doug
>
> On Monday, July 12, 2010 2:10:49 PM UTC-4, Tor Nordam wrote:
>>
>> I'm currently writing a blog framework in django, and I have it up an
>> running (on www.presskanne.com). During the last 20 hours or so, I
>> have gotten about 60 emails with error 500 messages. They seem to
>> originate from different pages all over the site, but they all have
>> two things in common:
>>
>> The tracebacks all show that the problem is in importing one
>> particular model
>>
>> The clients are all either googlebot or yahoo slurp
>>
>> Also, I can't reproduce any of the errors myself. When I visit the
>> offending urls, everything either seems fine, or in the case of a
>> nonexistent page, I get a nice 404 message.
>>
>> So my question is if there is anything in particular which might cause
>> the page to crash when a searchbot tries to load it, but not do the
>> same for a regular user.
>
>  --
> 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
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/08289acf-2fef-4953-b77c-153001ec8ef9%40googlegroups.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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 email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAAb4X%3Dzv4fGbVvigwhQ-hctC5NHmFH5EHR_cyFmnnW9EdBjUFA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

label_tag bug in Django 1.6. with mark_safe + ugettext_lazy ?

[neal]

Hi,

I'm in the process of upgrading a Django application from 1.5 to 1.6 and 
I've come across a mark_safe + ugettext_lazy issue in form field labels 
that I think might be a bug introduced in 1.6 (possibly related to the 
introduction of the new Form.label_suffix?).

Before reporting it I thought I check here first to see if people think it 
is a bug.

In essence, given a label that is a translatable string containing HTML and 
wrapped in mark_safe, e.g. mark_safe(_("Foo"), calling label_tag 
on the field in a template:

in Django 1.5 results in a non-escaped string: Foo
in Django 1.6 results in an escaped string: Foo:

(including the default label suffix of ":" for 1.6).

I was expecting 1.6 to render: Foo:

Here's a shell example for 1.5 and 1.6 that distills what I'm getting:

>>> import django
>>> django.get_version()
'1.5.5'
>>> from django import forms
>>> from django.template import Template, Context
>>> from django.utils.safestring import mark_safe
>>> from django.utils.translation import ugettext_lazy as _
>>> class FooForm(forms.Form):
... foo = forms.IntegerField(label=mark_safe(_("Foo")))
... 
>>> fooForm = FooForm()
>>> fooForm.fields['foo'].label
u'Foo'
>>> Template("{{ f }}").render(Context({'f': fooForm}))
u'Foo:'
>>> Template("{{ f.foo.label }}").render(Context({'f': fooForm}))
u'Foo'
>>> Template("{{ f.foo.label_tag }}").render(Context({'f': fooForm}))
u'Foo'


>>> import django
>>> django.get_version()
'1.6.1'
>>> from django import forms
>>> from django.template import Template, Context
>>> from django.utils.safestring import mark_safe
>>> from django.utils.translation import ugettext_lazy as _
>>> class FooForm(forms.Form):
... foo = forms.IntegerField(label=mark_safe(_("Foo")))
... 
>>> fooForm = FooForm()
>>> fooForm.fields['foo'].label

>>> Template("{{ f }}").render(Context({'f': fooForm}))
u'Foo:'
>>> Template("{{ f.foo.label }}").render(Context({'f': fooForm}))
u'Foo'
>>> Template("{{ f.foo.label_tag }}").render(Context({'f': fooForm}))
u'Foo:'


It may or may not be related but when I tried delaying the translation as 
described in 
https://docs.djangoproject.com/en/dev/topics/i18n/translation/#other-uses-of-lazy-in-delayed-translations
 
I got a TypeError under 1.6 when passing the lazy object to ugettext:

>>> import django
>>> django.get_version()
'1.5.5'
>>> from django.utils import six  # Python 3 compatibility
>>> from django.utils.functional import lazy
>>> from django.utils.safestring import mark_safe
>>> from django.utils.translation import ugettext_lazy as _
>>> mark_safe_lazy = lazy(mark_safe, six.text_type)
>>> lazy_string = mark_safe_lazy(_("My string!"))
>>> lazy_string

>>> from django.utils.translation import ugettext
>>> ugettext(lazy_string)
u'My string!'


>>> import django
>>> django.get_version()
'1.6.1'
>>> from django.utils import six  # Python 3 compatibility
>>> from django.utils.functional import lazy
>>> from django.utils.safestring import mark_safe
>>> from django.utils.translation import ugettext_lazy as _
>>> mark_safe_lazy = lazy(mark_safe, six.text_type)
>>> lazy_string = mark_safe_lazy(_("My string!"))
>>> lazy_string

>>> from django.utils.translation import ugettext
>>> ugettext(lazy_string)
Traceback (most recent call last):
  File "", line 1, in 
  File 
".../lib/python2.7/site-packages/django/utils/translation/__init__.py", 
line 76, in ugettext
return _trans.ugettext(message)
  File 
".../lib/python2.7/site-packages/django/utils/translation/trans_real.py", 
line 281, in ugettext
return do_translate(message, 'ugettext')
  File 
".../lib/python2.7/site-packages/django/utils/translation/trans_real.py", 
line 256, in do_translate
eol_message = message.replace(str('\r\n'), 
str('\n')).replace(str('\r'), str('\n'))
  File ".../lib/python2.7/site-packages/django/utils/functional.py", line 
129, in __wrapper__
raise TypeError("Lazy object returned unexpected type.")
TypeError: Lazy object returned unexpected type.


Any ideas as to whether it may be a bug, or whether I'm just doing it wrong 
and 1.6 has exposed that?

Cheers, Neal

-- 
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 email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/926b5932-245f-474d-ba11-9f6ed087f416%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

backends-mysql: cannot import name utils

[Miklos Smeja]

Dear all,

I've started using Django only a few months ago so I'm not an expert at all.
(But until now I could explain most of the problems what I had.. :))

Config: Raspbian, MySql, Django 1.6, Python 2.7.3 -- but most of the 
versions are in the attached stacktrace file.
Symptom: every 5th page refresh is generating this cannot import name utils 
error. Return page is of course a http 500 error.

How could I narrow this issue? Why is coming this error only sometimes?
Any ideas?

Many thanks!

BR,
 Miklos

-- 
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 email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/bca9a31d-a2d7-4d05-9cf2-c0aaaf223648%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Linux testpi 3.10.24+ #614 PREEMPT Thu Dec 19 20:38:42 GMT 2013 armv6l


[Sun Jan 19 06:25:18 2014] [error] python_init: Python version mismatch, 
expected '2.7.2+', found '2.7.3'.
[Sun Jan 19 06:25:18 2014] [error] python_init: Python executable found 
'/usr/bin/python'.
[Sun Jan 19 06:25:18 2014] [error] python_init: Python path being used 
'/usr/lib/python2.7/:/usr/lib/python2.7/plat-linux2:/usr/lib/python2.7/lib-tk:/usr/lib/python2.7/lib-old:/usr/lib/python2.7/lib-dynload'.
[Sun Jan 19 06:25:18 2014] [notice] mod_python: Creating 8 session mutexes 
based on 150 max processes and 0 max threads.
[Sun Jan 19 06:25:18 2014] [notice] mod_python: using mutex_directory /tmp
[Sun Jan 19 06:25:18 2014] [warn] mod_wsgi: Compiled for Python/2.7.2+.
[Sun Jan 19 06:25:18 2014] [warn] mod_wsgi: Runtime using Python/2.7.3.
[Sun Jan 19 06:25:18 2014] [notice] Apache/2.2.22 (Debian) PHP/5.4.4-14+deb7u7 
mod_python/3.3.1 Python/2.7.3 mod_wsgi/3.3 configured -- resuming normal 
operations
[Sun Jan 19 06:49:47 2014] [error] [client 86.59.144.19] mod_wsgi (pid=9470): 
Target WSGI script '/opt/homemonitor/homemonitor/wsgi.py' cannot be loaded as 
Python module.
[Sun Jan 19 06:49:47 2014] [error] [client 86.59.144.19] mod_wsgi (pid=9470): 
Exception occurred processing WSGI script 
'/opt/homemonitor/homemonitor/wsgi.py'.




[Fri Jan 24 18:31:01 2014] [error] [client 86.59.144.19]   File 
"/usr/local/lib/python2.7/dist-packages/django/utils/importlib.py", line 40, in 
import_module
[Fri Jan 24 18:31:01 2014] [error] [client 86.59.144.19] __import__(name)
[Fri Jan 24 18:31:01 2014] [error] [client 86.59.144.19]   File 
"/usr/local/lib/python2.7/dist-packages/django/db/backends/mysql/base.py", line 
39, in 
[Fri Jan 24 18:31:01 2014] [error] [client 86.59.144.19] from django.db 
import utils
[Fri Jan 24 18:31:01 2014] [error] [client 86.59.144.19] ImproperlyConfigured: 
Error importing module django.contrib.auth.middleware: "cannot import name 
utils"
[Fri Jan 24 18:31:02 2014] [error] [client 86.59.144.19] mod_wsgi (pid=9737): 
Exception occurred processing WSGI script 
'/opt/homemonitor/homemonitor/wsgi.py'.
[Fri Jan 24 18:31:02 2014] [error] [client 86.59.144.19] Traceback (most recent 
call last):
[Fri Jan 24 18:31:02 2014] [error] [client 86.59.144.19]   File 
"/usr/local/lib/python2.7/dist-packages/django/core/handlers/wsgi.py", line 
187, in __call__
[Fri Jan 24 18:31:02 2014] [error] [client 86.59.144.19] 
self.load_middleware()
[Fri Jan 24 18:31:02 2014] [error] [client 86.59.144.19]   File 
"/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 47, 
in load_middleware
[Fri Jan 24 18:31:02 2014] [error] [client 86.59.144.19] mw_class = 
import_by_path(middleware_path)
[Fri Jan 24 18:31:02 2014] [error] [client 86.59.144.19]   File 
"/usr/local/lib/python2.7/dist-packages/django/utils/module_loading.py", line 
26, in import_by_path
[Fri Jan 24 18:31:02 2014] [error] [client 86.59.144.19] sys.exc_info()[2])
[Fri Jan 24 18:31:02 2014] [error] [client 86.59.144.19]   File 
"/usr/local/lib/python2.7/dist-packages/django/utils/module_loading.py", line 
21, in import_by_path
[Fri Jan 24 18:31:02 2014] [error] [client 86.59.144.19] module = 
import_module(module_path)
[Fri Jan 24 18:31:02 2014] [error] [client 86.59.144.19]   File 
"/usr/local/lib/python2.7/dist-packages/django/utils/importlib.py", line 40, in 
import_module
[Fri Jan 24 18:31:02 2014] [error] [client 86.59.144.19] __import__(name)
[Fri Jan 24 18:31:02 2014] [error] [client 86.59.144.19]   File 
"/usr/local/lib/python2.7/dist-packages/django/contrib/auth/middleware.py", 
line 3, in 
[Fri Jan 24 18:31:02 2014] [error] [client 86.59.144.19] from 
django.contrib.auth.backends import RemoteUserBackend
[Fri Jan 24 18:31:02 2014] [error] [client 86.59.144.19]   File 
"/usr/local/lib/python2.7/dist-packages/django/contrib/auth/backends.py", line 
3,

Re: Using Natural Keys With dumpdata / loaddata

[Alex Thomas]

I tried adding unique=True to voyage_id but that did not have any effect.  
I later found somewhere in the docs that specifying in not necessary.  So I 
am still in the same situation. 

On Thursday, January 23, 2014 4:03:34 PM UTC-5, Alex Thomas wrote:
>
> I have already created a stackoverflow question on this and have only 
> received one (*incorrect*) response.  For the sake of time I am just 
> linking that question which has all the details.
>
>
> http://stackoverflow.com/questions/21151544/django-loaddata-with-natural-keys-not-querying-correct-forign-key
>
>
> -Alex
>

-- 
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 email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/af7f0eaa-725d-4825-9aaa-61c947bd33ea%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Using Natural Keys With dumpdata / loaddata

[Alex Thomas]

I tried adding unique=True to voyage_id but that did not have any effect.  
I later found somewhere in the docs that specifying is not necessary.  So I 
am still in the same situation. 

On Thursday, January 23, 2014 4:03:34 PM UTC-5, Alex Thomas wrote:
>
> I have already created a stackoverflow question on this and have only 
> received one (*incorrect*) response.  For the sake of time I am just 
> linking that question which has all the details.
>
>
> http://stackoverflow.com/questions/21151544/django-loaddata-with-natural-keys-not-querying-correct-forign-key
>
>
> -Alex
>

-- 
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 email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/aa2a7cac-d7fb-4855-a356-5731897dff24%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Using Natural Keys With dumpdata / loaddata

[Mike Dewhirst]

On 25/01/2014 7:31am, Alex Thomas wrote:

I tried adding unique=True to voyage_id but that did not have any
effect.  I later found somewhere in the docs that specifying is not
necessary.  So I am still in the same situation.


Is it possible to have unique=True together with null=True and blank=True???

In theory that is mutually incompatible. Two records with a blank 
voyage_id have the same voyage_id therefore voyage_id is not unique. I'm 
not sure but I have a feeling the ORM permits this for normal operations 
but it would probably break loaddata.




On Thursday, January 23, 2014 4:03:34 PM UTC-5, Alex Thomas wrote:

I have already created a stackoverflow question on this and have
only received one (*incorrect*) response.  For the sake of time I am
just linking that question which has all the details.


http://stackoverflow.com/questions/21151544/django-loaddata-with-natural-keys-not-querying-correct-forign-key




-Alex

--
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 email to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/aa2a7cac-d7fb-4855-a356-5731897dff24%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


--
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 email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/52E2EBC9.1060600%40dewhirst.com.au.
For more options, visit https://groups.google.com/groups/opt_out.

Honest feedback

[Bobby Roberts]

Hi group.  I've been out if the django world for over four years.  I am going 
to rebrand and replatform away from classic asp.   Don't laugh.  Yes I know 
it's sad.  Without telling me how good django is, what has changed in the last 
four year that should make me choose django as my new platform?  Are they still 
actively developing it ?  Just looking for honest feedback, not a sales pitch.  
 Thanks in advance 

-- 
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 email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/fdc1d112-a509-4996-93ee-d56a8c799d7f%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Honest feedback

[Alex Mandel]

On 01/24/2014 03:04 PM, Bobby Roberts wrote:
> Hi group.  I've been out if the django world for over four years.  I am going 
> to rebrand and replatform away from classic asp.   Don't laugh.  Yes I know 
> it's sad.  Without telling me how good django is, what has changed in the 
> last four year that should make me choose django as my new platform?  Are 
> they still actively developing it ?  Just looking for honest feedback, not a 
> sales pitch.   Thanks in advance 
> 

Have look over the release notes of major versions.
https://docs.djangoproject.com/en/dev/releases/

If you liked django before there's no reason to think you won't like it
now. There are all sorts of optional newer faster ways to get some
things done if you want to use them like the Class Based Views/Forms
auto generated from models (some people aren't fans but they can save
some major time).

Enjoy,
Alex

-- 
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 email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/52E2F3AB.1050306%40wildintellect.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Honest feedback

[Lachlan Musicman]

I would say it's very actively developed and supported.

In 2010 release 1.1 was the newest stable. Currently it's 1.6 with 1.7
due in 3-4 months. Wikipedia shows that in those years:

1.2 17 May 2010 Multiple db connections, CSRF, model validation
1.3 23 Mar 2011 Class based views, static files
1.4 23 Mar 2012 Timezones, in browser testing, app templates
1.5 26 Feb 2013 Python 3 Support, configurable user model
1.6 6 Nov 2013 Dedicated to Malcolm Tredinnick, db transaction
management, connection pooling


 - In the upcoming 1.7 release, migrations are moving into the
mainline (used to be an app called South)
 - the tutorial docs are still the premier example of how docs should
be done for new comers to software
 - the code itself is still very well documented in terms of APIs, the
IRC channel and this email list are both busy and helpful
 - almost every deprecated function happens because it's being
replaced with a super sized version of itself
 - community strong enough that the two BDFL have been able to step down

Check out the Two Scoops of Django too - a great follow up doc to the
tutorial, goes into a variety of best practices that have been
developed over the years.

L.



On 25 January 2014 10:04, Bobby Roberts  wrote:
> Hi group.  I've been out if the django world for over four years.  I am going 
> to rebrand and replatform away from classic asp.   Don't laugh.  Yes I know 
> it's sad.  Without telling me how good django is, what has changed in the 
> last four year that should make me choose django as my new platform?  Are 
> they still actively developing it ?  Just looking for honest feedback, not a 
> sales pitch.   Thanks in advance
>
> --
> 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 
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/fdc1d112-a509-4996-93ee-d56a8c799d7f%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.



-- 
>From this perspective it is natural that anarchism be marked by
spontaneity, differentiation, and experimentation that it be marked by
an expressed affinity with chaos, if chaos is understood to be what
lies outside or beyond the dominant game or system. Because of the
resistance to definition and categorisation, the anarchist principle
has been variously interpreted as, rather than an articulated
position, “a moral attitude, an emotional climate, or even a mood”.
This mood hangs in dramatic tension between utopian hope or dystopian
nihilism...
-
http://zuihitsu.org/godspeed-you-black-emperor-and-the-politics-of-chaos

-- 
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 email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAGBeqiMt1mfGEGbxEg0%2B6%2BW6mMBfkUZL0VuuYGB6-DDQFBX5qg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

throwing a 301

[Bobby Roberts]

i've got a site i'm porting from classic asp over to django.  Is there a 
way to nicely throw a 301 for the .asp pages?

-- 
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 email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/5d025669-08bc-4eaa-af00-0b3e63214fc3%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: throwing a 301

[Lachlan Musicman]

Docs:
https://docs.djangoproject.com/en/dev/ref/request-response/#django.http.HttpResponsePermanentRedirect

SO:
http://stackoverflow.com/questions/523356/python-django-page-redirect

On 25 January 2014 13:50, Bobby Roberts  wrote:
> i've got a site i'm porting from classic asp over to django.  Is there a way
> to nicely throw a 301 for the .asp pages?
>
> --
> 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
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/5d025669-08bc-4eaa-af00-0b3e63214fc3%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.



-- 
>From this perspective it is natural that anarchism be marked by
spontaneity, differentiation, and experimentation that it be marked by
an expressed affinity with chaos, if chaos is understood to be what
lies outside or beyond the dominant game or system. Because of the
resistance to definition and categorisation, the anarchist principle
has been variously interpreted as, rather than an articulated
position, “a moral attitude, an emotional climate, or even a mood”.
This mood hangs in dramatic tension between utopian hope or dystopian
nihilism...
-
http://zuihitsu.org/godspeed-you-black-emperor-and-the-politics-of-chaos

-- 
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 email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAGBeqiPCQEfHw%2Bfk_fQ8kp1Gb_oUOR1wg3zZWsvWS0kPG_6H1A%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.