Path: csiph.com!optima2.xanadu-bbs.net!xanadu-bbs.net!nntp.club.cc.cmu.edu!micro-heart-of-gold.mit.edu!newsswitch.lcs.mit.edu!nntp.TheWorld.com!newsfeed-00-ls.mathworks.com!panix!not-for-mail
From: Grant Edwards <invalid@invalid.invalid>
Newsgroups: comp.lang.python
Subject: Re: Reason for not allowing import twice but allowing reload()
Date: Wed, 2 Mar 2016 15:15:29 +0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Lines: 29
Message-ID: <nb702h$n4$1@reader1.panix.com>
References: <645cdd46-d4a4-49b3-a0d8-848608d70d73@googlegroups.com> <mailman.8.1456729298.2321.python-list@python.org> <56d57aa4$0$1586$c3e8da3$5496439d@news.astraweb.com> <CAPTjJmoWMfW-5Pn=ZpcDp8nmAfYbHuAWea3T2mhRRi+_+hcyXA@mail.gmail.com> <CALwzidnUsX9HftTzk-5BqA_tNK0qCxi=zOmBWGWAS5mZzi3VzQ@mail.gmail.com> <CALwzidk49ZWX1ruHtVuhWQOumVmXJ0iV4zy1r-q1ny-Q8V6ygQ@mail.gmail.com> <CAPTjJmq_pB+CDBiH96o7SAsMVpK+Nfu5uuSh_sywuehE=cCE4Q@mail.gmail.com> <mailman.86.1456871434.20602.python-list@python.org> <56d63fb0$0$1618$c3e8da3$5496439d@news.astraweb.com> <mailman.90.1456885378.20602.python-list@python.org>
NNTP-Posting-Host: 67-130-15-94.dia.static.qwest.net
X-Trace: reader1.panix.com 1456931729 740 67.130.15.94 (2 Mar 2016 15:15:29 GMT)
X-Complaints-To: abuse@panix.com
NNTP-Posting-Date: Wed, 2 Mar 2016 15:15:29 +0000 (UTC)
User-Agent: slrn/1.0.2 (Linux)
Xref: csiph.com comp.lang.python:103876

On 2016-03-02, Ian Kelly <ian.g.kelly@gmail.com> wrote:

> Software updates? The nice thing about *nix systems is that *most*
> updates don't require a reboot. I'm still going to reboot any time
> there's a kernel update though, and those are fairly frequent. I could
> read the patch notes to determine whether this new kernel version is
> actually important, but it takes less of my time just to go ahead and
> reboot.

I try to remember to reboot every couple weeks or so even without a
kernel update.  There sometimes updates to things like the "rc" stuff
or udev or whatnot which occasionally cause boot-time problems.  If
you let too much time go by between reboots, and something that
happend several months ago is going to cause a problem at boot time,
that reboot is guaranteed to happen when it's the most inconvenient.
And it's a lot easier to figure out the problem when it's due to a
recent update.

> With my company-owned Macbook Air, the security policy will
> eventually schedule a *forced* reboot when there are "critical"
> updates to be installed. Thankfully the scheduler is pretty good
> about making sure it's not catching the user at an inopportune
> moment.


-- 
Grant Edwards               grant.b.edwards        Yow! Let's all show human
                                  at               CONCERN for REVERAND MOON's
                              gmail.com            legal difficulties!!