PyShell | python backdoor （后门程序） | Machine Learning library

You have made a typo.

The error gives you the solution, simply let the new method to take the arguments even if you don't use them:

As I wrote in the comments, mgrid generates arange (or its equivalent) for each 'dimension'. And that only works with scalar.

But lets look at the ranges that your bounds create:

Finding the dictionary with max profit and the index works without copying the profit value as first element in a list. I slightly modified the dictionaries.

Change your WHILE_LOOP and INPUT to this

From the commit history of cpython - My emphasis: github

In the future, the population must be a sequence. Instances of
:class:set are no longer supported. The set must first be converted to a :class:list or :class:tuple, preferably in a deterministic order so that the sample is reproducible.

If you don't care about reproducibility sorting is not necessary.

Since I don't have reputation to comment I'm writing this as an answer. I tried to run your erroring code on my machine and it had no problems with it whatsoever (provided I replace path with something like 'check_json.json'). This tells me that it's related to your environment.

The error itself (json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)) seems to pop up when you're operating on an empty string, meaning that File.read() is returning an empty string that json.loads doesn't know what to do with.

Some possible issues could be:

1. You've redefined a reserved keyword somewhere and so Python is struggling to get the objects to behave as they should (a shot in the dark based on your use of File and Dictionary. Yes they're not builtins/reserved words but who knows what the rest of the code looks like right?)
2. Something's wrong in your Python install and you need to reinstall it.
3. You have some sort of strange permissions that stop you from actually saving down data to this file that you're creating.

In the previous answer I had to guess which version of python-shell was used by the node as it has no hints, so I picked the current latest version (3.0.1) as an arbitrary choice.

It appears that this was the wrong choice soI suggest you edit the package.json file again and change the ^3.0.1 version for the python-shell dependency and change it to ^1.0.4

The b'' isn't a "string prefix", instead it indicates that you are dealing with a sequence of bytes. Bytes can represent anything, including a text which is just a series of characters in some encoding, like UTF-8, ASCII, etc.

That's what .decode() does, it takes the sequence of bytes and interprets it as if it were a string of characters in that encoding and returns a string of those characters. Conversely, you could then encode the resulting string of characters into some other encoding by calling .encode() on the string and you'd get the sequence of bytes that represents that string in that encoding.

However, you can't just take any sequence of bytes and 'decode' it as any decoding - the bytes will have a certain encoding if they represent some string, but the example you give (of an executable) doesn't represent a string of characters at all and thus won't successfully decode into a string if you just call .decode() on it.

If you're lucky, the decoding works on the parts of the executable that are strings in that encoding, but even that's not guaranteed to work, as the strings will be surrounded by bytes that don't represent that encoding.

If you want to extract strings from an executable, you need to correctly identify what parts of the executable represent strings, extract those sequences of bytes and decode them with the correct encoding. How to do that will depend on the operating system the executable is for, whether it's 32-bit or 64-bit, etc.

Note: many programmers new to Python or coding in general get confused by the fact that Python (for the sake of convenience) shows you a bytes object as very similar to a string (it looks just like string with a b before it), this is even more confusing if it happens to be an encoding that's UTF or very similar, as the contents of the bytes object will even be readable then. But that doesn't mean the bytes objects actually is a string.