#10930 closed (invalid)
int_alias UnboundLocalError exception in query.py (reported by Wingware IDE defaults)
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 1.1-beta |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
using latest wingware IDE which always reports UnboundLocalError exceptions by its default preferences, immediatelly during first application access to started devserver I discovered this small waste annoyance in code - I had ignored this error location according to this thread:
http://groups.google.com/group/django-developers/browse_thread/thread/a5432ea21c40b667#,
but today it occured again during debugging deeper in this code, so I decided to report it with quick patch.
IMHO its better to have this ugly annoyance solved.
Attachments (1)
Change History (4)
follow-up: 2 comment:1 by , 15 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
by , 15 years ago
| Attachment: | patch.diff added |
|---|
comment:2 by , 15 years ago
Replying to mtredinnick:
There is no bug in Django here. Certainly the variable is potentially used unbounded and we handle that case on the very next line, which is fine.
Ok :), it's only "first impression issue" while using ide with this exceptions forced by defaults. After many hours of debugging, this is only one place where something like this occured for me. Hope for 1.1 soon anyway :) thanks for support
There is no bug in Django here. Certainly the variable is potentially used unbounded and we handle that case on the very next line, which is fine.