-
Notifications
You must be signed in to change notification settings - Fork 315
Launchers don't forward command line arguments to batch scripts #1564
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
We lost that feature when simplifying launchers to something that was not scaring anti-viruses. the "/scripts/*.bat" second layer of launcher should still accept to forward command line, though |
When I individually submitted the launchers I rebuilt, 1 or 2 antiviruses were unhappy. Rising, which I've never heard of, was the only one that complained about all of them. |
here there is "Gridinsoft (no cloud)" and "Deep Instinct" .... removing pywin32 from my test flavor, to check further |
otherwise, your lanchers looks perfectly ok, but rules are made per anti-viruses |
apparently, removing pywin32 and 30' minutes, makes one or the two red flags go away .... hummm. patch are ready if weather truly improve. |
The
exe
launchers don't seem to forward command line arguments to the batch scripts. For example,opens JupyterLab with the notebook directory set as C:\, but
launches JupyterLab with the default notebook directory.
The text was updated successfully, but these errors were encountered: