Tim and Scott, thank you very much!
On Jun 9, 10:03 pm, Tim Chase <[EMAIL PROTECTED]> wrote:
> >> I think this way, apache could be a little more faster. Am I
> >> right?
>
> > I don't think it will be faster. Django normally runs as a
> > long-standing process (either inside Apache or as a standalone
> > process, depending on the deployment model you've chosen).
> > So, unlike ordinary CGI scripts, your Python bytecode will not
> > need to be generated except for the very first time that your
> > code is loaded. Once it's up and running it will already be
> > in memory so it won't need to be reinterpreted.
>
> If you want, you can pre-compile everything as described at
>
> http://effbot.org/pyfaq/how-do-i-create-a-pyc-file.htm
>
> which shows you can issue
>
> bash$ cd ~/code
> bash$ python -m compileall .
> [output]
>
> which will compile each .py file into a corresponding .pycfile
> within the current directory and subdirectories. I believe the
> Debian variants (others may as well) do this in the system
> directories upon installation so users don't have to recompile
> all the system libraries.
>
> The time saved is minimal, but there's no harm in preemptively
> compiling your files.
>
> -tim
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
