Re: what are the files goes inside "contrib" folder?

[James Turley]

The short answer is: it depends what OS you're on, and where your Django
package is installed.

On Unix-like systems, it'll be somewhere like
lib/python2.7/site-packages/django/contrib/ (substitute your python
version, obviously). But what goes before 'lib' depends on where your
Python libraries in general are installed, which would vary from OS to OS;
if you're using virtualenv, it'll be the root directory for the environment
you're working on, etc.

You shouldn't need to change anything in there, however. What leads you to
look for it? If you just want to browse the code, then I'd recommend
looking through it at github:
https://github.com/django/django/tree/master/django or else cloning the
relevant branch from there.




On Fri, Feb 7, 2014 at 11:33 AM, Giri  wrote:

> Can someone tell me what are the files goes inside "contrib" folder?
>
> If possible give me a webpage link that explains django's folder
> structure..
>
> --
> 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/73852141-a06f-4293-bca3-ec61b434cc7c%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%3DzLsd5cxxznswpvNqW4Oywu-aB3OMUXQK%3D8A7XGV7WuAQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Do you think Django's future is threatened by JS frameworks in both client & server?

[James Turley]

I'm not sure I buy this stuff about JS taking over everything. The reason
is that client and server are different domains, and we might reasonably
expect - even in a pure JS-only shop - people to specialise anyway. Apart
from the tiniest start-ups, there isn't really an evolutionary advantage to
having the same language on both ends. Rather than people who know x
language, you primarily want people with familiarity with the
domain-specific problems.

It's worth noting that the JS hype is not the only thing at the moment:
among functional programming evangelists, there is a sense that "their time
has come" after years on the CS-boffin fringe. The theory goes like this -
nowadays, major web apps are deployed on enormous server clusters,
sometimes with enormous numbers of virtual or real CPU cores, database
sharding and so forth. The key problems facing server-side dev work - at
least at the top end of the web - have to do with handling all this,
parallelism, async, race conditions and so forth. A relatively 'pure' FP
language like Haskell, with its divine commandments against mutable state
and focus on pure functions, has a headstart on OOP languages like Python &
Ruby in this domain.

JS is *sort of *an FP language, and can be used to write pure code, but has
hitherto been used almost exclusively as a simple interface to that great
clump of mutable global state called the DOM; it certainly does not enforce
good FP practices or anything like that. The Node model of event-driven IO
is obviously directed at this group of problems, but it's very much a work
in progress, despite all the hype. (This is also a problem I have with
client-side MV* frameworks, BTW: I'm promised that picking up Ember is a
breeze, but major parts of the API change so frequently that it gives me
actual nightmares.)

Meanwhile, we've got the Async IO library coming in Python 3.4; and, as
others have pointed out, a headstart on big data crunching thanks to
Python's excellent math/science ecosystem. I'm sure the Ruby people have
tricks up their sleeve. And there's Go. And Scala. And Clojure. And ...

The point is: there's an enormous explosion of new tools around, plus
serious improvements in old favourites. Devs who know what's good for them
will use the correct tool for the job at hand; the cognitive convenience of
working in one language only is a part of that decision, but only a part.


On Tue, Jan 28, 2014 at 4:27 PM, Cal Leeming [Simplicity Media Ltd] <
cal.leem...@simplicitymedialtd.co.uk> wrote:

> It makes for an interesting debate and food for thought.
>
> Python has a lot of libraries and user contributions which can speed up
> development, but like every language, has it's good sides and bad sides.
>
> Django holds a strong position, libraries such as south, pipeline,
> mongoengine, uWSGI and the Django ORM itself make it incredibly easy to get
> clean code quickly out the door.
>
> Personally I think the biggest risk to Django's future is lack of public
> contributions (separate debate), and evolution being held back for
> backwards compatibility reasons (again, separate debate), rather than any
> threat from new kids on the block. I would be quite surprised if NodeJS (as
> an example) overtook Django in terms of functionality and popularity.
>
> Disclaimer: I'm +1 python and -0 JS, and thus slightly biased.
>
> Cal
>
>
>
>
>
> On Mon, Jan 27, 2014 at 10:44 PM,  wrote:
>
>> Hi,
>>
>> I would like to know if this community is somewhat worried about the
>> future relevance of Django (and other purely server-side MV* Python web
>> app frameworks such as web2py for that matter) given the current momentum
>> of JavaScript (JS) everywhere?
>>
>> There are many competing architecture patterns for a WHOLE web app today
>> ranging:
>> a)  from client-heavy SPA with a client-side MVC framework synching its
>> models via a REST API with a server-side reduced to a database access layer
>>
>> b) to light client apps with a server-side MVC frameworks and very
>> little or no Ajax
>>
>> c) and everything in the middle.
>>
>> I guess it is not too controversial to say that which is best (or even
>> merely adequate) depends on the generally moving target of the app
>> requirements (especially the non-functional ones) and thus a long
>> lifecycle app can be expected to have to change pattern at some point.
>>
>>
>> Given that:
>> 1) full web apps following any pattern can today be developed exclusively
>> with JavaScript (JS) frameworks on both sides who have incorporated most
>> (if not all) great design ideas from Django (and Rails)
>>
>> 2) IDEs ranging from Visual Studio to browser-based ones are available
>> to support such development
>>
>> 3) Python in the browser projects do not yet provide productive debugging
>> support (and will they ever without support from a tech giant?)
>>
>> 4) Cloud giants (Amazon, Google, Heroku, Microsoft) all offering JS framework
>> running servers
>>
>> are the productivity gains 

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.

Re: Deploying to Heroku for first time, Dynos is blank, not recognizing Procfile

[James Turley]

Do you have a requirements.txt file (with all your requirements therein)?
Heroku recognises python apps by its presence (although I'm told this is
not yet 100% reliable - never tried myself).


On Tue, Jan 7, 2014 at 9:55 AM, Vibhu Rishi  wrote:

> yes. just create a text file with no extension. Here's mine for reference
> :
>
> $ cat Procfile
> web: gunicorn qj.wsgi
>
>
> V.
>
>
> On Tue, Jan 7, 2014 at 9:31 AM, Scott Meyers wrote:
>
>> Programming newb, Trying to use Heroku for the first time for a Django
>> app. After I push it to Heroku, the Dynos field is blank. I expected to see
>> my procfile: web: python manage.py runserver 0.0.0.0:$PORT --noreload
>>
>> Of course, when I try to open the application on Heroku, I get: An error
>> occurred in the application and your page could not be served. Please try
>> again in a few moments.
>>
>> If you are the application owner, check your logs for details
>>
>> Could this be because I don't have an extension on my procfile?
>>
>> My Procfile should just be a file I created in my text editor, right?
>>
>> Here is the log:
>>
>> 2014-01-06T07:34:17.321925+00:00 heroku[router]: at=error code=H14
>> desc="No web processes running" method=GET path=/ host=
>> aqueous-dawn-4712.herokuapp.com fwd="98.232.45.58" dyno= connect=
>> service= status=503 bytes=
>>
>> 2014-01-06T07:34:17.778360+00:00 heroku[router]: at=error code=H14
>> desc="No web processes running" method=GET path=/favicon.ico host=
>> aqueous-dawn-4712.herokuapp.com fwd="98.232.45.58" dyno= connect=
>> service= status=503 bytes=
>>
>> 2014-01-06T07:35:01.608749+00:00 heroku[router]: at=error code=H14
>> desc="No web processes running" method=GET path=/ host=
>> aqueous-dawn-4712.herokuapp.com fwd="98.232.45.58" dyno= connect=
>> service= status=503 bytes=
>>
>> 2014-01-06T07:35:01.868486+00:00 heroku[router]: at=error code=H14
>> desc="No web processes running" method=GET path=/favicon.ico host=
>> aqueous-dawn-4712.herokuapp.com fwd="98.232.45.58" dyno= connect=
>> service= status=503 bytes=
>>
>> 2014-01-06T07:46:57.862560+00:00 heroku[router]: at=error code=H14
>> desc="No web processes running" method=GET path=/ host=
>> aqueous-dawn-4712.herokuapp.com fwd="98.232.45.58" dyno= connect=
>> service= status=503 bytes=
>>
>> 2014-01-06T07:46:58.114270+00:00 heroku[router]: at=error code=H14
>> desc="No web processes running" method=GET path=/favicon.ico host=
>> aqueous-dawn-4712.herokuapp.com fwd="98.232.45.58" dyno= connect=
>> service= status=503 bytes=
>>
>> --
>> 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/293796b7-2700-4c95-ac02-25c512ea41b0%40googlegroups.com
>> .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> --
> Simplicity is the ultimate sophistication. - Leonardo da Vinci
> Life is really simple, but we insist on making it complicated. - Confucius
>
> --
> 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/CAPiONwkA87ecejWXLMrvjUgmTE8z3pbZ%2B1N1t%3DyPJ85xYyb2DQ%40mail.gmail.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%3DwJczRTTP1ejYs0jO3VFEUViM4WvHO44JGC4%2BHUyMFApQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: 'python manage.py migrate' command gives error even after installing south

[James Turley]

line 5, models.py - you've capitalised Class. It should just be 'class',
all lower case.

JT


On Fri, Nov 22, 2013 at 4:41 AM, puneet pandey wrote:

> I was going through Django tutorials and found the command - 'python
> manage.py migrate' to give output as 'unknown command' . So i searched for
> it and found that its most probably due to 'south' not installed. i checked
> it on python shell by giving the command - 'import south' which resulted in
> 'unknown module'. So I installed south first by using easy_install and then
> by apt-get and then updated the system. I also went to settings.py and
> added south in the installed_apps section.
>
> Now when I ran 'python manage.py migrate' command there was an error -
> pasting it here -
>
> popo@popo-HP-TouchSmart-tm2-Notebook-PC:~/Django_apps/mysite$ python
> manage.py migrate
> Traceback (most recent call last):
>   File "manage.py", line 10, in 
> execute_from_command_line(sys.argv)
>   File
> "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py",
> line 399, in execute_from_command_line
> utility.execute()
>   File
> "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py",
> line 392, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File
> "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py",
> line 242, in run_from_argv
> self.execute(*args, **options.__dict__)
>   File
> "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py",
> line 284, in execute
> self.validate()
>   File
> "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py",
> line 310, in validate
> num_errors = get_validation_errors(s, app)
>   File
> "/usr/local/lib/python2.7/dist-packages/django/core/management/validation.py",
> line 34, in get_validation_errors
> for (app_name, error) in get_app_errors().items():
>   File
> "/usr/local/lib/python2.7/dist-packages/django/db/models/loading.py", line
> 196, in get_app_errors
> self._populate()
>   File
> "/usr/local/lib/python2.7/dist-packages/django/db/models/loading.py", line
> 75, in _populate
> self.load_app(app_name, True)
>   File
> "/usr/local/lib/python2.7/dist-packages/django/db/models/loading.py", line
> 99, in load_app
> models = import_module('%s.models' % app_name)
>   File "/usr/local/lib/python2.7/dist-packages/django/utils/importlib.py",
> line 40, in import_module
> __import__(name)
>   File "/home/popo/Django_apps/mysite/polls/models.py", line 5
> Class Question(models.Model):
>  ^
> SyntaxError: invalid syntax
>
>
>
>
>
>
>
>
>
>
> what can i do to solve this issue.
> Thanks a lot everyone for reading this and helping me 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/ae647a5a-bea1-4c89-9816-4162ddb9809e%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%3DyfunZLSuUjNYzs2X_he%2BdfpLn6r9U1DPKuEx%2B%3D5%3D_wMA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How do I use mathematical calculations on my forloop Article/Publication list?

[James Turley]

On number 3, annotate returns the annotated queryset, not the particular
result of the annotation. The annotation is added to each individual object
in the set.

Turning that into an integer doesn't make sense, because num_publications
is a property of *each individual *entry in the set, not the set itself.

articles[0].num_publications() would return the number of publications
associated with the first article in the set, for example.

James


On Wed, Nov 20, 2013 at 9:29 PM, Pepsodent Cola wrote:

> 1.)
> How do I use mathematical calculations on my forloop Article/Publication
> list?
>
> * I have attached a screenshot with the table field that I'm working on 
> *"Publicists
> coverage (%)"*.
> * Admin user/pass = joe/joe
> * I have also attached my project files so that you can see things for
> yourselves.
>
>
> 2.)
> Is the solution I'm working with in "Index View page" the correct practice
> to do my mathematical calculations?
>
>
> #___
>
> def index(request):
> publications = Publication.objects.all()
>
>
> # sum_publications = Publication.objects.filter(article__pk=1).count()
> articles =
> Article.objects.all().annotate(num_publications=Count('publications'))
> *#articles_int = int(articles)*
>
> *sum_publicists = Publication.objects.all().count()*
>
> *#publicists_coverage = articles/sum_publicists*
>
>
> #context = {'publications':publications,
> 'sum_publicists':sum_publicists,
> #   'publicists_coverage':publicists_coverage,
> 'articles':articles}
> context = {'publications':publications,
> 'sum_publicists':sum_publicists,
>'articles':articles}
> return render(request, 'magazine/index.html', context)
>
> #___
>
> 
> How many Publications was each Article in?
>
> {% if articles %}
> 
> 
> Article id
> Article
> Publication
> *Publicists coverage (%)*
> 
> {% for row in articles %}
> 
> {{ row.id }}
> {{ row.headline }}
> {{ row.num_publications }}
> (*{{ row.num_publications }} / {{ sum_publicists }}*) = x
> %
> 
> {% endfor %}
> 
> {% else %}
> No Articles are available.
> {% endif %}
>
> 
> 
>
>
> #___
>
>
> 3.)
> When I try to convert articles object into int it doesn't work.  Am I
> going the wrong direction when thinking about solving things like this?
>
>
> Exception Type: TypeError
> Exception Value: *int() argument must be a string or a number, not
> 'QuerySet'*
> Exception Location: /home/linux/Django/ManyToMany/magazine/views.py in
> index, line 17
>
>
> >>> articles =
> Article.objects.all().annotate(num_publications=Count('publications'))
> >>> type(articles)
> 
> >>>
> >>> *articles_int = int(articles)*
> Traceback (most recent call last):
>   File "", line 1, in 
> TypeError: int() argument must be a string or a number, not 'QuerySet'
> >>>
>
>
>
>
>
>
>  --
> 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/eaa87962-c182-4261-8668-69285dde8de3%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%3DyEebUmaMRZRaFNSd-4yn-vJAx-y3eb08UTk0-23oT6TQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: 'NoneType' object has no attribute '__getitem__' Please help me to debug this

[James Turley]

Hi Ham, I was following your thread on the LinkedIn django group and it
looked there like you had a couple of simple typos in your CatalogCategory
model's __unicode__ method. Did you get round to fixing those?

JT


On Wed, Nov 6, 2013 at 11:46 AM, Ham Kibz  wrote:

> Below is the traceback
>
> Django Version: 1.5.1
> Python Version: 2.7.4
> Installed Applications:
> ('django.contrib.auth',
>  'django.contrib.contenttypes',
>  'django.contrib.sessions',
>  'django.contrib.sites',
>  'django.contrib.messages',
>  'django.contrib.staticfiles',
>  'django.contrib.admin',
>  'products')
> Installed Middleware:
> ('django.middleware.common.CommonMiddleware',
>  'django.contrib.sessions.middleware.SessionMiddleware',
>  'django.middleware.csrf.CsrfViewMiddleware',
>  'django.contrib.auth.middleware.AuthenticationMiddleware',
>  'django.contrib.messages.middleware.MessageMiddleware')
>
>
> Traceback:
> File
> "/home/kelcy/django1.5.1/local/lib/python2.7/site-packages/django/core/handlers/base.py"
> in get_response
>   115. response = callback(request,
> *callback_args, **callback_kwargs)
> File
> "/home/kelcy/django1.5.1/local/lib/python2.7/site-packages/django/contrib/admin/options.py"
> in wrapper
>   372. return self.admin_site.admin_view(view)(*args,
> **kwargs)
> File
> "/home/kelcy/django1.5.1/local/lib/python2.7/site-packages/django/utils/decorators.py"
> in _wrapped_view
>   91. response = view_func(request, *args, **kwargs)
> File
> "/home/kelcy/django1.5.1/local/lib/python2.7/site-packages/django/views/decorators/cache.py"
> in _wrapped_view_func
>   89. response = view_func(request, *args, **kwargs)
> File
> "/home/kelcy/django1.5.1/local/lib/python2.7/site-packages/django/contrib/admin/sites.py"
> in inner
>   202. return view(request, *args, **kwargs)
> File
> "/home/kelcy/django1.5.1/local/lib/python2.7/site-packages/django/utils/decorators.py"
> in _wrapper
>   25. return bound_func(*args, **kwargs)
> File
> "/home/kelcy/django1.5.1/local/lib/python2.7/site-packages/django/utils/decorators.py"
> in _wrapped_view
>   91. response = view_func(request, *args, **kwargs)
> File
> "/home/kelcy/django1.5.1/local/lib/python2.7/site-packages/django/utils/decorators.py"
> in bound_func
>   21. return func(self, *args2, **kwargs2)
> File
> "/home/kelcy/django1.5.1/local/lib/python2.7/site-packages/django/db/transaction.py"
> in inner
>   223. return func(*args, **kwargs)
> File
> "/home/kelcy/django1.5.1/local/lib/python2.7/site-packages/django/contrib/admin/options.py"
> in add_view
>   1009. self.log_addition(request, new_object)
> File
> "/home/kelcy/django1.5.1/local/lib/python2.7/site-packages/django/contrib/admin/options.py"
> in log_addition
>   530. action_flag = ADDITION
> File
> "/home/kelcy/django1.5.1/local/lib/python2.7/site-packages/django/contrib/admin/models.py"
> in log_action
>   18. e = self.model(None, None, user_id, content_type_id,
> smart_text(object_id), object_repr[:200], action_flag, change_message)
>
> Exception Type: TypeError at /admin/products/catalogcategory/add/
> Exception Value: 'NoneType' object has no attribute '__getitem__'
>
>  --
> 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/1798ea05-5f4e-4e9d-aebf-0227a840e0c8%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%3Dws_3A-x27kO7Dz0q-Pe6%3DpAUUM0yKGhNXZSDcZOf09dA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Seeking reviewers for a "Guide to Idiomatic Django Deployment"

[James Turley]

Hi George,

As a fellow relative n00b to Django (and 'serious' web development), I
think this is a very good idea. I'm working through Harry Percival's
excellent book, and only got hopelessly lost during the deployment
chapter(admittedly,
I was attempting to deploy to 'production' through my
development machine - an effort which succeeded principally in FUBARing my
Apache settings for about a week, and possibly sucking knowledge of unix
sockets etc *out of* my brain. Lessons have been learned).

More broadly, one of the first major brain-teasers for PHP refugees
(*cough*) coming to Django or Rails or whatever is the loss of that "open
filezilla, upload folder, done" deployment workflow.

Obviously I'm not the person to help you with this, however. :-)

JT


On Wed, Nov 6, 2013 at 2:07 AM, Vijay Khemlani  wrote:

> Wouldn't it be better to publish the book the same way as the Django Book (
> http://www.djangobook.com/, https://github.com/jacobian/djangobook.com)
> instead of looking for private reviewers?
>
>
> On Tue, Nov 5, 2013 at 9:34 PM, George London 
> wrote:
>
>> Hi All!
>>
>> As a fairly recently self-taught Djangonaut, I was a bit dissatisfied
>> with the existing resources for learning to deploy Django in a production
>> setting. There are lots of blog posts about how to configure specific
>> services but really not much that recommends which services to use or how
>> to bring everything together (except for guides like
>> http://www.deploydjango.com/ that recommend just using Heroku.)
>>
>> I think it would be really helpful for new-comers to have a clear,
>> opinionated guide to "commonly accepted (i.e. idiomatic)" deployment best
>> practices. Or at least I know it would have really helped me.
>>
>> So I decided to write such a guide. I'm painfully aware that it's
>> presumptuous for someone with my limited experience to make "best
>> practices" recommendations. So to avoid recommending things that are dumb,*
>> I'm hoping some of our community's heavy weights could heavy-weigh in and
>> verify that my recommendations make sense.*
>>
>> I've got a full draft prepared. *If you'd be interested in reviewing it
>> (or can recommend someone I should ask directly), please email me directly.*
>>
>> -George
>>
>>
>> --
>> ---
>> George London
>> E: george.j.lon...@gmail.com
>> T: @rogueleaderr 
>> B: rogueleaderr.com
>> ---
>>
>> --
>> 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/de9ba225-0ce4-4888-b121-986762c63f39%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/CALn3ei0wtHEODfTU8Qif-688A%3DZXW%3DaJYqeoxyAOKHLxh%2BRSSg%40mail.gmail.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%3Dy8zcrg%2B9mjF1Yrq_WYAuHpJWAwSqhEsBKPCZ_J7PUSXw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.