Re: Name error

n, 2019, 3:12 PM RAJA MISHRA, > wrote: > >> Name error : name 'django' is not defined in one of my app >> Plzz anyone explain how to fix this >> also how to use django.setup() >> >> -- >> You received this message because you are subscribed to the Google Gr

Re: Name error

Plz show your code otherwise search your total error line in Google you can find it. Always try to paste error codes so that it will b easy to find out error. Thanks. On Wed, 5 Jun, 2019, 3:12 PM RAJA MISHRA, wrote: > Name error : name 'django' is not defined in one of my app > Plzz

Name error

Name error : name 'django' is not defined in one of my app Plzz anyone explain how to fix this also how to use django.setup() -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving e

Re: Unique app name error problem when building a Wagtail multisite solution

Hi Melvyn, thanks for your answer. Unfortunately switching the CMS isn't an option. And even if I skip the multisite requirements i could think of usecases where it might be a problem in just a django project as well, wanting to have a similar project structure, doesn't it? Am Donnerstag, 22.

Re: Unique app name error problem when building a Wagtail multisite solution

Hi, On Wednesday 21 December 2016 14:30:32 'Matthias Brück' via Django users wrote: > is this really just not possible? What I found is this: > > you can't have two apps with the same name, even if they have > different > > fully qualified module paths > >

Re: Unique app name error problem when building a Wagtail multisite solution

is this really just not possible? What I found is this: you can't have two apps with the same name, even if they have different > fully qualified module paths https://groups.google.com/forum/#!msg/django-users/AMYLfQo6Ba4/Y-57B0i7qy4J How would you guys handle this? -- You received this

Unique app name error problem when building a Wagtail multisite solution

when i try to set the name in `apps.py` to unique ones i still get the unique name error. Is this project structure somehow possible? I understand that you would commonly put app2 in a separate project. But how would you do it if you implement a Wagtail multisite solution and still want to keep

Re: Messages framework name error

So, I woke up this morning and went to go get the trace for you. Turned off my DEBUG setting in the settings.py and ran into some internal server errors. Fixed those, and then the messages error I was getting fixed itself, I guess. It's working now, randomly. Don't know what was causing it,

Re: Messages framework name error

Hi, could you show the full stack trace? Antonis Christofides http://djangodeployment.com On 12/14/2016 07:34 AM, Zachary Sohovich wrote: I'm attempting to add a success or error message to a form. As far as I can see, I've added everything correctly. But, when I try to submit the form with

Messages framework name error

I'm attempting to add a success or error message to a form. As far as I can see, I've added everything correctly. But, when I try to submit the form with success or with error I get a 'NameError at /contact/' -> 'name message not defined'. Note that it says name message (not plural) not

Re: Name error ,not defined problem

Your URL definition is calling a module that hasn't been imported. At the top of your urls.py, add: from newsletter import views In the URL definition, do: url(r'^$', views.home, name='home'), ./s > > -- You received this message because you are subscribed to the Google Groups "Django

Re: Name error ,not defined problem

Didi you add* 'newsletter' *to your INSTALLED_APPS in settings.py? Em domingo, 19 de julho de 2015 07:16:52 UTC-3, Tara gurung escreveu: > > > > > This is my application structure with

Name error ,not defined problem

This is my application structure with newsletter application inside *SRC* project. *Hellow am newbie to django framework and need some help to fix it* *urls.py* has this added

Re: ChoiceInline field giving name error

> > Are you following any tutorial? If yes, provide link. Yes I was following tutorial of poll app and the error was solved by the solution provided by vinayak -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and

Re: ChoiceInline field giving name error

On Jan 15, 2015 4:17 PM, "Kamal Kaur" wrote: > > On Thu, Jan 15, 2015 at 4:08 PM, sanjeet kaur wrote: > > Yes I tried but all that is correct. > > Are you following any tutorial? If yes, provide link. Error solved -- You received this message

Re: ChoiceInline field giving name error

On Thu, Jan 15, 2015 at 4:08 PM, sanjeet kaur wrote: > Yes I tried but all that is correct. Are you following any tutorial? If yes, provide link. -- Kamaljeet Kaur -- You received this message because you are subscribed to the Google Groups "Django users" group. To

Re: ChoiceInline field giving name error

> > > Have you tried this? > > http://stackoverflow.com/questions/22768262/nameerror-not-defined > > -- > Kamaljeet Kaur > Yes I tried but all that is correct. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this

Re: ChoiceInline field giving name error

On Wednesday, 14 January 2015 18:33:59 UTC+5:30, sanjeet kaur wrote: > > Hi, > I am working on django ap in which I have two apps in a single project > but while using inline option, I get the error > > NameError: name 'ChoiceInline' is not defined > > I have searched this error and all

Re: ChoiceInline field giving name error

On Wed, Jan 14, 2015 at 6:33 PM, sanjeet kaur wrote: > NameError: name 'ChoiceInline' is not defined Have you tried this? http://stackoverflow.com/questions/22768262/nameerror-not-defined -- Kamaljeet Kaur -- You received this message because you are subscribed to

Re: no module name error

Since I'm unfamiliar with the book, I don't know about the 'created_at' field, which must be specific to the book's app design. Try commenting out the reference to 'created_at' in admin.py and see if you get further. If so, then try to be sure that you are following the book in order, and that

Re: no module name error

And by the way thanks for being patience with me! -- 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

Re: no module name error

Ok i removed ecomstore from, from ecomstore.catalog.models import Product, Category to from catalog.models import Product, Category And i think it worked fine. But now again it gives an error: ImproperlyConfigured at/catalog - 'ProductAdmin.exclude' refers to field 'created_at' that is missing

Re: no module name error

Ok. If catalog is in the upper directory, take the leading "ecomstore." off of the import statement. Also remove it from the entry in INSTALLED_APPS. Alternatively, move the catalog directory (will all of its contents), into the lower directory. If you are at a unix or mac os shell prompt the

Re: no module name error

Can you run: python manage.py shell ? If you already have an error, try again with the 'ecomstore.catalog', line commented out in settings.py If shell runs without an error and gives you a python prompt, try the following, in sequence until you get an error: >>> import ecomstore >>>

Re: no module name error

Its in the upper directory, i.e. where the manage.py is. Sent from Samsung tablet Bill Freeman wrote: Yes, but of which directory is the catalog directory a sub-directory?  The upper ecomstore (which contains manage.py) or the lower ecomstore (which contains

Re: no module name error

Yes, but of which directory is the catalog directory a sub-directory? The upper ecomstore (which contains manage.py) or the lower ecomstore (which contains settings.py)? Or is it somewhere else entirely? On Sat, May 18, 2013 at 6:59 PM, Kakar Arunachal Service <

Re: no module name error

The directory is as follows: ecomstore --manage.py --ecomstore __init__.py settings.py urls.py wsgi.py --preview __init__.py models.py views.py test.py --templates --tags navigation.html base.html catalog.html index.html --static css.css --catalog __init__.py

Re: no module name error

ecomstore is the project name. And within it, it has another ecomstore, which has the __init__.py, settings.py, urls.py and wsgi.py. And yes catalog too has the __init__.py file in it, as it was created by the startapp command. The error says, import error: no module named catalog.models in

Re: no module name error

Does the ecomstore directory (as well as the catalog dirction) also have an __init__.py file in it? And is the ecomstore directory in the same directory as manage.py ? Or is ecomstore the project name, rather than part of an app with extra levels? (Still needs an __init__.py) And if so, and

Re: no module name error

Oh..m sorry. I mistyped, it was not django.ecomstore.catalog.models, but just, ecomstore.catalog.models import Category, Product. N in the catalog dir, it has __init__.py file, so should have done the problem. N m using sqlite3 so i dnt need adapters too. Pls help. -- You received this message

Re: no module name error

Unless you actually created your stuff inside your installation of Django (or under some directory named site-packages or dist-packages), which is not recommended, it is unlikely that the place from which you import Category and Products will be named beginning with "django.". The book may be

no module name error

I'm practicing from a book Begining django e-commerce and m stuck in one place. My project name is ecomstore, and in it i have two app, one is preview and the other is catalog. In my preview app, there's just html in the templates dir, and thats not the problem, because the result was fine when i

Re: Name Error in django class method

yes-sure i ll follow the instructions note. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/KprOvRmbsXYJ. To post to this group, send email to

Re: Name Error in django class method

yes i had imported os module. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/Uo4NIB7To7EJ. To post to this group, send email to

Re: Constant name error undefined in custom template tags

On Sun, Oct 9, 2011 at 8:49 PM, Daniel Roseman wrote: > On Sunday, 9 October 2011 20:26:26 UTC+1, Kayode Odeyemi wrote: > >> Hello, >> >> I'm creating a template tag that will will allow session variables stored >> as strings or >> dict in a view to be available in its

Re: Constant name error undefined in custom template tags

On Sunday, 9 October 2011 20:26:26 UTC+1, Kayode Odeyemi wrote: > > Hello, > > I'm creating a template tag that will will allow session variables stored > as strings or > dict in a view to be available in its template. The syntax is: > > {% session_value [view_name] [session_variable] [arg] %}

Constant name error undefined in custom template tags

Hello, I'm creating a template tag that will will allow session variables stored as strings or dict in a view to be available in its template. The syntax is: {% session_value [view_name] [session_variable] [arg] %} But at the moment I don't know how I can get Django to stop throwing name errors

Re: No module name error

yes that import statement was done by me but im not sure if that is the correct way to do it or not. On May 7, 12:01 pm, Bayuadji wrote: > see this line > import profiles.utils > > in views.py on django registration doesn't have that line. so I think > you or someone already

Re: No module name error

see this line import profiles.utils in views.py on django registration doesn't have that line. so I think you or someone already customized the registration apps -adji- On Fri, May 7, 2010 at 9:57 AM, newbiedjango wrote: > my views.py is > down here which is an

Re: No module name error

my views.py is down here which is an extension of http://bitbucket.org/ubernostrum/django-registration/src/tip/registration/views.py I am a total newbie here and don't know much about this..kindly help... from django.shortcuts import redirect from django.shortcuts import render_to_response from

No module name error

hi all, i am a newbie in django and have been trying to get this django- registration app working with few extra fields. now i am getting his module error http://dpaste.com/191756/ please help fixing me this error.. Thanks -- You received this message because you are subscribed to the Google

Re: No module name error

Hi, I don't know which version of django-registration you use, but the source on views.py doesn't have any profiles.utils see :http://bitbucket.org/ubernostrum/django-registration/src/tip/registration/views.py -adji- On Fri, May 7, 2010 at 9:19 AM, newbiedjango wrote:

No module name error

hi all, i am a newbie in django and have been trying to get this django- registration app working with few extra fields. now i am getting his module error http://dpaste.com/191756/ please help fixing me this error.. Thanks -- You received this message because you are subscribed to the Google

Re: name error not defined in models

On Tue, Sep 1, 2009 at 11:19 AM, Joru<avenp...@gmail.com> wrote: > > Hi > > I got name error in my models when using models.ManyToManyField > Here are my models > > class Ank(models.Model): >    route = models.ManyToManyField(Dek) >    intercity = models.BooleanF

name error not defined in models

Hi I got name error in my models when using models.ManyToManyField Here are my models class Ank(models.Model): route = models.ManyToManyField(Dek) intercity = models.BooleanField() class Dek(models.Model): ank = models.ManyToManyField(Ank) How come I got "NameError: name

Re: weird name error

To whom it may concern, the problem was the order in which the classes are created. In the above exampel, the order seems fine but in my model the species_d comes first and then the layers. this makes it search for sth that is not initiated yet! cheers and sorry for the stupid error... On Mar

Re: weird name error

models.CharField(max_length=200, null=True) > >     speciesUser = models.ForeignKey(User) > >     lon = models.FloatField(4) > >     lat = models.FloatField(4) > >     uLayer = models.ForeignKey(LayersOfUsers) > > >     def __unicode__(self): > >         ret

Re: weird name error

rField(max_length=200, null=True) >     speciesUser = models.ForeignKey(User) >     lon = models.FloatField(4) >     lat = models.FloatField(4) >     uLayer = models.ForeignKey(LayersOfUsers) > >     def __unicode__(self): >         return self.speciesName > * > > i am getting

weird name error

): speciesName = models.CharField(max_length=200, null=True) speciesUser = models.ForeignKey(User) lon = models.FloatField(4) lat = models.FloatField(4) uLayer = models.ForeignKey(LayersOfUsers) def __unicode__(self): return self.speciesName * i am getting a name error

Weird Name error?

I am getting a weird error when I call a property from a template. I also tried calling it from the view and get the same error. However I have called it from another script it works fine. Error: http://dpaste.com/115147/ definition of survivor(which is being included with the same include that