Question About When Objects Are Destroyed (continued)
Grant Edwards
grant.b.edwards at gmail.com
Mon Aug 7 10:56:20 EDT 2017
On 2017-08-05, Tim Daneliuk <info at tundraware.com> wrote:
> On 08/05/2017 03:21 PM, Chris Angelico wrote:
>> so the object's lifetime shouldn't matter to you.
>
> I disagree with this most strongly. That's only true when the
> machine resources being consumed by your Python object are small in
> size. But when you're dynamically cranking out millions of objects
> of relatively short lifetime, you can easily bump into the real
> world limits of practical machinery. "Wait until the reference
> count sweep gets rid of it" only works when you have plenty of room
> to squander.
I've been writing Python applications for almost 20 years. I've never
paid any attention _at_all_ (none, zero) to object lifetimes, and it's
never caused any problems for me. Admittedly they didn't involve
gigabytes of data, but many of them ran for days at a time...
--
Grant Edwards grant.b.edwards Yow! Jesuit priests are
at DATING CAREER DIPLOMATS!!
gmail.com
More information about the Python-list
mailing list