Re: Tips for debugging intermittent 502s with Daphne

Please add your nginx conf, this error may be connected to gthe setup of the server. On Sunday, October 11, 2020 at 7:04:51 PM UTC+2 dvs...@gmail.com wrote: > Hi do you hire contract based python/django freelancer? > We can help you in this and related tasks at fair prices. Reply or send >

Re: Tips for debugging intermittent 502s with Daphne

Hi do you hire contract based python/django freelancer? We can help you in this and related tasks at fair prices. Reply or send email to divy...@pythonmate.com Best Regards, Divyesh Khamele, Pythonmate On Thu, 8 Oct 2020, 3:50 am Keith Hackbarth, wrote: > Hey all, > > Was hoping to get some

Tips for debugging intermittent 502s with Daphne

Hey all, Was hoping to get some advice about how to debug intermittent 502 using Daphne - I observe connection error in the NGIX logs (where I"m using proxy_pass) *Connection refused) while connecting to upstream* - I observe in NGIX logs that it correlates with spike in inbound

Needs some debugging codes

Can anyone provide me some codes examples that i can debug. Basically I am new to gsoc so want to know how to contribute?Thanks in advance -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails

Debugging allauth social authentiacation

Hey, I am trying to include social authentication with google to my site with allauth. There are certain requirements to the site. I am trying to modify the adapters, but modifying a simple adapter is giving the server error. It is not giving what the error is, but just popping a server

Re: Django-Channels: Debugging

Thanks Andrew, using print("message", flush=True) did the trick to get the print messages immediately. Am Dienstag, 30. Januar 2018 02:00:20 UTC+1 schrieb Andrew Godwin: > > I'm not sure why the print messages were buffered - next time try flushing > stdout and see if that makes it work. > >

Re: Django-Channels: Debugging

I'm not sure why the print messages were buffered - next time try flushing stdout and see if that makes it work. Andrew On Mon, Jan 29, 2018 at 6:49 AM, 'Matthias Brück' via Django users < django-users@googlegroups.com> wrote: > Ok, i found the problem, the authentification is not working

Re: Django-Channels: Debugging

Ok, i found the problem, the authentification is not working because of django-tenant-schemas. But I'm still wondering why the print messages only gets output after a restart of the worker. Am Montag, 29. Januar 2018 12:30:54 UTC+1 schrieb Matthias Brück: > > Hi everyone, > > I have added a

Django-Channels: Debugging

Hi everyone, I have added a websocket connection via django-channels to one of my projects. Everything is working fine locally. But when I try to setup everything on my staging server I never come to the point where actually messages got send and received between the clients and the server.

Re: How to: Django development and debugging

2016-10-23 17:08 GMT-06:00 Don Thilaka Jayamanne : > @Luis Zárate > >I dislike VS as IDE but > Please remember, this is Visual Studio Code (cross platform, open source, > free) and not to be confused with Visual Sutdio IDE (full blown IDE runs > only on Windows) > Visual

Re: How to: Django development and debugging

/wiki/Refactoring:-Extract-Method> , Sort Imports <https://github.com/DonJayamanne/pythonVSCode/wiki/Refactoring:-Sort-Imports> ) - Viewing references, code navigation, view signature - Excellent debugging support (remote debugging, mutliple threads, django, fl

Re: How to: Django development and debugging

pport Django there Django is supported today (including template debugging). Right now i'm looking at the need for debugging with auto-reload. Check here for Python Extension and Features <https://marketplace.visualstudio.com/items?itemName=donjayamanne.python> On Monday, 24 October 20

Re: How to: Django development and debugging

ka Jayamanne wrote: >> >> Hi Everyone, I'm the author of a Python plugin for the VS Code editor ( >> https://github.com/DonJayamanne/pythonVSCode). Basically it provides >> intellisense, code navigation, debugging (django, multi threads, etc), data >> science and the lik

Re: How to: Django development and debugging

@Luis Zárate >I dislike VS as IDE but Any particular reason for this? >great if you want to support Django there Django is supported today (including template debugging). Right now i'm looking at the need for debugging with auto-reload. On Mon, Oct 24, 2016 at 3:38 AM, Luis Zárate

Re: How to: Django development and debugging

+2, Don Thilaka Jayamanne wrote: >> >> Hi Everyone, I'm the author of a Python plugin for the VS Code editor ( >> https://github.com/DonJayamanne/pythonVSCode). Basically it provides >> intellisense, code navigation, debugging (django, multi threads, etc), data >&

Re: How to: Django development and debugging

with --no-autoreload parameter, so then works well because when I am debugging I am not coding and I can start or stop the server when I want. I always run django in external terminal when I am coding, I really like the autoreload, I think it's better if the IDE can reload, but I really hate when Aptana

Re: How to: Django development and debugging

isense, code navigation, debugging (django, multi threads, etc), data > science and the like. > > When it comes to debugging django applications, today the extension > disables (doesn't support) live reloading of django applications. > > I'm thinking of having a look at this partic

Re: How to: Django development and debugging

/wiki/Debugging On Saturday, 22 October 2016 05:56:43 UTC+11, Muizudeen Kusimo wrote: > > Hello Folks, > > PyCharm makes debugging Django (and other Python) applications very easy. > Some of the features which are very helpful include: > >1. Ability to choose specific Python

Re: How to: Django development and debugging

isense, code navigation, debugging (django, multi threads, etc), data science and the like. When it comes to debugging django applications, today the extension disables (doesn't support) live reloading of django applications. I take this to mean reload the dev server when code c

Re: How to: Django development and debugging

Hello Folks, PyCharm makes debugging Django (and other Python) applications very easy. Some of the features which are very helpful include: 1. Ability to choose specific Python Interpreter you want to run the code base against. Useful if you use virtualenv and need to test your code

Re: How to: Django development and debugging

> intellisense, code navigation, debugging (django, multi threads, etc), data > science and the like. > > When it comes to debugging django applications, today the extension disables > (doesn't support) live reloading of django applications. > > I'm thinking of having a look at th

How to: Django development and debugging

Hi Everyone, I'm the author of a Python plugin for the VS Code editor (https://github.com/DonJayamanne/pythonVSCode). Basically it provides intellisense, code navigation, debugging (django, multi threads, etc), data science and the like. When it comes to debugging django applications, today

Re: Help debugging static files issue

directory under the project root. > > # Debugging information > OS: Ubuntu 16.04 (4.4.0-31-generic) > Nginx (reverse proxy and serving static file): 1.11.2 > uWSGI (application server): 2.0.13.1 > Django: 1.9.8 > > # Where my debugging left me > In my nginx logs I'm finding reques

Help debugging static files issue

: Static files are not being served correctly, even though they are correctly being collected using the `./manage.py collectstatic`, and placed in a `static/` directory under the project root. # Debugging information OS: Ubuntu 16.04 (4.4.0-31-generic) Nginx (reverse proxy and serving static file

Re: Debugging DJango app on production for High CPU Usage

Integrated new Relic and seems to be good. Thanks for the suggestion. On Monday, February 29, 2016 at 3:20:43 PM UTC+5:30, Lloyd Dube wrote: > > New Relic. > > On Wed, Feb 24, 2016 at 6:59 AM, Web Architect > wrote: > >> Hi, >> >> We have an ecommerce platform based on

Re: Debugging DJango app on production for High CPU Usage

Hi James, Thanks for the detailed explanation. Certainly helps and I would embed logging to debug the CPU usage. Please find my comments inline: On Monday, February 29, 2016 at 2:45:41 PM UTC+5:30, James Schneider wrote: > > > On Tue, Feb 23, 2016 at 8:59 PM, Web Architect

Re: Debugging DJango app on production for High CPU Usage

Hi! I have seen such a behavior on a couple of sites running an older version of Zinnia. It simply hit the 100% CPU usage on some queries. I would also suggest integrating New Relic. It gives you a pretty detailed information on where the CPU is spending most of the time. miercuri, 24

Re: Debugging DJango app on production for High CPU Usage

New Relic. On Wed, Feb 24, 2016 at 6:59 AM, Web Architect wrote: > Hi, > > We have an ecommerce platform based on Django. We are using uwsgi to run > the app. The issue the CPU usage is hitting the roof (sometimes going > beyond 100%) for some scenarios. I would like to

Re: Debugging DJango app on production for High CPU Usage

On Tue, Feb 23, 2016 at 8:59 PM, Web Architect wrote: > Hi, > > We have an ecommerce platform based on Django. We are using uwsgi to run > the app. The issue the CPU usage is hitting the roof (sometimes going > beyond 100%) for some scenarios. I would like to debug the

Re: Debugging DJango app on production for High CPU Usage

The load is low - around 4-5 rps. I don't think that should effect the CPU usage so much. On Friday, February 26, 2016 at 9:57:42 PM UTC+5:30, Nikolas Stevenson-Molnar wrote: > > What sort of load are you experiencing in production? Is it possible that > you're simply running into a hardware

Re: Debugging DJango app on production for High CPU Usage

What sort of load are you experiencing in production? Is it possible that you're simply running into a hardware limitation and need to scale? On Thursday, February 25, 2016 at 9:29:22 PM UTC-8, Web Architect wrote: > > Hi Nikolas, > > Cache backend is Redis. The CPU usage is directly

Re: Debugging DJango app on production for High CPU Usage

Hi Nikolas, Cache backend is Redis. The CPU usage is directly proportional to the load (increases with the increase in load). Memory usage seems to be fine. Thanks. On Friday, February 26, 2016 at 3:32:23 AM UTC+5:30, Nikolas Stevenson-Molnar wrote: > > Which cache backend are you using?

Re: Debugging DJango app on production for High CPU Usage

Which cache backend are you using? Also, how's your memory usage? Do the spikes in CPU correlate with load? I.e., does the CPU use increase/decrease consistently with the number of users? On Wednesday, February 24, 2016 at 10:17:24 PM UTC-8, Web Architect wrote: > > Hi Nikolas, > > I am new to

Re: Debugging DJango app on production for High CPU Usage

Hi Nikolas, I am new to uwsgi. Top is showing CPU consumption by uwsgi. Following is my uwsgi configuration: master=True socket=:7090 max-requests=5000 processes = 4 threads = 2 enable-threads = true #harakiri = 30 (not sure if using this would be a good idea) stats = 127.0.0.1:9191 HW

Re: Debugging DJango app on production for High CPU Usage

Hi Will, In fact thats what I am doing currently. Also, trying to run the load as per the production (similar RPS etc based on reports from ngxtop). But unfortunately not able to generate the CPU usage spike on development (similar to production). Thanks. On Wednesday, February 24, 2016 at

Re: Debugging DJango app on production for High CPU Usage

Hi Javier, I am new to uwsgi. The CPU usage is what top is reporting. Is there a way to optimise uwsgi? Thanks. On Wednesday, February 24, 2016 at 7:06:34 PM UTC+5:30, Javier Guerra wrote: > > On 24 February 2016 at 13:18, Avraham Serour > wrote: > >> sometimes going

Re: Debugging DJango app on production for High CPU Usage

Hi Avraham, Please find my comments inline. On Wednesday, February 24, 2016 at 6:49:29 PM UTC+5:30, Avraham Serour wrote: > > > sometimes going beyond 100% > > how?? > > That's what I am trying to figure out :) > You can use django-debug-toolbar on your development machine, check the > logs

Re: Debugging DJango app on production for High CPU Usage

Hi Asif, The OS is CentOS 6 Linux - HW is a dual core processor. Running Django with uwsgi. uwsgi is configured with 4 processes and 2 threads (no logic behind the numbers but trying to find the optimal combination). I just ran top and was checking the CPU usage. Mostly two instances of uwsgi

Re: Debugging DJango app on production for High CPU Usage

Just to be clear: is is the uwsgi process(es) consuming the CPU? I ask because you mention DB queries, which wouldn't impact the CPU of uwsgi (you'd see that reflected in the database process). On Tuesday, February 23, 2016 at 8:59:28 PM UTC-8, Web Architect wrote: > > Hi, > > We have an

Re: Debugging DJango app on production for High CPU Usage

Hey Web Architect, I guess you never got that DB dump running in development? ;-) Why don't you run some profiling middleware to see if you can some traces of the production system? Or how about New Relic or some such? That's pretty good at helping to identify problems spots in your stack.

Re: Debugging DJango app on production for High CPU Usage

On 24 February 2016 at 13:18, Avraham Serour wrote: >> sometimes going beyond 100% > > how?? if it's what top reports, 100% refers to a whole core. a multiforking server (like uWSGI) can easily go well beyond that. and that's not a bad thing -- Javier -- You received

Re: Debugging DJango app on production for High CPU Usage

> sometimes going beyond 100% how?? You can use django-debug-toolbar on your development machine, check the logs for the pages that take the longest to process and the one that are the most requested and start with those, of course your CPU won't be high but you should check and compare if there

Re: Debugging DJango app on production for High CPU Usage

What is your server configuration and system usage statistics? On Wednesday, February 24, 2016 at 10:59:28 AM UTC+6, Web Architect wrote: > > Hi, > > We have an ecommerce platform based on Django. We are using uwsgi to run > the app. The issue the CPU usage is hitting the roof (sometimes going

Debugging DJango app on production for High CPU Usage

Hi, We have an ecommerce platform based on Django. We are using uwsgi to run the app. The issue the CPU usage is hitting the roof (sometimes going beyond 100%) for some scenarios. I would like to debug the platform on Production to see where the CPU consumption is happening. We have used

Re: Debugging Django with Debug set to False

What I do is to log things in log files. All exceptions are logged in error.log files and I've enabled admin mail which sends me an email whenever there is an exception. So basically logs and emails are quite helpful in debugging and makes it smooth. On Wed, 6 Jan 2016 at 10:20 Web Architect

Re: Debugging Django with Debug set to False

Thanks all for the responses and I would certainly consider them for production level debugging. I understand that application level debugging could be achieved by various logging mechanisms or tools. But one of my main concern is the platform level debugging where in if anything goes wrong

Re: Debugging Django with Debug set to False

If it is the exception tracebacks you are after, consider setting up a Sentry ( https://getsentry.com/ ) server to send the error / exception logs of all your sites to. Whenever something bad happens, it'll show up there, with full tracebacks. Greetings, Remco Gerlich On Mon, Jan 4, 2016 at 6:33

Re: Debugging Django with Debug set to False

Technically speaking, setting DEBUG=False on a production system does not render it un-debuggable. You can still debug and work with such deployments but expect resistance. An ancient approach to debugging ANY production environment is to liberally sprinkle printf (or the django log equivalent

Re: Debugging Django with Debug set to False

You don't say what your front end is. There are ways to use pdb with apache, look for advise on the modwsgi site. But if you are in production, rather than just bringing up the instance that will be production, you may not want to interrupt. Be sure that you can't reproduce the problem in the

Debugging Django with Debug set to False

Hi, Is there a way to debug Django when DEBUG is set to False in settings.py (for example on production)? The reason for asking the above is if we face any issue with DEBUG set to False and if we need to debug. We are new to Django and we are building an ecommerce platform based on Django.

Re: Admin debugging delete

> > Now I think about it, I suspect your way (and now my preferred way) might have been an innovation for Python 3? > > M I don't believe so. I didn't look, but I think that syntax goes back <= 2.6. Pretty sure I've used it in 2.4. I know I've been using it in 2.7 for years. As I mentioned, I'd

Re: Admin debugging delete

On 21/12/2015 6:03 PM, James Schneider wrote: I haven't tested this, but I think that will end up looking for False (the 'not' applying to 'instance' rather than the 'in' operation) in self.deleted_objects, which means saving would be broken entirely. It

Re: Admin debugging delete

> I haven't tested this, but I think that will end up looking for False >> (the 'not' applying to 'instance' rather than the 'in' operation) in >> self.deleted_objects, which means saving would be broken entirely. >> > > It certainly looks nicer. But it didn't break saving so I assume it means >

Re: Admin debugging delete

On 20/12/2015 4:30 PM, James Schneider wrote: > Â Â for instance in instances: > Â Â Â Â if not instance in self.deleted_objects: > Â Â Â Â Â Â instance.modified_by = request.user > Â Â Â Â Â Â instance.save() > > ... but that didn't do anything. Shouldn't that be: if

Re: Admin debugging delete

> for instance in instances: > if not instance in self.deleted_objects: > instance.modified_by = request.user > instance.save() > > ... but that didn't do anything. Shouldn't that be: if instance not in self.deleted_objects: I haven't tested this, but I think

Re: Admin debugging delete

v server I have been digging a little and think this is a javascript initiated event. I am not comfortable with javascript so my uncertainty has just doubled. Thanks very much for any direction Cheers Mike On 17/12/2015 6:41 PM, Mike Dewhirst wrote: I'm havi

Re: Admin debugging delete

I'm having trouble debugging a failed child record Delete. That is the Delete [x] checkbox being ticked does not delete the child record. It is obviously something to do with my bad but I'm not sure where to start. Any hints? Thanks

Re: Admin debugging delete

with javascript so my uncertainty has just > doubled. > > Thanks very much for any direction > > Cheers > > Mike > > On 17/12/2015 6:41 PM, Mike Dewhirst wrote: > >> I'm having trouble debugging a failed child record Delete. That is the >> De

Re: Admin debugging delete

Cheers Mike On 17/12/2015 6:41 PM, Mike Dewhirst wrote: I'm having trouble debugging a failed child record Delete. That is the Delete [x] checkbox being ticked does not delete the child record. It is obviously something to do with my bad but I'm not sure where to start. Any hints? Thanks Mike

Admin debugging delete

I'm having trouble debugging a failed child record Delete. That is the Delete [x] checkbox being ticked does not delete the child record. It is obviously something to do with my bad but I'm not sure where to start. Any hints? Thanks Mike -- You received this message because you

Re: Debugging Django using Pycharm

Here's an article that might help: https://www.jetbrains.com/pycharm/help/run-debug-configuration-django-test.html Also PDB,the python debugger does a very good job of debuuging your Django App. In case you've never used pdb,this should get you started:

Re: Debugging Django using Pycharm

> > Hi Team, > > This is Prabhu just started using Django. > > I would like to know how to debug the code by attaching django application > which is running on server. > > Please share the Pycharm Setting and Steps to be followed. > > If you are recommend any other debug tool that too ok for me. >

Debugging Django using Pycharm

Hi Team, This is Prabhu just started using Django. I would like to know how to debug the code by attaching django application which is running on server. Please share the Pycharm Setting and Steps to be followed. If you are recommend any other debug tool that too ok for me. Thanks and

Re: debugging with pycharm

mething (e.g., *not* on a class/function definition, empty > line, etc.) > > _Nik > > On 4/21/2013 10:14 PM, Mark Lybrand wrote: > > I can't get PyCharm to break at breakpoints when debugging a django app. > what is the magic incantation i neec to invoke to make this happen > regard

Re: Gjango - debugging argument of type <> is not iterable

If I change this to class Meta: *owner = serializers.ReadOnlyField(source='owner.username')* model = UserPrefs fields = ('owner', 'name', 'value') depth = 1 I get a error: {"value":["This field is required."]} -- You received this message because you are

Re: Gjango - debugging argument of type <> is not iterable

Hello, Thanks for responding. I am not sure where in the code this is coming from. I have this code in my view. Not sure if this is the culprit. If it is, what is a better way to access this data. class UserPrefSerializer(serializers.ModelSerializer): class Meta: *owner =

Re: Gjango - debugging argument of type <> is not iterable

No Note: you use 'ReadOnlyField' argument type is error, case modules call of django is incorrect 在 2015年5月29日星期五 UTC+8下午4:43:29，Shekar Tippur写道： > > > Hello, > > Acurl post request is throwing this error: > > Request Method:POSTRequest URL:http://127.0.0.1:8000/setProfile/Django >

Gjango - debugging argument of type <> is not iterable

Hello, Acurl post request is throwing this error: Request Method:POSTRequest URL:http://127.0.0.1:8000/setProfile/Django Version:1.8Exception Type:TypeErrorException Value: argument of type 'ReadOnlyField' is not iterable Exception

Re: Debugging local Django app outside server root

Update: The django app and the django server are both using the same Python interpreter. If I try to set a breakpoint in the app, the breakpoint does not exist warning actually is a local file but is in the remote_sources cache: Connected to pydev debugger (build 135.1057) pydev debugger:

Debugging local Django app outside server root

Is it possible to debug (e.g. stop on breakpoints) an external Django app when running a Django server in a VM via remote debugging in Pycharm? I am able to run and debug the Django server using PyCharm's remote debugger, and the app runs as expected (changes to the local source code

debugging

i got this error when trying to use* pyhto**b**n manage.py syncdb* what does it mean? Traceback (most recent call last): File "manage.py", line 10, in execute_from_command_line(sys.argv) File "/home/user/it/local/lib/python2.7/site-packages/django/core/management/__init__.py", line

Re: debugging

On Wed, Jan 22, 2014 at 10:18 AM, Ankit Singh wrote: > i got this error when trying to use pyhtobn manage.py syncdb what does it > mean? > File > "/home/user/it/local/lib/python2.7/site-packages/django/db/backends/mysql/base.py", > line 17, in > raise

Debugging admin site

I'm using the admin site for editing a model. One of the fields in the model is readonly when editing. But when try to save the model while editing django gives the error "Please correct error below" and does not give a clue about where the error happens. I know the cause is the readonly field

Re: debugging with pycharm

I hope not :( I will check template debugging tomorrow. I have already started looking at WingIDE as an alternative, but would much prefer to stick with PyCharm, since I am familiar with other JetBrain products. On Mon, Apr 22, 2013 at 9:49 PM, Ezequiel <ediazpach...@gmail.com>

Re: debugging with pycharm

On Monday, April 22, 2013 3:03:11 PM UTC-3, Mark Lybrand wrote: > > It would appear that this was broken in 2.7.1. When I upgraded to 2.7.2 > my breakpoints once again work as expected. > I think in 2.7.1 the BP did not work if you set them after running server, on 2.7.2 is fixed. But in

Re: debugging with pycharm

r > isn't still running. Also, make sure your break point is on a line a line > which does something (e.g., *not* on a class/function definition, empty > line, etc.) > > _Nik > > > On 4/21/2013 10:14 PM, Mark Lybrand wrote: > > I can't get PyCharm to break at breakpoi

Re: debugging with pycharm

get PyCharm to break at breakpoints when debugging a django > app. what is the magic incantation i neec to invoke to make this > happen regardless of where i am in code (views, urls, models, > templates, etc) > > -- > Mark :) > -- > You received this message because you a

debugging with pycharm

I can't get PyCharm to break at breakpoints when debugging a django app. what is the magic incantation i neec to invoke to make this happen regardless of where i am in code (views, urls, models, templates, etc) -- Mark :) -- You received this message because you are subscribed to the Google

Re: debugging issues with settings.py and database (postgres) and syncdb

Yes indeed! That was it. I am following a tutorial for getting things running on a Heroku platform and that seems to be something special for that environment. Thank you!! On Thursday, December 27, 2012 12:52:57 PM UTC-5, donarb wrote: > > On Thursday, December 27, 2012 8:51:11 AM UTC-8, Dan

Re: debugging issues with settings.py and database (postgres) and syncdb

On Thursday, December 27, 2012 8:51:11 AM UTC-8, Dan Richards wrote: > > Yeah, psycopg2 is definitely installed... > I noticed that you are using djcelery (which I know nothing about), but have you tried getting everything working without it first? There's a line in your settings that says

Re: debugging issues with settings.py and database (postgres) and syncdb

On Thursday, December 27, 2012 8:51:11 AM UTC-8, Dan Richards wrote: > > Yeah, psycopg2 is definitely installed... > > On Thursday, December 27, 2012 9:03:31 AM UTC-5, ke1g wrote: >> >> >> >> On Thu, Dec 27, 2012 at 8:26 AM, Dan Richards wrote: >> >>> Hmmm...well that isn't

Re: debugging issues with settings.py and database (postgres) and syncdb

On Thu, Dec 27, 2012 at 11:51 AM, Dan Richards wrote: > Yeah, psycopg2 is definitely installed... > It sounds like it may be time to insert: import pdb;pdb.set_trace() at the point where the exception gets raised. Looking at variables that it doesn't like, and looking

Re: debugging issues with settings.py and database (postgres) and syncdb

Yeah, psycopg2 is definitely installed... On Thursday, December 27, 2012 9:03:31 AM UTC-5, ke1g wrote: > > > > On Thu, Dec 27, 2012 at 8:26 AM, Dan Richards > wrote: > >> Hmmm...well that isn't working either - same error. My method for >> verifying it's picking up the

Re: debugging issues with settings.py and database (postgres) and syncdb

On Thu, Dec 27, 2012 at 8:26 AM, Dan Richards wrote: > Hmmm...well that isn't working either - same error. My method for > verifying it's picking up the right settings.py is by putting a syntax > error in the settings.py it should be using and seeing that it generates an >

Re: debugging issues with settings.py and database (postgres) and syncdb

Hmmm...well that isn't working either - same error. My method for verifying it's picking up the right settings.py is by putting a syntax error in the settings.py it should be using and seeing that it generates an error. This is the settings.py file in the directory below my app directory and

Re: debugging issues with settings.py and database (postgres) and syncdb

Ok. I would try setting the ENGINE value to *sqlite3* and try running *syncdb *again. If that works (which it should), then we can presume it's a configuration access problem with the DB. On 26 December 2012 13:18, Dan Richards wrote: > NO, just me messing around that it

Re: debugging issues with settings.py and database (postgres) and syncdb

NO, just me messing around that it made no difference. I have the db access to all and trust and the error doesn't change no matter what I use there. It feels like it could be a permissions problem, but I don't know how to track it down other than to verify I can access postgres via psql

Re: debugging issues with settings.py and database (postgres) and syncdb

Are the user and password fields meant to be blank? Cheers, Ryan On Dec 26, 2012, at 9:40 AM, Dan Richards wrote: > First off, I am a newbie to django, python and postgres - so I suspect I am > missing something obvious, but I am stumped. Any ideas will be gratefully >

debugging issues with settings.py and database (postgres) and syncdb

First off, I am a newbie to django, python and postgres - so I suspect I am missing something obvious, but I am stumped. Any ideas will be gratefully accepted... I get the popular "Improperly configured settings.DATABASES" error message when I run syncdb on my test app. I am running: django

Re: Hard time debugging an strange problem

Al 31/08/12 18:26, En/na Tomas Neme ha escrit: I'd like to see some of your management commands' code. It smells somewhat like you're running a shell subprocess and not waiting for it to be done before going on to the next thing Thanks for taking the time to answer. I've thought on this. On

Re: Hard time debugging an strange problem

Hi again, doing some more testing I've realized that the problem happens because the .py and .pyc files are out of sync. My guess is that the .py files are modified so quickly that the timestamp does not change and a recompilation is not triggered. After some research I've found that the

Re: Hard time debugging an strange problem

I'd like to see some of your management commands' code. It smells somewhat like you're running a shell subprocess and not waiting for it to be done before going on to the next thing -- "The whole of Japan is pure invention. There is no such country, there are no such people" --Oscar Wilde

Hard time debugging an strange problem

Hi all, sorry for the ambiguous subject, but I can't summarize it in a few words. This is my first message to the list asking for help so I think that is polite to give a big thanks to those of you that are making developing with django such a great pleasure. This is a great community. Said

IntelliJ IDE, Running & Debugging Tests

Hi - Has anyone managed to run/debug their tests in IntelliJ IDE? If so, are there any specific tricks to the launch configurations, IDE setup, or version. Any information you have would be very helpful. Thanks, TE -- You received this message because you are subscribed to the Google Groups

Error while debugging the code in "class file editor source not found" in Runtime.class file

Dear All, I am facing the problem as "class file editor source not found" in Runtime.class file, while running the code in eclipse on android could any body please do the needful in proceeding further As am new to this, pls help me as soon as possible, Thanks, Srinivasan S -- You received

Re: Disable debugging for all, but allow debug toolbar for one host

On 11/07/2011 12:49 PM, Tom Evans wrote: > On Sun, Nov 6, 2011 at 12:30 AM, Gelonida N <gelon...@gmail.com> wrote: >> Hi, >> >> If I understood well, then the Django debug toolbar is only working if >> debugging is enabled. >> >> What I wanted to

Re: Disable debugging for all, but allow debug toolbar for one host

On Sun, Nov 6, 2011 at 12:30 AM, Gelonida N <gelon...@gmail.com> wrote: > Hi, > > If I understood well, then the Django debug toolbar is only working if > debugging is enabled. > > What I wanted to do is is to disable the explicit django error messages > for all

Disable debugging for all, but allow debug toolbar for one host

Hi, If I understood well, then the Django debug toolbar is only working if debugging is enabled. What I wanted to do is is to disable the explicit django error messages for all but one specific IP address and to disable the django debug toolbar for this one address. -- You received

Re: Question about "Django 1.1 Testing and Debugging" Book for Karen

Hi Karen, Ah, very sorry - my mistake! The machine I was using had an old version of python and it was using django 1.0. So that's why it didn't create tests.py, and I just assumed there must be a bunch of changes between 1.1 and 1.2. Ok, mystery solved. Thanks for your explanation of the

Re: Question about "Django 1.1 Testing and Debugging" Book for Karen

On Thu, Apr 28, 2011 at 6:18 PM, Margie Roginski wrote: > > I have a bit of time on my hands and was going to run through your > book to cement my understanding of the best way to test. I started > out and was immediately confronted with the fact that there seem to be >

  1   2   3   4   >