Python2 | - File Backup | Continuous Backup library

Try using, cmd ="py C:\Python27\Tools\Scripts\\2to3.py "+file_path+" -w"

If all you need is to ensure that the Source Code Encoding Heading and the 4 import statements are present, then the following script will recursively descend through a directory modifying all .py files ensuring that these the required statements are present. The updates will be done in place, so it could be wise to make sure that you have a backup in case of a hardware failure in the middle of rewriting one of the files. Even if the code is rewritten to write to a temporary file and then do a final "move" to replace the old with the new, the same problem remains.

You should try this out on experimentally first in a test directory, and as always, USE AT YOUR OWN RISK.

I've tried to duplicate your problem with a fresh Debian under WSL install. I'm running Debian "bullseye" under WSL 1 under Windows 10. That Debian version must be a little newer than yours, since the GHC packages are version 8.8.4 instead of 8.4.4, but that seems to be the only difference.

Using a clean copy of that Git repository (commit 9c3b6315) with only the Makefile changed (exactly as below except with usual "tab" indentation):

Try using a next-generation Ruby image. In your case, change circleci/ruby:2.7.4-node-browsers to cimg/ruby:2.7.4-browsers. You can find the full list of images here.

This version is no longer available in canonical mirrors.

It has been released in 2013.

As a result, having both python and pip working together since then is challenging.

It may be the simplest way if ubuntu is not a requirement.

I'm not familiar with VSCode, but you can manually force the chosen architecture slice of anything you launch with the arch command (see man arch).

If you have a script that you'd normally launch like:

First of all, you need to convert all values in your data to numeric type, int for example:

You don't read regex for that; try

After minimization, your error boils down to re.compile("""[\\s-_]"""). This is a bad character range indeed; you probably meant the dash to be literal re.compile(r"[\s\-_]") (always use raw strings for regex r"..."). Moving the dash to the end of the bracket group works too: r"[\s_-]".

In the future, try to binary search to find the minimal failing input: remove the right half of the regex. If it still fails, the problem must have been in the left half. Remove the right half of the remaining substring and repeat until you're down to a minimal failing case. This technique doesn't always work when the problem spans both halves, but it can't hurt to try.

As mentioned in the comments, it's pretty odd to have such a massive regex as this, but I'll assume you know what you're doing.

As another aside, there are some antipatterns in this regex (pardon the pun) like {0,} which can be simplified to *.