The Communication Cube

[ClockworkCoder]

It's Idoha's birthday tomorrow. If I don't survive please make sure I get a decent burial.

It was nice knowing you. What would you like as an epitaph?

 

[Null]

What would you like as an epitaph?

BRB

 

[Kev2442]

What would you like as an epitaph?

"Life ? Don't talk to me about life."

 

[ClockworkCoder]

"Life ? Don't talk to me about life."

Lol, thanks Marvin.

 

[Klumpen]

 

[Klumpen]

twitter.com/myhtopoeic/status/980264924927717377

 

[Caine]

I suspect that Goebbels and al-Sahhaf would be proud and/or jealous of that one.

 

[Null]

 

[Kev2442]

I'd like to like, but who'd like the idea of @Uncle Jack being dead ?

 

[Null]

but who'd like the idea of @Uncle Jack being dead ?

Idoha: I would.

Spoiler

j/k

 

[Null]

 

[Null]

I wanted to stop the 2nd hard drive in my laptop from going to sleep when it felt like it, so I came up with the following affront to humanity.

import time

secs = time.time()
secstr = str(secs)

while True:
    tf = open("seconds","w")
    tf.write(secstr)
    tf.close()
    time.sleep(10.0)

It writes the number of seconds since 00:00:00 1/1/1970 to a text file called seconds in my documents folder every 10 seconds (or thereabouts).

 

[Caine]

Python file objects are context managers. This allows you to write:

import time

secstr = str(time.time())

while True:
  with open("seconds", 'w') as tf:
    tf.write(secstr)
  time.sleep(10.0)

This is slightly cleaner, explicitly communicates the file scope and ensures that the file object is always closed, even when exceptions occur.

 

[Null]

Thanks for the tip. Looks like someone needs more practice.

 

[Caine]

Thanks for the tip. Looks like someone needs more practice.

Yeah, I know... I'm working on it. I will learn eventually

When people come from other languages, the python context managers are often overlooked. They are such a powerful feature, great for resource acquisition, locks, transactions, etc. I think it was PEP 343 where they were introduced.

 

[ible]

that keeps writing the same number of seconds to the file, from when the python program was first opened. (secstr is a constant.)

which i suppose still accomplishes your goal, but you could just write in "a", over and over again, with the same effect.

 

[Caine]

Yep, I noticed that too. It is a bit of a weird choice for a string constant unless you want to log when you last started this application. Still, I suppose it works for the stated purpose.

 

[Null]

but you could just write in "a", over and over again, with the same effect.

Seems like all that may be needed is to keep writing a blank text file to the drive in question. https://stackoverflow.com/a/600211

Edit: New method (blank text file) seems to be working fine so far.

Edit 2: Batch file because why not.

@echo off
:start
copy NUL D:\nsleep.txt
del D:\nsleep.txt
TIMEOUT /T 10 /NOBREAK
goto start

 

[Caine]

Sounds like Lunduke is having some great fun offline.


I should try some of that. Too much not important/non urgent stuff in my life these days.

 

[ible]

would touching a file do the same thing?

that should update the timestamp, which affects the harddrive:

while [ 1 ]; do sleep 10; touch ~/file; done