<set_>
@zmatt: Did you see my updated pathlib thing?
<zmatt>
that's probably because you've never been tasked to figure out how to get <this>, <that>, <that>, and <that> functionality pinned out of some SoC or microcontroller and having to figure out how to get all of that using the obnoxiously constrained pinmux options of that SoC/microcontroller
<set_>
Slowly will a man learn to be a boy and grow again?
<set_>
I have not used the other available functions yet but I will/might learn how to use them soon.
<zmatt>
it looks like it makes no sense whatsoever and you've just copy-pasted some random bits of totally unrelated python code and put them into a blender to create some kind of disgusting smoothie
<set_>
Well, w/ your education in this dept, yes. You make more since and can articulate things better in source.
<set_>
since = sense
<set_>
I am still just a learner thinkin' of ways to handle source that is already available.
<set_>
Speakin' of learnin'. My hard drive crashed.
<set_>
Boo.
<set_>
it is basically new and under warranty.
<set_>
Phew.
<set_>
Anyway...
<set_>
@zmatt: Are you saying do not add the functions from pathlib for use in case I want to use them?
<zmatt>
but you weren't "using source already available", even if perhaps you copied bits of code from random sources (evidently unrelated to task at hand), the resulting nonsense in your files is genuinely all your own :P
<zmatt>
I have no idea what you're even saying
<set_>
Okay. in pathlib.py, there are classes and functions that are available for use in source.
<set_>
Why not use more than just write_text?
<zmatt>
because none of those functions are useful in this situation?
<set_>
oh.
<set_>
Right, but I can learn new things that may be useful in different situations.
<set_>
like globbing in Linux, glob is a file in python3.
<zmatt>
sure, but that requires that the functionality is actually useful in the situation you're applying it
<zmatt>
otherwise nothing is achieved and nothing is learned
<set_>
Oh. Right...my query is this idea: Should I make things easy to understand or harder to grasp in case random people view my work?
<zmatt>
nobody who reads your code has any idea what it does
<zmatt>
at least this particular python code (and most python code I've seen from you)
<set_>
Hhaha. You are probably right.
<set_>
So, what if one day, ONE DAY, I come up w/ something of use?
<zmatt>
like, your MySecond.py and MySecond_Test.py ... like 90% of it I have not the slightest clue what it could possibly be trying to achieve
<set_>
Oh. It has to do w/ unfinished business or WIP.
<set_>
So, I am building the flow slowly.
<zmatt>
no, that's not the problem
<set_>
Oh.
<set_>
What is the problem?
<zmatt>
I honestly can't tell, other than "you" ... it just doesn't seem like, even after all this time, you have any sort of mental model of what a line of python code actually does
<zmatt>
I guess
<set_>
No issue. If you cannot be more hateful in your journey in life as it pertains to me and my source, sobeit.
<set_>
I accept the niceness.
<set_>
jp1 heh?
<zmatt>
or whatever relay
<set_>
I know.
<set_>
You just mentioned something earlier that made me think.
<zmatt>
this isn't using gpiod so that concern doesn't exist
<set_>
Oh.
<set_>
Okay.
<set_>
So, the issue w/ the jp1/2 is only for libgpiod.
<set_>
Which you utterly hate.
<zmatt>
I think hate is a strong word, but it's just in many ways worse than sysfs gpio
<set_>
Okay. No hating. Just disliking. It has so many more functions!
<zmatt>
I mostly just don't want *you* messing with it since that's just asking for trouble
<set_>
Okay.
<set_>
Fine.
<set_>
I know people in the community of Open Source dislike me. I am okay w/ this idea. But, this does not mean I should stop, cease, halt, shutdown, or zilch my understandings of code, hardware, and the combination of the two.
<zmatt>
certainly not, but maybe try to focus a bit more
<set_>
Forget focusing. I need a real education in this matter "a bit more."
<set_>
I am old now.
<set_>
I mean, literally, does PWM on the BBB still work?
<zmatt>
yes
<set_>
Oh.
<set_>
Hmm. This one person from github and forums says that the newer kernels take the path of pwm away from his boards.
<zmatt>
though some versions of the bb-customizations package have a broken udev rule that neglects to export the pwms
<set_>
Aw.
<set_>
I remember why now.
<set_>
It is for a backlight.
<set_>
Right.
<zmatt>
(because of compatibility issues.. for which I've proposed a solution but it hasn't been implemented yet)
<set_>
Oh.
<zmatt>
what person on the forums?
<set_>
Hmm. I think kiosk mode is neat but...oh. Hold on.