Project Setup Checklist. Found this helpful...

[Aaron Harris]

Just curious how your project setup compares here and other resources you 
might suggest. Thanks!!

*Easily Install Django: A Quick Guide*

*Installation*
Assuming you have Python setup with pip – installation is simple. This will 
install Django along with a useful command that will help you get a project 
started quickly.

pip install django
The following command creates the project directory foo/ and creates a 
basic project structure and some initial files.

django-admin startproject foo
Let’s quickly go over each file we created:

Manage.py is the command-line utility that Django provides. It comes with a 
number of commands that are supported out of the box, some of which we’ll 
see later. Some Django applications that you may install later on will add 
commands accessible through this utility, and ultimately you’ll be able to 
add your own as needed.

foo/settings.py is n initial example of a Django settings file that should 
contain all the configuration for your application. If you take a look, you 
will see the default values that set your application up for running in a 
local development environment.

foo/urls.py is the default location for your URL configuration. Essentially 
this provides Django with the rules of how to route requests your 
application receives.

foo/wsgi.py is where the actual WSGI application lives. When running Django 
in production, you’ll want to use a server like uwsgi or green unicorn, 
whose servers interface with the application that resides in this file.

Now that we’ve created the project, let’s take it for a spin. To run the 
built-in development server, run:

./manage.py runserver
You should see some output indicating the settings used and where the 
server is available. Note that by default, it makes the server available at 
http://127.0.0.1:8000. If you go to that address, a default page will load, 
letting you know that you have successfully installed Django. As the page 
indicates, the only reason you’re seeing that page is because the default 
configuration provided in the settings.py file has DEBUG = True. Otherwise, 
trying to reach that page would give you a 404 as your URL configuration in 
urls.py doesn’t route that path to anything within your application.

‍
It's not that long but a bit too much for this post*. The rest is here 
:*

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/eef47143-bcf3-4f3d-8642-af8e04eee408%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Django reusable apps checklist

[Filipe Ximenes]

Hi everyone,

yesterday Flávio <https://twitter.com/flaviojuvenal> gave a talk about 
"Qualities of great reusable Django apps" at DjangoCon Europe. We put 
together most of his ideas from the talk and published as a hot site:

http://djangoappschecklist.com/

The code is open source and we would love to get feedbacks on improvements 
as well as new additions. Just open an issue to contribute: 
https://github.com/vintasoftware/django-apps-checklist

If you want to see the full talk, it's already available at: 
https://www.youtube.com/watch?v=NVVABF4Yj-U=youtu.be=32145

Best,
Filipe

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/d2aacb6d-90ed-4391-a371-6de386489133%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Checklist for appreciating a project from 1.2.7 to 1.4a1

[akaariai]

On Feb 4, 9:09 am, Alec Taylor <alec.tayl...@gmail.com> wrote:
> Good afternoon,
>
> I'm bringing the "social-commerce" project up to the latest trunk of
> Pinax and Django.
>
> Is there a checklist of things I'll need to update?
>
> I've begun updating it, i.e. adding the new database dictionary:
> DATABASES = {
>     'default': {
>         'ENGINE': 'django.db.backends.mysql',
>         'OPTIONS': {
>             'read_default_file': '/path/to/my.cnf',
>         },
>     }
>
> }
>
> But it keeps giving me error after error once I've done that, so
> instead of tackling issues one at a time, I thought their might be a
> guide of some sort?
>
> Thanks for all suggestions,

The best guide is checking the release notes of 1.3 and 1.4. They
should contain all the deprecated and backwards incompatible changes.
Missing or hard to understand parts of the release notes are valuable
knowledge to Django's developers, so please inform about those if you
see something.

You should also run your code with full warnings under 1.2. If you
don't get any warnings about deprecation under 1.2, in principle you
should be able to just update to 1.4.

 - Anssi

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Checklist for appreciating a project from 1.2.7 to 1.4a1

[Alec Taylor]

Good afternoon,

I'm bringing the "social-commerce" project up to the latest trunk of
Pinax and Django.

Is there a checklist of things I'll need to update?

I've begun updating it, i.e. adding the new database dictionary:
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.mysql',
'OPTIONS': {
'read_default_file': '/path/to/my.cnf',
},
}
}

But it keeps giving me error after error once I've done that, so
instead of tackling issues one at a time, I thought their might be a
guide of some sort?

Thanks for all suggestions,

Alec Taylor

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

checklist

[Jiri Barton]

Hello there,

I want to display a checklist dynamically:

1 apple [ ]
3 pears [ ]
8 plums [ ]

([ ] stands for checkboxes)

The items are generated on the fly. I can create the form fields in a
manipulator __init__ dynamically, such as in:

for item in items:
self.fields.append(CheckboxField(fieldname="%s-%s" % (item.name,
item.number)))

Then, in the template:

{% for row in form %}
{{ row }}
{% endfor %}

This does not work because ``form`` is not a a list. How could I solve
this?

Then, I need to be able to display the labels next to the checkboxes.
But I cannot include them in self.fields because they are just texts.
How can I do it? I mean, do I need to create my own LabelField?

Thank you in advance.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---