This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients alexandre.vassalotti, belopolsky, bpb, brett.cannon, ehuss, facundobatista, fmitha, georg.brandl, gvanrossum, jafo, jaraco, jarpa, kylev, loewis, lukasz.langa, nnorwitz, pitrou, sbt, taleinat, tseaver, vstinner, zbysz, zseil
Date 2012-07-26.23:23:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1343344868.3697.0.camel@localhost.localdomain>
In-reply-to <1343344599.32.0.530948449101.issue1692335@psf.upfronthosting.co.za>
Content
> I think there are two options simple enough to sneak in to 3.3:
> 
> (1) The trivial patch of initially setting self->args in __new__().
> 
> (2) Georg's idea of additionally setting a __newargs__ attribute in
> __new__() and using it in __reduce__().  However, I would store
> __newargs__ directly in the struct to avoid always triggering creation
> of a dict for the instance.

At this point of the release process, the trivial approach sounds safer
to me (but is it?).
History
Date User Action Args
2012-07-26 23:23:17pitrousetrecipients: + pitrou, gvanrossum, loewis, nnorwitz, brett.cannon, georg.brandl, facundobatista, jafo, ehuss, tseaver, jaraco, belopolsky, zseil, fmitha, vstinner, taleinat, alexandre.vassalotti, jarpa, bpb, zbysz, kylev, lukasz.langa, sbt
2012-07-26 23:23:16pitroulinkissue1692335 messages
2012-07-26 23:23:16pitroucreate