#8313 closed (worksforme)
rev 8340 crashes python on OS X Leopard
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I'm using OS X Leopard (10.5.4) and Postgres 8.3 w/ psycopg2. After updating past revision 8340, psycopg2 causes my Python 2.5 to crash consistently. I tried flushing the database and loading my fixtures from scratch. It crashed no matter what I tried. I noticed there were several fixes related to sessions. I suspect the fact that I was still logged in had something to do with why _psycopg2.so was crashing python.
I backed the changes out to 8339 and I was able to work again and I was prompted to log in.
Change History (5)
comment:1 by , 16 years ago
| milestone: | → 1.0 beta |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 16 years ago
Removing .pyc files and cleaning out sessions/cookies seems to help in my case.
comment:3 by , 16 years ago
I wouldn't have thought you'd need to clean out cookies, since nothing changed in the format we use to read/write cookies. Those changes should all be fully backwards compatible for that type of use-case.
Leaving open until I can get confirmation from the other reporter that it's old .pyc files or something similar.
comment:4 by , 16 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
I just looked over the shoulder of a co-worker running the exact same setup and Django trunk (r8346) and he was able to use sessions on a fairly complex application without trouble, too. So I'm suspicious of the older .pyc files here. Closing as "works for us" for now. If somebody repeats it and has traceback info and details, we can explore further.
"It crashes" doesn't tell us what was going on at the time. Is there a traceback you can provide? If not, how do you know it crashed?
I've seen a couple of people report this now and am yet to see details that I can use to diagnose the problem, so any information gratefully received.