Opened 16 years ago

Closed 16 years ago

Last modified 14 years ago

#11316 closed (fixed)

Changeset [10966] broken python 2.3 support

Reported by: Kyle Fuller Owned by: Kyle Fuller
Component: Database layer (models, ORM) Version: dev
Severity: Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

"FutureWarning: x<<y losing bits or changing sign will return a long in Python 2.4 and up"

Changeset [10966] used 1<<32 which will return 0 in python 2.3, and 4294967296L in newer versions. I have simply changed 1<<32 and hard coded the value in (4294967296L)

Attachments (1)

301ab5fb6095ef19c1c0cb12a3879e597d2317ee.diff​ (562 bytes ) - added by Kyle Fuller 16 years ago.
Patch attached and on my git repo at github ​http://github.com/kylef/django/commit/301ab5fb6095ef19c1c0cb12a3879e597d2317ee

Download all attachments as: .zip

Change History (4)

comment:1 by Alex Gaynor, 16 years ago

milestone: 1.0.3 → 1.1
Triage Stage: Unreviewed → Accepted
Version: 1.0 → SVN

by Kyle Fuller, 16 years ago

Attachment: 301ab5fb6095ef19c1c0cb12a3879e597d2317ee.diff​ added

Patch attached and on my git repo at github ​http://github.com/kylef/django/commit/301ab5fb6095ef19c1c0cb12a3879e597d2317ee

comment:2 by Gary Wilson, 16 years ago

Resolution: → fixed
Status: new → closed

(In [11004]) Fixed #11316 -- Fixed a Python 2.3 compatibilty issue with [10966] (in Python 2.3 on 32-bit machines, 1<<32 is 0). Thanks to kylef for the report and patch.

comment:3 by Jacob, 14 years ago

milestone: 1.1

Milestone 1.1 deleted

Note: See TracTickets for help on using tickets.
Back to Top