On Sun, 2 Jun 2013 13:51:26 -0700 (PDT)
"William T. Schultz" wrote:
> Hello,
>
> I have been going through the Django first app tutorial with success
> until I received the message, "File
> "/Users/williamtschultz/mysite/mysite/settings.py"
Hello,
I have been going through the Django first app tutorial with success until
I received the message, "File
"/Users/williamtschultz/mysite/mysite/settings.py", line 104 ROOT_URLCONF =
'mysite.urls' : SyntaxError: invalid syntax" in Terminal after I enter
&qu
On Monday, March 18, 2013 6:17:26 PM UTC+5:30, Tom Evans wrote:
>
> Hi Navid
>
> Can you show the structure of your project, where it is on disk and so
> on. I suspect that in mysite.wsgi, you are inserting the wrong paths
> into sys.path, and then Django cannot find your correct settings.
>
On Sunday, March 17, 2013 7:49:31 PM UTC+5:30, JirkaV wrote:
>
> I'd look at how you reference your settings during imports. The error
> message spells "Settings" with uppercase "S" which feels incorrect.
>
> Hi Jirka,
I appreciate your response.
This is default behavior (I am not sure whether t
On Sun, Mar 17, 2013 at 9:20 AM, Navid Shaikh wrote:
> Hi folks,
>
> (Before posting I searched in archive and the question is kind of similar to
> thread [1].)
>
> I am getting error:
> AttributeError: 'Settings' object has no attribute 'ROOT_URLCONF'
29
To:
Reply-To: django-users@googlegroups.com
Subject: Settings object has no attribute 'ROOT_URLCONF' while deploying
using apache and mod_wsgi
Hi folks,
(Before posting I searched in archive and the question is kind of similar
to thread [1].)
I am getting error:
AttributeError:
Hi folks,
(Before posting I searched in archive and the question is kind of similar
to thread [1].)
I am getting error:
AttributeError: 'Settings' object has no attribute 'ROOT_URLCONF'
I am using
a) Django version 1.3.2.
b) Apache
c) mod_wsgi
I followed standar
..
Am Samstag, 19. Mai 2012 07:52:58 UTC+2 schrieb doniyor:
>
> Hi
>
> i have this problem, i dont why, i have root_urlconf in my settings.py. i
> cannot figure out what it wants from me.. pls help
>
>
>
--
You received this message because you are subscribed to th
Hi
i have this problem, i dont why, i have root_urlconf in my settings.py. i
cannot figure out what it wants from me.. pls help
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web vi
I'm not really a pro with the who path stuff but this is how I see it.
ROOT_URLCONF = 'projectname.urls'
In my project I can import projectname and projectname.urls.
generally all django project have a __init__.py file which makes it a
module, so in your case soco-site should be
py
If I have in that settings file:
ROOT_URLCONF = 'soco-site.urls'
and start up my server from the soco-site directory, it finds the urls
file. How? If I print out sys.path from inside settings.py, it
includes /Users/roy/S7/soco/soco-site, but not /Users/roy/S7/soco.
Even stranger, &q
In short, it has to be on your PYTHONPATH or in the local directory.
If you're importing from the local directory it always works (assuming
the subdirectory contains a file named __init__.py). The other path,
'foo.urls' works because 'foo' is in your PYTHONPATH.
Do whatever makes sense to you and
On Apr 3, 2:55 pm, andy wrote:
> Well I'm guess you don't have to. Both ROOT_URLCONF = "foo.urls" and
> ROOT_URLCONF = "urls" seem to work fine.
Interesting, I just tried it that way, and sure enough it does work.
I had simply been following the exampl
Well I'm guess you don't have to. Both ROOT_URLCONF = "foo.urls" and
ROOT_URLCONF = "urls" seem to work fine.
On Apr 3, 8:11 am, Roy Smith wrote:
> I don't understand how ROOT_URLCONF is declared in settings.py. If I
> put all my apps (and my se
I don't understand how ROOT_URLCONF is declared in settings.py. If I
put all my apps (and my settings.py file) in a directory "foo", I'm
supposed to do:
ROOT_URLCONF = "foo.urls"
This seems counter-intuitive to me. When I run my app (by running
"python manage
dick...@gmail.com wrote:
> was looking for some info on how ROOT_URLCONF setting is supposed to
> be used? i am trying something very simple. i have a single django
> project. there are two apps.
>
> i want to run one app, call it foo, with a specific settings file,
> and se
On Dec 31, 12:31 pm, "dick...@gmail.com" wrote:
> was looking for some info on how ROOT_URLCONF setting is supposed to
> be used? i am trying something very simple. i have a single django
> project. there are two apps.
>
> i want to run one app, call it foo, with a spec
was looking for some info on how ROOT_URLCONF setting is supposed to
be used? i am trying something very simple. i have a single django
project. there are two apps.
i want to run one app, call it foo, with a specific settings file,
and set of urls, and bar with something else.
so, with a
On 7/2/07, Graham Dumpleton <[EMAIL PROTECTED]> wrote:
> What is the initial memory size of the process when it is first
> started? In other words, does it start out this large or grow over
> time?
>
> Have you identified whether it is requests against specific URLs
> within your application which
On Jul 1, 10:43 pm, "Vladimir Pouzanov" <[EMAIL PROTECTED]> wrote:
> $ grep Vm /proc/9453/status
> VmPeak:54556 kB
> VmSize:54552 kB
> VmLck: 0 kB
> VmHWM: 9804 kB
> VmRSS: 9804 kB
> VmData:48160 kB
> VmStk: 128 kB
> VmExe: 4 kB
> VmLib: 5528 kB
> V
On Jul 1, 8:17 pm, [EMAIL PROTECTED] wrote:
> Every django app grabs ~60mb of RAM. I'm currently running three
> different django fcgi processes and that uses half of my available
> RAM.
What is the initial memory size of the process when it is first
started? In other words, does it start out thi
$ grep Vm /proc/9453/status
VmPeak:54556 kB
VmSize:54552 kB
VmLck: 0 kB
VmHWM: 9804 kB
VmRSS: 9804 kB
VmData:48160 kB
VmStk: 128 kB
VmExe: 4 kB
VmLib: 5528 kB
VmPTE:60 kB
settings.DEBUG = False
settings.TEMPLATE_DEBUG = False
On 7/1/07, Ti
>> Every django app grabs ~60mb of RAM. I'm currently running three
>> different django fcgi processes and that uses half of my available
>> RAM.
>
> I'm kind of curious what you're doing with all that RAM ;)
Sounds almost like the classic case of not turning off DEBUG
settings, and having quer
On 7/1/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Every django app grabs ~60mb of RAM. I'm currently running three
> different django fcgi processes and that uses half of my available
> RAM.
I'm kind of curious what you're doing with all that RAM ;)
I run my blog on FastCGI, with a fair
Every django app grabs ~60mb of RAM. I'm currently running three
different django fcgi processes and that uses half of my available
RAM.
On 7/1/07, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
>
> Jeremy Dunck wrote:
> > Two settings files being used by a single process?
> >
> > How would that work?
Jeremy Dunck wrote:
> Two settings files being used by a single process?
>
> How would that work?
Oh... I missed the bit about a single process. But now I wonder why
require this? One server can happily serve two sites either from
separate mod_python handlers or separate FastCGI servers.
Vlad
On 6/30/07, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
>
> Vladimir Pouzanov wrote:
> serve both sites from one django process.
>
> Why not just have two settings files?
Two settings files being used by a single process?
How would that work?
--~--~-~--~~~---~--~~
Y
Vladimir Pouzanov wrote:
> Hi all,
>
> I have two sites that run nearly identical django instances. I wonder
> if it's possible to somehow set per-domain ROOT_URLCONF and
> TEMPLATE_DIRS to serve both sites from one django process.
Why not just have two settings files
On Sat, 2007-06-30 at 07:29 -0500, Jeremy Dunck wrote:
> On 6/30/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> >
> ...
> > No, this isn't possible. The settings file is read once and then the
> > settings are cached (and are assumed to be static).
>
> Actually, it *is* possible to alter the
On 6/30/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
...
> No, this isn't possible. The settings file is read once and then the
> settings are cached (and are assumed to be static).
Actually, it *is* possible to alter the urlconf that's processed on a
per-request basis, though TEMPLATE_DIR
On Sat, 2007-06-30 at 14:38 +0300, Vladimir Pouzanov wrote:
> Hi all,
>
> I have two sites that run nearly identical django instances. I wonder
> if it's possible to somehow set per-domain ROOT_URLCONF and
> TEMPLATE_DIRS to serve both sites from one django process.
>
Hi all,
I have two sites that run nearly identical django instances. I wonder
if it's possible to somehow set per-domain ROOT_URLCONF and
TEMPLATE_DIRS to serve both sites from one django process.
--
Sincerely,
Vladimir "Farcaller" Pouzanov
http
>
> > The line is there, inside the settings.py
> > It looks like
> > ROOT_URLCONF = 'testdrorys.urls'
> > ('testdrorys' is the name of my project)
> > and the file urls.py is in the same directory as settings.py
>
> > I'm getting co
On 6/6/07, ilDave <[EMAIL PROTECTED]> wrote:
>
> The line is there, inside the settings.py
> It looks like
> ROOT_URLCONF = 'testdrorys.urls'
> ('testdrorys' is the name of my project)
> and the file urls.py is in the same directory as settings.py
&
The line is there, inside the settings.py
It looks like
ROOT_URLCONF = 'testdrorys.urls'
('testdrorys' is the name of my project)
and the file urls.py is in the same directory as settings.py
I'm getting confused...
On Jun 6, 4:56 pm, "Deryck Hodge" <
On 6/6/07, ilDave <[EMAIL PROTECTED]> wrote:
> AttributeError: 'Settings' object has no attribute 'ROOT_URLCONF'
>
>
> What's wrong with my configuration? It seem that python can't find the
> urls.py file, but it is in the right place and eve
rs/
base.py", line 64, in get_response
urlconf = getattr(request, "urlconf", settings.ROOT_URLCONF)
File "/usr/local/lib/python2.5/site-packages/django/conf/
__init__.py", line 32, in __getattr__
return getattr(self._target, name)
AttributeError: 'Settings&#
37 matches
Mail list logo
