my_scripts | python scripts that help in automating boring tasks | Automation library

You can use Path.stem to get the name of a file without the extension

__file__ is the full path to the current file which you can pass to Path

First Solution:

Try replacing ~/mytools/my_scripts with /home/your_username/mytools/my_scripts in your .profile OR use $HOME variable instead like this.

The reason Git is confused here is simple enough, but before we get there, let me address a red flag here:

The merge conflict UI ...

Git does not have a merge conflict UI.¹ This leads to lots of people adding different ones, each of which has a different method of presenting the conflict. It's helpful to know that Git itself provides only two things here:

• First, Git provides all three input files. We'll look at this more in a moment. These three files are all invisible: you can't see any of them. You have to have Git extract them for you. The various UIs that people add usually do this, but, well, see "different method of presenting".

• Last, Git also provides, in your working tree, its own best effort at merging, marked up with conflict markers. The default conflict marker style is called merge style and it shows lines from two of the three input files. The other conflict marker style available is called diff3 and it shows lines from all three of the three input files. I find this style superior, though you still need to know about the three input files.

¹You can call these two things that Git provides a UI, but ... that takes us back to a quote attributed to Abraham Lincoln. The quote says that Lincoln asked how many legs a dog has, if you call a tail a leg. The obvious answer is 5, to which the reply is: "ah, but calling a tail a leg doesn't make it one." According to the link here, Lincoln did say this, but about a calf, not a dog.

The git rebase command works, in principle and sometimes in reality, by repeatedly invoking git cherry-pick. Git's git-cherry-pick documentation describes cherry-pick in a sentence as:

Given one or more existing commits, apply the change each one introduces, recording a new commit for each.

(The rebase code does one at a time, for extra control, so we can disregard the "or more" part.) "Apply the changes ... and make a new commit" means, to me, to copy some existing commit. What's missing here—but is strongly hinted-at—is that this "apply the changes" is actually a merge operation:

... See git-merge(1) for some hints on resolving such conflicts.

A merge operation involves three commits. So: what are the three commits here? Well, one is obvious: we have to tell git cherry-pick which commit we want it to copy, as in:

If you are trying to add your script in your backend you should use this:

The issue should be with the URL, it must be absolute I think.

It would be easier to just specify the full path to the file in the head of your html document, example;

WordPress provides hooks to enqueue scripts properly.

You might have called the enqueue method directly. It should be in action callback of wp_enqueue_scripts hook.

Pipes don't know about "lines". Bytes go in on one end, and the same bytes in the same order come out at the other end. There is a little bit of (configurable) buffer in between, but when working with them, consider them being unbuffered.

And line oriented I/O happens at a higher level, e.g. when creating a C stdio FILE object on a pipe file descriptor, or using a readline library (or similar). Or – like in your case – Python stdio print, writelines and readline.

EDIT 1:

Here are two simple python programs

writer.py

You basically have this situation, where at the end of each iteration you output something. You keep doing this because you don't know when you'll get to the last element.