Re: Why does django throw TypeError when sending requests through Apache WSGI?

Used libapache2-mod-wsgi-py3 instead of python 2 version On Wednesday, 15 December 2021 at 10:03:27 UTC Kyle Paterson wrote: > I am not using either of those, I think. The only place I explicitly load > settings is in wsgi.py, with the line: > os.environ[‘DJANGO_SETTINGS_MODULE’] = ‘travel

Re: Why does django throw TypeError when sending requests through Apache WSGI?

I am not using either of those, I think. The only place I explicitly load settings is in wsgi.py, with the line: os.environ[‘DJANGO_SETTINGS_MODULE’] = ‘travel data.settings' On Thu, 9 Dec 2021 at 12:52, Jason wrote: > > with your settings usage, are you defining a property in settings and >

Re: Why does django throw TypeError when sending requests through Apache WSGI?

with your settings usage, are you defining a property in settings and trying to use it anywhere? furthermore, are you using settings via from traveldata.traveldata import settings (example) or via from django.conf import settings The latter is the recommended means because settings are

Re: Why does django throw TypeError when sending requests through Apache WSGI?

Hi, I think this is not related with apache It seems like class object property is called as a method somehow. Unfortunately the error does not reveal the property name. Regards, Sencer HAMARAT On Wed, Dec 8, 2021 at 4:59 PM Kyle Paterson wrote: > Started a new project after not using

Why does django throw TypeError when sending requests through Apache WSGI?

Started a new project after not using Django for roughly two years, works fine when running as a development server but throws TypeError: SimpleLazyObject class: property object not callable. >From apache error log: [Wed Dec 08 10:11:53.023239 2021] [wsgi:error] [pid 10704:tid 140343150348032]

Re: Discussion: Why not Django include uWSGI/FastCGI support internally just like Spring Boot include tomcat ?

Exactly ! It's cool to have a project like Django Boot ~~ Simone Federici 于2019年2月27日周三 下午4:52写道： > Spring boot is like a django boot external lib to start a django > microservice. > exactly like spring boot. you can build your spring application without a > spring boot starter. > > > On Wed,

Re: Discussion: Why not Django include uWSGI/FastCGI support internally just like Spring Boot include tomcat ?

Spring boot is like a django boot external lib to start a django microservice. exactly like spring boot. you can build your spring application without a spring boot starter. On Wed, 27 Feb 2019 at 09:35, panfei wrote: > If Django include these production-ready container, and then implement a >

Discussion: Why not Django include uWSGI/FastCGI support internally just like Spring Boot include tomcat ?

If Django include these production-ready container, and then implement a mange.py admin command, by just executing the command we can start a production-ready service. Any possibilities on this idea ? -- 不学习，不知道 -- You received this message because you are subscribed to the Google Groups

Re: REG: Why my django email settings not sending email notifications?

Hi Amitesh, >From my experience, You need to go to Google’s settings and enable access to >‘less secure apps’. That will let you send emails freely from your django dev >environment. Do so at your own risk, as any less secure app can use your email >and password. I would suggest you create a

Re: REG: Why my django email settings not sending email notifications?

if you have MFA enabled on your gmail, you may have to disable it On Mon, Feb 18, 2019 at 1:08 PM Onkar Narkar wrote: > > Hi Amitesh, > > Are you getting some error like this: > smtplib.SMTPAuthenticationError: (534, b'5.7.9 Application-specific > password required. Learn more at\n5.7.9 >

Re: REG: Why my django email settings not sending email notifications?

Hi Amitesh, Are you getting some error like this: smtplib.SMTPAuthenticationError: (534, b'5.7.9 Application-specific password required. Learn more at\n5.7.9 https://support.google.com/mail/?p=InvalidSecondFactor 128sm18480521pfx.7 - gsmtp') If this is the case, you need to specify

Re: REG: Why my django email settings not sending email notifications?

When I used gmail for my testing, I had to go to my gmail settings to turn on some settings. Sorry cannot remember it but I will try to find what it was. By the way what does the debug error says? On Mon, Feb 18, 2019 at 9:42 AM Simon A wrote: > Just to add, please try to create a python file

Re: REG: Why my django email settings not sending email notifications?

Just to add, please try to create a python file with the simplest implementation of send mail just to check if it actually works. On Monday, February 18, 2019 at 11:43:22 AM UTC+8, Sid wrote: > > can you check if you your email server is somehow blocking your emails? > Have you enabled your

Re: REG: Why my django email settings not sending email notifications?

The email server is a gmail smtp server. People across the globe use that for their development purpose. So, I guess that shouldn't be a issue. The debug is "ON" by default. Regards, Amitesh Sahay91-750 797 8619 On Monday, 18 February, 2019, 9:12:57 am IST, Siddharth Tamang wrote:

Re: REG: Why my django email settings not sending email notifications?

can you check if you your email server is somehow blocking your emails? Have you enabled your debug settings ON? On Sun, Feb 17, 2019 at 2:49 PM 'Amitesh Sahay' via Django users < django-users@googlegroups.com> wrote: > I have created a registration page that sends an email notification on >

REG: Why my django email settings not sending email notifications?

I have created a registration page that sends an email notification on successful registration. I do have my email notification in place. But it doesn't seem to be working, neither it is throwing any error. Below is the code snippet. views.py def register(request): validators =

Re: Why some Django fields are not saved in database?

Thanks for sharing this, I will do the same first. On Thursday, June 21, 2018 at 5:55:42 PM UTC+5:30, Melvyn Sopacua wrote: > > On donderdag 21 juni 2018 11:31:26 CEST prateek gupta wrote: > > > > > Thanks for reviewing the code. > > > > > > I am new to Django and just tried to put logic from

Re: Why some Django fields are not saved in database?

On donderdag 21 juni 2018 11:31:26 CEST prateek gupta wrote: > Thanks for reviewing the code. > > I am new to Django and just tried to put logic from googling to achieve my > goal. > That's why I don't understand my code completely. Try to understand it before applying. The main issue you're

Re: Why some Django fields are not saved in database?

Thanks for reviewing the code. I am new to Django and just tried to put logic from googling to achieve my goal. That's why I don't understand my code completely. Can you please point out where I am doing this and how can I change this behaviour? On Thursday, June 21, 2018 at 2:48:46 PM

Re: Why some Django fields are not saved in database?

On donderdag 21 juni 2018 10:42:09 CEST prateek gupta wrote: > Issue is in database , latitude/longitude values are blank. > > What I am doing wrong here? Why do you not understand your own code? How did you get that code - you explicitly code it so that it they do NOT end up in the database.

Why some Django fields are not saved in database?

Hi All, I have a store address form in Django which have fields like- name, address, location, latitude, longitude etc. I am autofilling the latitude, longitude fields based on address with the help of django package-https://github.com/caioariede/django-location-field In django view after

Re: Why doesn't Django support managing Raw SQL changes using migration system like models

Hi Cmp, Well, Django has to be database agnostic for things to work with any database. If raw sql is allowed, how do you can be sure it will work with any database? So far, you mentioned a bunch of PostreSQL things. But what if, tomorrow, some higher ups decided that support is required and buy

Why doesn't Django support managing Raw SQL changes using migration system like models

I have an problem that I wanted to solve recently using a Postgres Trigger + Procedure that I do not want to do via Signals or within Python itself. I want to make a log which when an entry is created the result is applied to a row. We need the log to be the source of truth and I don't want to

Re: Why does Django say my login form is invalid? How can I find out why Django thinks it is?

gt; The login form accepts two fields labeled "Email" and "Password." But when > I hit "Log in" button, the page just seems to refresh. If I uncomment the > `print` statement, it prints, indicating that > `login_form.is_valid()!=True`. Why does Django do this? >

Re: Why does Django say my login form is invalid? How can I find out why Django thinks it is?

Tom, - You shouldn't use Model=User (or the Meta) as it was a ModelForm, it is just a regular Form - AuthenticationForm takes request as its first parameter: def login_register(request, template="templates/login_register.html"): if request.method == "POST": login_form =

Re: Why does Django say my login form is invalid? How can I find out why Django thinks it is?

I removed that line, but nothing changed. On Wednesday, November 29, 2017 at 11:58:28 PM UTC-5, Matemática A3K wrote: > > > > On Thu, Nov 30, 2017 at 12:35 AM, Tom Tanner > wrote: > >> What would I need to change? >> >> I tried changing the ... >> fields= ("username",)

Re: Why does Django say my login form is invalid? How can I find out why Django thinks it is?

On Thu, Nov 30, 2017 at 12:35 AM, Tom Tanner wrote: > What would I need to change? > > I tried changing the ... > fields= ("username",) > > ... to ... > fields= ("username","email",) > or... > fields= ("email",) > > Nothing seemed to change. the

Re: Why does Django say my login form is invalid? How can I find out why Django thinks it is?

What would I need to change? I tried changing the ... fields= ("username",) ... to ... fields= ("username","email",) or... fields= ("email",) Nothing seemed to change. the `login_form.is_valid()` still is `False`. Sorry if the question is dumb, I'm still learning Django thru working with it.

Re: Why does Django say my login form is invalid? How can I find out why Django thinks it is?

> class LoginForm(AuthenticationForm): > username= forms.EmailField(label=_("Email"), max_length=254) > > > class Meta: > model= User > > > fields= ("username",) > > If you use "fields = ("username")" you are restricting the fields to just that field, and the authentication form needs also

Why does Django say my login form is invalid? How can I find out why Django thinks it is?

{{ login_form.as_p }} Log in The login form accepts two fields labeled "Email" and "Password." But when I hit "Log in" button, the page just seems to refresh. If I uncomment the `print` statement, it prints, indicating that `login_form.is_valid()!=True`. Why

Re: Why in Django the field IntegerRangeField not worked with None?

Look like it is expected behaviour. filter builds sql, any sql should have sence. What is sence with broken sql ? Many thanks, Serge +380 636150445 skype: skhohlov On Wed, Jun 15, 2016 at 1:09 PM, Seti Volkylany wrote: > The model next: > > class

Re: Why does Django allow Circular Model Relation

You would use it any time the relationship means something different. It would generally be inappropriate to use it as a simple backwards relationship (Django does this for you), but there's no reason not to have multiple relationships in a number of directions. In an HR system, someone could be

Re: Why does Django allow Circular Model Relation

On 2016-02-19 07:29, Eddilbert Macharia wrote: > Hello vadim when would such a relationship be needed I'm curious Think of a hierarchy at a company. Most employees have a supervisor. So your table would reference the supervisor in the same table: class Employee(models.Model): name = ...

Re: Why does Django allow Circular Model Relation

Hello vadim when would such a relationship be needed I'm curious -- 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

Re: Why does Django allow Circular Model Relation

Why should it be complained? I know a lot of the same cases that may be applied. пятница, 19 февраля 2016 г., 15:00:12 UTC+2 пользователь Eddilbert Macharia написал: > > Hello All, > > I was working on a project, and realized that Django does not complain > when you create Circular Model

Re: Why does Django allow Circular Model Relation

On 19 February 2016 at 13:00, Eddilbert Macharia wrote: > Hello All, > > I was working on a project, and realized that Django does not complain when > you create Circular Model relationship even when creating migrations where i > expected to have this complain why would it

Why does Django allow Circular Model Relation

Hello All, I was working on a project, and realized that Django does not complain when you create Circular Model relationship even when creating migrations where i expected to have this complain e.g. the example does not make any sense as far as relationships go but it makes my point.

Re: Why does django use mysqldb over mysql-connector?

Hello, > https://github.com/PyMySQL/mysqlclient-python > > I didn't tried that. Someone use it? > I use it. There's a thread about it on django-developers. https://groups.google.com/d/topic/django-developers/n-TI8mBcegE/discussion Collin -- You received this message because you are

Re: Why does django use mysqldb over mysql-connector?

Yes, thanks for the link. For some reason google wasn't finding that for me. On Tue, Nov 4, 2014 at 6:59 AM, wrote: > > Are you talking about this? > > https://github.com/PyMySQL/mysqlclient-python > > I didn't tried that. Someone use it? > > > Em terça-feira, 4 de novembro de

Re: Why does django use mysqldb over mysql-connector?

Are you talking about this? https://github.com/PyMySQL/mysqlclient-python I didn't tried that. Someone use it? Em terça-feira, 4 de novembro de 2014 09h08min38s UTC-2, larry@gmail.com escreveu: > > What about mysqlclient? The django site says that is "the recommended > choice for using

Re: Why does django use mysqldb over mysql-connector?

What about mysqlclient? The django site says that is "the recommended choice for using MySQL with Django" but I can't seem to find that package. Does anyone have a link for that? On Mon, Nov 3, 2014 at 8:57 PM, wrote: > > Hi all, > > I notice that python-mysql-connector(1) is

Re: Why does django use mysqldb over mysql-connector?

Hi all, I notice that python-mysql-connector(1) is almost 30% slow that MySQLdb(2), but MySQLdb until now not support python3. Anyone have news when MySQLdb will support python 3 or know another connector for mysql? It's a litte confused at this time, because we have django1.7.X that

Re: why does django user require create database privlages for testing

>> Rails doesn't require this, you create a test database as super user and >> it uses it for testing. Why doesn't django allow this? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >&

Re: why does django user require create database privlages for testing

Because virtually all of us don't want our production database used for testing. On Wed, Apr 23, 2014 at 4:18 PM, dacresni <vivacar...@gmail.com> wrote: > Rails doesn't require this, you create a test database as super user and > it uses it for testing. Why doesn't

why does django user require create database privlages for testing

Rails doesn't require this, you create a test database as super user and it uses it for testing. Why doesn't django allow this? -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving e

Why would Django (1.5.1) call Loader.load_template_source() over and over again?

I've got a fairly standard ListView trying to render a template stored in my DB (originally via the dbtemplates lib, finally trying my own template loader). However, the view times out in the browser. After some investigation, it seems that Loader.load_template_source() is called 69 times in

Re: Why doesn't Django support subdomain url conf?

Thank you Rafał, it's useful. But it's will be reasonable if django own subdomains built-in. On Saturday, June 16, 2012 6:04:36 PM UTC+4, Rafał Stożek wrote: > > You may want to take a look at this project: > https://github.com/ennio/django-hosts > > On Saturday, June 16, 2012 1:48:16 PM UTC+1,

Re: Why doesn't Django support subdomain url conf?

+1 django-hosts worked very well for me. On Sat, Jun 16, 2012 at 5:04 PM, Rafał Stożek wrote: > You may want to take a look at this project: > https://github.com/ennio/django-hosts > > > On Saturday, June 16, 2012 1:48:16 PM UTC+1, Alireza Savand wrote: >> >> Have extremely

Re: Why doesn't Django support subdomain url conf?

You may want to take a look at this project: https://github.com/ennio/django-hosts On Saturday, June 16, 2012 1:48:16 PM UTC+1, Alireza Savand wrote: > > Have extremely control on URLs with django is easy as possible. > > But why there is nothing about handling subdomains url configration, all i

Re: Why doesn't Django support subdomain url conf?

i don't think we can say that, cause instead of handling url in urls.conf, we could done that in .htaccess or as you said in WebServer configuration. On Sat, Jun 16, 2012 at 5:21 PM, Daniel Roseman wrote: > On

Re: Why doesn't Django support subdomain url conf?

On Saturday, 16 June 2012 13:48:16 UTC+1, Alireza Savand wrote: > > Have extremely control on URLs with django is easy as possible. > > But why there is nothing about handling subdomains url configration, all i > found it was >

Why doesn't Django support subdomain url conf?

Have extremely control on URLs with django is easy as possible. But why there is nothing about handling subdomains url configration, all i found it was makinga middleware

Re: Why does django use mysqldb over mysql-connector?

My frustration was borne by the ease with which Debian makes the task: I did expect the job to be an insignificant one-line command. Thanks Tom. Apple don't see a profit in providing a mysql-client package. Ramiro has a point that lobbying MySQL for a client-only OSX package is a righteous

Re: Why does django use mysqldb over mysql-connector?

On Fri, May 4, 2012 at 2:18 AM, john2095 wrote: > I've just been through a slice of hell simply because I did not want to > install mysql-server on my (osx) django development machine - my app > connects to a remote mysql database.  It turns out that python's "mysqldb" >

Re: Why does django use mysqldb over mysql-connector?

On Thu, May 3, 2012 at 10:18 PM, john2095 wrote: > I've just been through a slice of hell simply because I did not want to > install mysql-server on my (osx) django development machine - my app > connects to a remote mysql database.  It turns out that python's "mysqldb" >

Re: Why does django use mysqldb over mysql-connector?

On 2012-05-04, at 09:36 , john2095 wrote: > Oh. Thanks Kurtis. That answers the first question: it's built on mysqldb > primarily because it's mature and stable. Thanks. > > As for the second question: has anyone tried building a backend on > mysql-connector yet? Silence? Is this an

Re: Why does django use mysqldb over mysql-connector?

Oh. Thanks Kurtis. That answers the first question: it's built on mysqldb primarily because it's mature and stable. Thanks. As for the second question: has anyone tried building a backend on mysql-connector yet? Silence? Is this an opportunity? On Friday, 4 May 2012 16:53:43 UTC+10, Kurtis

Re: Why does django use mysqldb over mysql-connector?

I think what he was trying to get at is that the Python MySQL Adapter is in early stages of development where-as Django is depended upon to be a very stable platform/framework. It would be great to have the option to use that adapter though for situations like yours. On Fri, May 4, 2012 at 1:21

Re: Why does django use mysqldb over mysql-connector?

Yes, that's the pure python adapter I'm talking about. I think that's effectively the same as this one. Nice link but I'm not sure if you're suggesting that as additional information or an answer? The question remains is a compelling reason

Re: Why does django use mysqldb over mysql-connector?

> Has this happened by default or by design?  Is mysqldb really that much > faster, or featureful, or just because it's more common? >From http://forge.mysql.com/projects/project.php?id=302 "Development Status: Early (Pre-Alpha)" -- steve -- You received this message because you are

Why does django use mysqldb over mysql-connector?

I've just been through a slice of hell simply because I did not want to install mysql-server on my (osx) django development machine - my app connects to a remote mysql database. It turns out that python's "mysqldb" depends on mysql binaries which are only packaged up with the server release.

Re: Why does django default to Chicago time?

I believe that people who created Django are from there. :) On 16 February 2012 14:46, Roy Smith wrote: > In the default settings.py file, the timezone is set to: > > TIME_ZONE = 'America/Chicago' > > Why? Wouldn't None (to match the server's time zone) be a more sane >

Why does django default to Chicago time?

In the default settings.py file, the timezone is set to: TIME_ZONE = 'America/Chicago' Why? Wouldn't None (to match the server's time zone) be a more sane default? Even setting it to UTC would be more reasonable than setting it to any specific timezone, but surely going with the system

Re: Why does Django create Postgres timestamp columns with time zones?

>From >postgresql.org/docs/8.4/static/datatype-datetime.html: > "All timezone-aware dates and times are stored internally in UTC. They are converted to local time in the zone specified by the timezone configuration parameter

Re: Why does Django create Postgres timestamp columns with time zones?

It's not required by PostgreSQL. See, http://www.postgresql.org/docs/8.4/interactive/datatype-datetime.html , for example. You may be able to change the data type of that column directly in the database. (See http://www.postgresql.org/docs/8.4/interactive/ddl-alter.html#AEN2595 .) Maybe

Why does Django create Postgres timestamp columns with time zones?

I thought that Django created datetime columns that were time zone agnostic, but when I looked at my Postgres table I saw that the values recorded there have time zone information. Going further I found that the Postgres backend directs Django to create columns that use time zones. >From

Why does Django not pass on error messages with the default 404 view?

The docs (https://docs.djangoproject.com/en/dev/topics/http/views/ #customizing-error-views) state, "The page_not_found view should suffice for 99% of Web applications, but if you want to override it, you can specify handler404 in your URLconf". The page_not_found view only passes on the

Why doesn't Django use same filebase backend for Cache and Session?

The Cache backend of file: django/core/cache/backend/filebased.py The Session backend of file: django/contrib/sessions/backends/file.py I want use the Session that information store in file, but I see the code of Session backend of file, it's terrible, they save all session file in same

Re: Why is django-registration 0.8 not on PyPI?

Hello Ram, James Bennett would be the final authority on that question. Perhaps because it's not actually been released as 0.8? It appears to be in alpha stage. Toodle-l... creecode -- You received this message because you are subscribed to the Google Groups "Django users"

Why is django-registration 0.8 not on PyPI?

Hey, Does anyone know what's up with django-registration 0.8 not being on PyPI? Ram. -- 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

Re: Why does Django Fail on Date Field?

I could easily have used the Informix "null" date of 12/31/1899, but chose that instead. I put the dates into a table, so when they were processed they'd be set to a real date, today's. On Mar 11, 7:39 am, Kenneth Gonsalves wrote: > On Fri, 2011-03-11 at 04:28 -0800,

Re: Why does Django Fail on Date Field?

On Fri, 2011-03-11 at 04:28 -0800, octopusgrabbus wrote: > It's a date format MySQL will accept into a date field. I suppose it can be used for recording Adam's date of birth? -- regards KG http://lawgon.livejournal.com Coimbatore LUG rox http://ilugcbe.techstud.org/ -- You received this

Re: Why does Django Fail on Date Field?

It's a date format MySQL will accept into a date field. On Mar 10, 8:07 pm, Kenneth Gonsalves wrote: > On Thu, 2011-03-10 at 09:46 -0800, octopusgrabbus wrote: > > load_date = '-00-00' > > what on earth is this? > -- > regards > KGhttp://lawgon.livejournal.com >

Re: Why does Django Fail on Date Field?

On Thu, 2011-03-10 at 09:46 -0800, octopusgrabbus wrote: > load_date = '-00-00' what on earth is this? -- regards KG http://lawgon.livejournal.com Coimbatore LUG rox http://ilugcbe.techstud.org/ -- You received this message because you are subscribed to the Google Groups "Django users"

Re: Why does Django Fail on Date Field?

I converted my date, and it all works fine. Thanks for your help. On Mar 10, 12:54 pm, Tom Evans wrote: > On Thu, Mar 10, 2011 at 5:46 PM, octopusgrabbus > > > > wrote: > > I'm confused as to how this code isn't using the model? > > > Here's

Re: Why does Django Fail on Date Field?

On Thu, Mar 10, 2011 at 5:46 PM, octopusgrabbus wrote: > I'm confused as to how this code isn't using the model? > > Here's the model I'm using. The table is in a MySQL database. > class CsRemove(models.Model): >    action = models.CharField(max_length=3,

Re: Why does Django Fail on Date Field?

Will this answer your question? >>> import datetime >>> datetime.datetime(year=, month=00, day=00) Traceback (most recent call last): File "", line 1, in ValueError: year is out of range Jirka -- You received this message because you are subscribed to the Google Groups "Django

Re: Why does Django Fail on Date Field?

I'm confused as to how this code isn't using the model? Here's the model I'm using. The table is in a MySQL database. class CsRemove(models.Model): action = models.CharField(max_length=3, db_column='Action') # Field name made lowercase. endpointid = models.IntegerField(primary_key=True,

Re: Why does Django Fail on Date Field?

On Thu, Mar 10, 2011 at 5:31 PM, octopusgrabbus wrote: > The code's in the last post. What other code would you like to see? > If you'd like help, please reply to the list, not to me directly. Thanks. *Some* code is in the post. Your problem is that you are formatting

Re: Why does Django Fail on Date Field?

On Thu, Mar 10, 2011 at 3:18 PM, octopusgrabbus wrote: > Could my problem be related to the fact that my views.py module first > performs a get (sql select) on the table in question, and if the > record is > not there, then inserts it? No, it's probably because you are

Re: Why does Django Fail on Date Field?

Could my problem be related to the fact that my views.py module first performs a get (sql select) on the table in question, and if the record is not there, then inserts it? try: temp_ept_id = CsRemove.objects.get(endpointid=requested_serial_number)

Re: Why does Django Fail on Date Field?

This is a MySQL 5.0+ database. I can manually insert using Query Browser. On Mar 8, 12:34 pm, octopusgrabbus wrote: > Sorry. The error is Exception Type: > ValidationError > Exception Value: > [u'Enter a valid date in -MM-DD format.'] > > I have printed out for

Re: Why does Django Fail on Date Field?

Sorry. The error is Exception Type: ValidationError Exception Value: [u'Enter a valid date in -MM-DD format.'] I have printed out for myself to prove that my date is in this format. On Mar 8, 8:24 am, Jirka Vejrazka wrote: > Well, we're missing the bit where you

Re: Why does Django Fail on Date Field?

Well, we're missing the bit where you tell us what error are you getting. I don't know about others, but my crystal ball is a bit dusty these days. The models.py snippet you posted is obvious result of inspectdb output, which *may* need some manual tweaking. But it's difficult for us to guess as

Why does Django Fail on Date Field?

Here is the table: class CsRemove(models.Model): action = models.CharField(max_length=3, db_column='Action') # Field name made lowercase. endpointid = models.IntegerField(primary_key=True, db_column='EndpointId') # Field name made lowercase. devicetype =

Re: Why not Django with FastCGI?

On Wed, Apr 21, 2010 at 3:08 AM, Sven Svenson <svensvens...@gmail.com> wrote: > I'm new to the Django world but it seems that FastCGI is not the > preferred way to deploy a Django application. Why is that? I've had > good success using FastCGI with Perl/Catalyst-based applicati

Why not Django with FastCGI?

I'm new to the Django world but it seems that FastCGI is not the preferred way to deploy a Django application. Why is that? I've had good success using FastCGI with Perl/Catalyst-based applications. Thanks. /sven -- You received this message because you are subscribed to the Google Groups

Re: Why is django returning only naive datetimes?

On 09/04/10 19:05, Paweł Roman wrote: I've noticed that django always fetches 'naive' datetimes from the database. Tzinfo property on a datetime object is always set to null, even if the database stores a value WITH a timezone. This is a bit tedious because such datetime cannot be later

Re: Why is django returning only naive datetimes?

On Fri, Apr 9, 2010 at 2:48 PM, Ramiro Morales wrote: > On Fri, Apr 9, 2010 at 3:20 PM, Tom X. Tobin wrote: >> >> This reminds me that we need to open-source our time zone code.  We >> track entertainment events across several time zones, and Django's

Re: Why is django returning only naive datetimes?

On Fri, Apr 9, 2010 at 3:20 PM, Tom X. Tobin wrote: > > This reminds me that we need to open-source our time zone code.  We > track entertainment events across several time zones, and Django's > standard time handling can't cleanly deal with that.  Database > backends

Re: Why is django returning only naive datetimes?

> This reminds me that we need to open-source our time zone code.  We > track entertainment events across several time zones, and Django's > standard time handling can't cleanly deal with that.  Database > backends that store time zones as a UTC offset (e.g., PostgreSQL) > actually cause *more*

Re: Why is django returning only naive datetimes?

On Fri, Apr 9, 2010 at 1:05 PM, Paweł Roman wrote: > I've noticed that django always fetches 'naive' datetimes from the > database. Tzinfo property on a datetime object is always set to null, > even if the database stores a value WITH a timezone. > > This is a bit

Why is django returning only naive datetimes?

I've noticed that django always fetches 'naive' datetimes from the database. Tzinfo property on a datetime object is always set to null, even if the database stores a value WITH a timezone. This is a bit tedious because such datetime cannot be later converted to any timezone. Each time I want to

Re: on manage.py validate why is django trying to access the database?

On Tuesday 22 Dec 2009 4:51:31 pm Kenneth Gonsalves wrote: > in a site on my local machine I am getting a psycopg programming error on > doing manage.py validate. Other sites on the same machine are behaving ok. > Any clues? > solved - someone had put code to execute in models.py - and

on manage.py validate why is django trying to access the database?

hi, in a site on my local machine I am getting a psycopg programming error on doing manage.py validate. Other sites on the same machine are behaving ok. Any clues? The error message is here: [law...@xlquest certificate]$ python manage.py validate Traceback (most recent call last):

Re: Why does Django think my browser doesn't except cookies?

Starting with that premise, I looked into what circumstances lead to IE rejecting cookies unread. As it turned out, the VM System clock was six weeks behind the times and IE was throwing out what appeared to be six week old cookies. After adjusting the VM system clock the problem went away.

Re: Why does Django think my browser doesn't except cookies?

I wouldn't be surprised if this is a bug in IE =/ --~--~-~--~~~---~--~~ 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

Why does Django think my browser doesn't except cookies?

This morning I started running a project using Django 1.03 on Apache2 on Ubuntu 9.10, which is running as a Virtual Machine on a Windows XP system. I have run the same Django project successfully on a Ubuntu 9.10 system. However, the VM version insists that IE does not accept cookies. Firefox

Re: Why doesn't Django display template line number of errors?

On Wed, Oct 7, 2009 at 5:38 PM, NealWalters wrote: > > Any ideas on this question from about a month ago? > It was answered. Django does display the line number, along with the line in error and surrounding lines, in the Django debug page. If Google App Engine

Re: Why doesn't Django display template line number of errors?

Any ideas on this question from about a month ago? Thanks, Neal --~--~-~--~~~---~--~~ 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

  1   2   >