Reason for not allowing import twice but allowing reload()

[Ian Kelly]

On Tue, Mar 1, 2016 at 6:19 PM, Steven D'Aprano <steve at pearwood.info> wrote:
> On Wed, 2 Mar 2016 09:29 am, Ian Kelly wrote:
>
>> There's a big difference between
>> that and clocking a year of uptime just because you can, though.
>
> What other reason is there for having a year of uptime?
>
> It's not like it is difficult. My laptop doesn't actually go anywhere: for
> historical reasons, it's a laptop but it is (mostly) used as a desktop. It
> sits on my desk. If there's a power outage, the handy built-in UPS
> (battery) keeps it alive for an hour or two. I come in, I nudge the mouse
> to wake xscreensaver and authenticate; I do my work; then I run
> xscreensaver to lock the screen and leave.
>
> If I need access to something from home, I can SSH into the office network,
> and from there into the laptop.
>
> The OS is as stable as the surface of the moon, and simply doesn't crash or
> go down ever. (If only Firefox was as good, alas, but when it does crash it
> is nearly always because I've allowed Javascript to run on some popular,
> multimedia-rich, information-free website.) I don't reboot because I don't
> need to reboot. Why would you reboot just for the sake of rebooting?

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.

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.