[Python-Dev] Python 2.3a1's mandatory use of cyclic GC causes existing applications to fail (original) (raw)
Kevin Jacobs jacobs@penguin.theopalgroup.com
Thu, 6 Feb 2003 15:06:08 -0500 (EST)
- Previous message: [Python-Dev] Python 2.3a1's mandatory use of cyclic GC causes existing applications to fail
- Next message: [Python-Dev] Python 2.3a1's mandatory use of cyclic GC causes existing applications to fail
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, 6 Feb 2003, Guido van Rossum wrote:
Hm... Given this feedback, it sounds like the only way to implement Christian's suggestion in a backwards-compatible way would be to use a different xxx name, e.g. fields. I also like the suggestion of allowing control over the order as well.
Not to be difficult, but I already use 'fields' for the same purpose as dictionaries assigned to slots for non-slot attributes.
(Yes, I know that this means nothing, since xyz names are fair game, though I think it is extremely funny that fate is trying to kill my ConatraintObject metatype)
-Kevin ;)
--
Kevin Jacobs The OPAL Group - Enterprise Systems Architect Voice: (216) 986-0710 x 19 E-mail: jacobs@theopalgroup.com Fax: (216) 986-0714 WWW: http://www.theopalgroup.com
- Previous message: [Python-Dev] Python 2.3a1's mandatory use of cyclic GC causes existing applications to fail
- Next message: [Python-Dev] Python 2.3a1's mandatory use of cyclic GC causes existing applications to fail
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]