Update (11/26/2013): I’m updating my recommendation. Since a sufficient amount of time has passed since I wrote this answer, I would recommend python-social-auth or django-allauth as the best tools for the job. They are active projects with good documentation and support for a lot more than just Facebook. I’ve had success using both. I have … Read more
Yes, you can do it simply in your apps.py file from your app folder change the verbose_name attribute from your config class. For example: from django.apps import AppConfig class FrontendConfig(AppConfig): name=”frontend” verbose_name = “Your Home Page” I test it and works in Django 1.10 UPDATE: In Django 3+ you should add this in your __init__.py … Read more
I’ll start this by saying we use none of these for object level permission – we use our own custom method and I really wish we hadn’t. If you can avoid object level permissions at all, do so, they are a pain to organise. This is how I evaluate the 3 apps you’ve mentioned. Active … Read more
A workaround that you can try is tweaking your models.py as follows: class Topping(models.Model): . . . class Meta: verbose_name_plural = “2. Toppings” class Pizza(models.Model): . . . class Meta: verbose_name_plural = “1. Pizzas” Not sure if it is against the django’s best practices but it works (tested with django trunk). Good luck! PS: sorry … Read more
Django < 1.7 has a handy management command that will give you the necessary SQL to drop all the tables for an app. See the sqlclear docs for more information. Basically, running ./manage.py sqlclear my_app_name gets you get the SQL statements that should be executed to get rid of all traces of the app in … Read more
The answer is yes. It’s perfectly okay for one application inside your django project to import models from another application. The power of a django project lies in the apps and their interactions. Also make sure that you have utility applications importing models from more generic applications and not the other way. So “userstatistics” app … Read more
You just need to make sure your structure makes sense to you. There’s no requirement to create a new app for every feature that is bound to another part of the project’s logic. Reusable apps are a whole different story, their code should be unaware of the implementation to some extent. Take a look at … Read more
You can add your apps folder to your python path by inserting the following in your settings.py: import os import sys PROJECT_ROOT = os.path.dirname(__file__) sys.path.insert(0, os.path.join(PROJECT_ROOT, ‘apps’)) Then you can use all the apps in this folder just in the same way as they were in your project root!
The problem reported can be because you skipped registering the models for the admin site. This can be done, creating an admin.py file under your app, and there registering the models with: from django.contrib import admin from .models import MyModel admin.site.register(MyModel)
They must be valid package names. That rules out 2 (“import my-django-app” would be a syntax error). PEP 8 says: Modules should have short, all-lowercase names. Underscores can be used in the module name if it improves readability. Python packages should also have short, all-lowercase names, although the use of underscores is discouraged. So, 1 … Read more