Re: Loading CSS
Well - that's one way A simpler way is to use your settings.py file to point to your media, and remove all reference to .css from your url.py files ... # Absolute path to the directory that holds media. # Example: "/home/media/media.lawrence.com/" MEDIA_ROOT = '/path_to_media_root/static_media/' # URL that handles the media served from MEDIA_ROOT. Make sure to use a # trailing slash if there is a path component (optional in other cases). # Examples: "http://media.lawrence.com;, "http://example.com/media/; MEDIA_URL = '/static_media/' ... -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
Re: Pydoc and security
Thanks, I've just added the following line near the start of my settings file ... __all__ = ['INSTALLED_APPS'] ... that looks much better On Nov 21, 8:24 pm, Masklinn <maskl...@masklinn.net> wrote: > On 2010-11-21, at 21:19 , Robert S wrote: > > > I'm not! > > Pydoc is picking up any variables that are not hidden in classes of > > functions. > > > Is there a command to (selectivly) stop this? > > PyDoc respects __all__. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
Re: Pydoc and security
I'm not! Pydoc is picking up any variables that are not hidden in classes of functions. Is there a command to (selectivly) stop this? On Nov 21, 11:35 am, Łukasz Rekucki <lreku...@gmail.com> wrote: > On 20 November 2010 23:31, Robert S <rob...@robert-stuart.me.uk> wrote: > > > Hi > > I'm trying generate documentation for a django project. > > > The obvious tool is pydoc, which does work. The trouble is, pydoc > > publishes everything ... including passwords. > > Why would you put any passwords in docstrings ? > > -- > Łukasz Rekucki -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
Pydoc and security
Hi I'm trying generate documentation for a django project. The obvious tool is pydoc, which does work. The trouble is, pydoc publishes everything ... including passwords. Is there a simply way of controlling the output from pydoc? TIA -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
Re: How crypt python code
You could try uploading your .pyc files, without your .py source. That will be something of a maintenance night-mare, but should work -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
Re: multidb - partitioning
Hello, I'm new to django, so bear with me if this is a silly approach but, could you assign the project name to db_table at run time? Something like ... models.py ... # app_name and project_code may need to be declared with global scope ... APP_NAME = 'app_name' # might be optional global project_code = get_project_code(...) def set_project_code(my_project_code): project_code = my_project_code class Measurand(models.Model): project = models.ForeignKey(Project) # project is implied by table name context, so may be unnecessary here? avg_value = models.DecimalField(max_digits=10, decimal_places=4, db_index=True) class Meta: db_table = u'%s_%s_measurand'%( app_name, project_code ) # app_name is usual django behaviour, but may not be necessary if you are certain no other apps will conflict with the table name # another approach would be ... # db_table = u'%s_measurand'%( project_code ) ... Obviously, before you build project tables, you'd need to call et_project_code HTH -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
