We Keep Coding

Python script is not executed from my batch file

I have written the following code within a .bat file, (to execute a python script):
conda activate
cd OneDrive - My path/Documenti/Python/Seguridad/Remote
py Seguridad_Python.py
If I execute that command in cmd.exe, the python file is executed.
But, if I run the .bat file with those commands, it opens the Command Prompt window, but does not execute the python script.
Can someone help?
I have also tried it with the next one, (everything in the same line), and it does the same.
C:\ProgramData\Anaconda3\python.exe C:\Users\------ MY PATH --------\\Documenti\Python\Seguridad\Remote\Seguridad_Python.python

Adding a call before was enough.
If I have the batch file and the python script at the same level, this was enough:
call conda activate
call py Seguridad_Python.py

Maybe you can try as below. Specify the batch file extension in the command prompt. Once you hit enter, it invokes your python script and run the program
C:\Users\------ MY PATH --------\\Documenti\Python\Seguridad\Remote\xyz.bat

Clickable Python CLI Instantiation

I'm trying to make my .py script clickable!
What I Have
The CLI program I created using Python works. I open Command Prompt and enter python my_script.py and everything works as expected. I want to make it clickable so a user doesn't have to run any commands!
What I've Tried
I created a .bat file in vim that runs the python my_script.py command. When I click it, the desired behavior is not achieved. Command Prompt opens for about a millisecond then closes.
My Question
How can I create a better .bat file so that my CLI program works with the click of a button?

Python, for better or worse does not allow you to specify the path to the script, and will not search the path for the script.
The official word, and I hate to say this, is that you must associate the Python.exe executable you want to run python scripts with the extension .py and then you can double click your script.py or type \path\to\script.py into the CMD prompt, and it will run the script.
I hate this from a standpoint of not wanting to accidentally execute a script by clicking it, and from the perspective of wanting to have multiple versions of python installed and choosing which one would do the execution.
There is an (IMHO) annoying (Kludgy) work-around.
You can create a File type for each instance of Python, you might have, and then associate it with the .py
so you could create the FTypes you need and associate them in a script at the time of to launch the script from the batch file:
FTYPE Py23=C:\Path\To\Pthon-23\python.exe %*
FTYPE Py38=C:\Path\To\Pthon-38\python.exe %*
Then your script could do this:
#Echo off
ASSOC .py=Py38
"C:\Path\To\Script.py"
ASSOC .py=

Python supports being called in a mode where it can ignore the first line of the script with -x. This coupled with a wrapper batch file means you can actually put the entire Python script in a batch file.
This little script shows how this can be done. It's a self-contained
#echo off
rem = """ # This is run in the batch file to launch Python
python -x "%~f0" %*
goto endofPython
rem = """
# Your python code goes here ..
def main():
print("Hello from Python")
if __name__ == "__main__":
main()
rem = """ # This section is run after Python is done, here just
# just run pause to keep the console window open
:endofPython
pause
rem = """

Get current path when running Python from Notepad++

I run Python scripts in Notepad++ using this command
cmd.exe /K "C:\InstallPython\python.exe" "$(FULL_CURRENT_PATH)"
it works, but it works not great.
When I run
exec(open("raw_ticker_list.lua").read())
it doesn't see the file, but it is in the same folder where the script lies.
When I run
import os
print(os.getcwd())
it prints
How can I make python see files in current folder?

Use this command instead:
cmd.exe /K "cd /D "$(CURRENT_DIRECTORY)" & python "$(FULL_CURRENT_PATH)""
To recap, open the "Run" menu, select the "Run" entry, and enter the above command as "The Program to Run". Possibly "Save…" it and assign a name (and keyboard shortcut) so that it permanently appears in the "Run" menu going forward.
What it does is, it opens a command window, changes the working directory to that of the script currently active in the editor (across hard drives, hence the /D parameter), then runs the Python interpreter on the script, but keeps the command window open afterwards (the /K parameter).
Use the full path to python.exe instead of just python in case it's not on the Windows search path for executables.

Python.exe opens in a new console window

I used to run Python scripts from my Windows command line, and all the prints were printed in the same console. Now something happened on my machine (Windows 10), and when I launch a Python script from the command line (i.e. open a Command Prompt and run python <my_script.py>), Windows opens a new window (titled with the absolute path of python.exe). This windows closes automatically at the end of the execution, so that I can't see the output.
How do I go back to printing output in the same command prompt window from which I run the script?

Not sure how useful this will be but I had this same problem, found this thread, and realized that the new console window was opening up when I omitted 'python' from the command.
>python myscript.py
shows the output right in the terminal where I typed the command, but
>myscript.py
opens the new console window and closes it immediately after the script runs.

It's odd but it very likely a windows setup issue as python is an exe. If memory serves windows will spawn on a > run command so checking the way python is booting will help.
Unfortunately it could be a range of issues, so some steps towards victory:
What happen when you just type python into the cmd? If it simply starts the input >>> - it means your python setup is fine. If a cmd window spawns and disappears it may be a windows permissions issue.
Try running your script with -i flag: python -i script.py. This drops you into the repl when the app completes - displaying your output.
Ensure you're using the native flavour of the cmd to test. Ensuring any command app or IDE isn't injecting a start command or weird /K (spawn new window) flag.
Hope it helps.

In my computer this was caused by Windows not knowing what program a .py file was associated with. I solved this by going to:
Control Panel -> Programs -> Default Programs -> Associate a file type or protocol with a program (Scroll down) and choose "Choose default apps by file type" Scroll down until you see ".py" and choose the correct
Python interpreter.

Simply: last row on the end of your program maybe this:
input("\nIf you whish end the program press any key ...")
...and your program wait for the key and you see your outcome

Running Python's IDLE in windows

I messed up my IDLE shortcut. What is the way to start IDLE from the cmd.exe shell in Windows?

On my system, running C:\Python26\lib\idlelib\idle.py launches idle from the command prompt. Obviously you will need to adjust your path if your main Python directory isn't C:\Python26\.
It looks like you could also launch it via idle.pyw or idle.bat in that same directory.

You can just add a path in your Environment variables tab in My Computer Properties --> Advanced as c:\Python27\Lib\idlelib. After adding this path just write idle.pyw in cmd whenever you want to run IDLE.
Just make sure you replace the folder name with whatever directory name you have.