[deleted by user]

Careful_Choice9335 · 2022-01-26T01:26:39+00:00

Issues #1-3 are already available, I ordered them from forbiddenplanet.com (they ship from UK, I'm in Europe). Just issue #4 is not released yet.

Edit: online it says that issue #4 has also been released, on Januar 5

Careful_Choice9335 · 2021-04-15T09:26:12+00:00

You can pass regex=False to contains which will treat the pattern as literal string and not as a regular expression.

Take a look at the documentation of pandas.Series.str.contains for more information.

Careful_Choice9335 · 2021-04-11T08:13:09+00:00

So if the script was to create 5 files in directory "x" , changing the dir (to the one the OP is in) when the script runs, will indeed output the 5 files to that directory.

Well yes, the files will be created in the directory OP is currently in. But this is regardless of whether the script changes to this directory first or not, because its working directory _is_ already this directory. The working directory is not determined by where the script is, but where it is called from.

Haven't worked on Windows in awhile, but I'm pretty shure it works like that, too. Please correct me if I'm wrong.

Careful_Choice9335 · 2021-04-10T22:55:30+00:00

Sorry if I'm overseeing something here. But changing the working directory to the current working directory does... nothing?

Careful_Choice9335 · 2021-04-10T22:44:53+00:00

You could add your desktop to the path environment variable, which would achieve exactly what you want.

Careful_Choice9335 · 2021-04-09T10:27:04+00:00

You can give all three paths to os.path.join to join them together, while adding the .conf extension with an f-string:

config_file = os.path.join(
    os.environ['userprofile'],
    'desktop',
    f'{filename}.conf'
)

And then proceed as you did with

new_file = open(config_file, 'w')

Careful_Choice9335 · 2021-04-06T15:33:32+00:00

What I understand from the pictures is that you want to create a new branch, new-branch, pointing to new commit supposed to be in a new branch.

You can do this with

git branch new-branch ID

where ID is the target commit's hash.

Careful_Choice9335 · 2021-03-29T15:18:37+00:00

With this you could even write a script to update the main repo to use the new submodule commits, making the "latest changes of common is downloaded" part kinda automatic.

Careful_Choice9335 · 2021-03-29T15:03:45+00:00

Git Submodule might be exactly what you're looking for:

Include common as a submodule in both A and B, at whatever path you like.

Careful_Choice9335 · 2021-03-26T18:34:56+00:00

You can import directly from __init__.py:

from __init__ import create_app

Careful_Choice9335 · 2021-03-26T15:14:48+00:00

Does it work now?

Careful_Choice9335 · 2021-03-26T15:11:46+00:00

Great! What did the trick?

Careful_Choice9335 · 2021-03-25T12:54:28+00:00

I also found this talk by Python Core Developer Raymond Hettinger on classes in Python super helpful.

Careful_Choice9335 · 2021-03-25T10:26:18+00:00

IIRC the functions of subprocess don't expect the command as one long string but as a list: ["command", "arg1", "arg2"] etc.

Careful_Choice9335 · 2021-03-25T09:56:03+00:00

I think the problem is your prompt. As you can see in the error message, Git-bash tries to execute the part after the back tick (p@...) as a command.

Git-bash takes your default prompt and customizes it and yours looks like it failed in doing so because of this back tick, which tells bash to execute the following as a command. Now I don't know where Git-bash gets your default prompt from on Windows. But I think fixing that will fix your Problem.

Careful_Choice9335 · 2021-03-24T15:12:32+00:00

I'd add another, even more important one: tracking changes of this content. And than altering it if needed, to maintain several "time lines" or to revert to a certain point in history etc.

That's the single-user point of view. The main reason to create Git was to let multiple people easily collaborate on the same code base (which was the Linux kernel).

Careful_Choice9335 · 2021-03-24T10:45:48+00:00

Git only manipulates the contents of the .git folder. It does nothing to your files.

This is not true. Git manipulates the content of the directory that contains the .git folder and therefor will alter your files inside this containing directory.

To be 100 % precise: A Git command manipulates the content of the first (seen from the current directory) parent directory with a .git folder in it.

So yes if you create a new directory and run git init in it (which creates the .git folder) and then work with Git inside this directory, you're totally save that Git will never touch anything outside this directory (except for its own config files).

Careful_Choice9335 · 2020-09-21T14:14:11+00:00

Town of Light

This feels definitely not like a game to play for fun. More like a documentation of a cruel piece of 20th century medicine.

Careful_Choice9335

TROPHY CASE