There were some instructions regarding how to use the generated .EXE file in the README.
The original intention was to make it easy to run for someone who isn't familiar with Python/programming.
@sc1341 Why did you decide to remove it in your PR? Do you think it is unnecessary or superfluous?
Buggify.EXE
Pyinstaller was used with the --onefile argument to generate the .exe so that this can be run without installing Python.
pip install pyinstaller
pyinstaller Buggify.py --onefile
Double-Click
The easiest method is to simply download Buggify.exe and double click it. You will be prompted to select a file. It will automatically ouput the buggified version (with a default of 20 bugs applied) and the answer key.
Command Line - Windows
By default, Buggify.exe runs with 20 bugs. If you'd like to add more you should run Buggify.exe from the command line. Open up command prompt (cmd.exe) and navigate to the folder where Buggify.exe was saved. Type Buggify.exe followed by up to two arguments. The arguments are the file and the number of bugs.
The arguments are optional and can be entered in any order.
If the number of bugs is left out, it will default to 20.
If the file is left out, you will be prompted to select one.
If the file you're trying to select is in a different location than the .exe, you'll need to type the full file path.
If you're not in the same directory as Buggify.exe, you'll need type the full path to Buggify.exe. All of these are valid commands:
#Both Buggify.exe and testfile.py are in the same directory as the command prompt.
Buggify.exe testfile.py 15
#Only Buggify.exe is in the same path as the command prompt.
Buggify.exe 15 C:\Temp\testfile.py
#Only testfile.py is in the same path as the command prompt. Number of bugs defaults to 20.
C:\Temp\Buggify.exe testfile.py
#Buggify.exe is in the same path as the command prompt. User is prompted to select a file.
Command Line - Linux
Download and Save Buggify.py. Navigate to the directory where it was saved, open up a terminal and type the following:
The same rules regarding the optional arguments apply.
There were some instructions regarding how to use the generated .EXE file in the README.
The original intention was to make it easy to run for someone who isn't familiar with Python/programming.
@sc1341 Why did you decide to remove it in your PR? Do you think it is unnecessary or superfluous?
Buggify.EXE
Pyinstaller was used with the --onefile argument to generate the .exe so that this can be run without installing Python.
Double-Click
The easiest method is to simply download Buggify.exe and double click it. You will be prompted to select a file. It will automatically ouput the buggified version (with a default of 20 bugs applied) and the answer key.
Command Line - Windows
By default, Buggify.exe runs with 20 bugs. If you'd like to add more you should run Buggify.exe from the command line. Open up command prompt (cmd.exe) and navigate to the folder where Buggify.exe was saved. Type Buggify.exe followed by up to two arguments. The arguments are the file and the number of bugs.
The arguments are optional and can be entered in any order.
If the number of bugs is left out, it will default to 20.
If the file is left out, you will be prompted to select one.
If the file you're trying to select is in a different location than the .exe, you'll need to type the full file path.
If you're not in the same directory as Buggify.exe, you'll need type the full path to Buggify.exe. All of these are valid commands:
#Both Buggify.exe and testfile.py are in the same directory as the command prompt.
#Only Buggify.exe is in the same path as the command prompt.
#Only testfile.py is in the same path as the command prompt. Number of bugs defaults to 20.
#Buggify.exe is in the same path as the command prompt. User is prompted to select a file.
Command Line - Linux
Download and Save Buggify.py. Navigate to the directory where it was saved, open up a terminal and type the following:
The same rules regarding the optional arguments apply.