Changes

<code><b>user@host ~ $ ./duim.py -H /usr/local/lib</b></code>

61 % [============ ] 160.2 M 164028 /usr/local/lib/heroku 4 % [= ] 10.8 M 11072 /usr/local/lib/python2.7 34 % [======= ] 90.4 M 92608 /usr/local/lib/node_modules 0 % [ ] 8.0 K /usr/local/lib/python3.8Total: 261.4 M 267720 /usr/local/lib

160 MB 164028 represents 61% of the total 160 MB267720. The percentages don't have to add up to 100%, since with these arguments we are excluding files in the target directory. You may choose to add an option to your script to print files as well.

The bar chart in this example is 20 characters long, but this must be dynamic. The 20 characters does <i>not</i> include the square brackets. The resolution of the bar chart must become more accurate as you increase the total size. For example, if the user specifies a length of 100 total characters, in this example 61 of those characters would be equal signs and 39 would be spaces.

The output of each subdirectory should include percentage, size in bytes (or Human readable if the user uses the -H option), the bar chart and the name of the subdirectory.

You will need to complete the functions inside the provided file called <code>duim.py</code>. The provided <code>checkA2checkA1.py</code> will be used to test these functions.

* 1. <code>call_du_sub()</code> should take the target directory as an argument and return a list of strings returned by the command <b>du -d 1<target directory></b>.** Use subprocess.Popenor os.popen.

* 2. <code>percent_to_graph()</code> should take two arguments: percent and the total chars. It should return a 'bar graph' as a string.** Your function should check that the percent argument is a valid number between 0 and 100. It should fail if it isn't. You can <code>raise ValueError</code> in this case.

* 3. <code>create_dir_dict</code> should take a list as the argument, and should return a dictionary.

You may create any other functions that you think appropriate, especially when if you begin decide to build additional functionality. Part of your evaluation will be on how "re-usable" your functions are, and sensible use of arguments and return values.

== The First Milestone (due July 26October 7) ==

<code>python3 checkA2checkA1.py -f -v TestPercent</code>

<code>python3 checkA2checkA1.py -f -v TestDuSub</code>

== Second Milestone (due August 2October 21) ==

* 1. <code>create_dir_dict</code> will take your list from <code>call_du_sub</code> and return a dictionary. ** Every item in your list should create a key in your dictionary.** Your dictionary values should be a number of bytes.

** Again, test using your Python interpreter or the check script. To run the check script, enter the following:

You will be using a module in the standard library called <bcode>Argparse</b>. This will help handle more complex sets of options and arguments than simply using sys.argvpython3 checkA1.Refer to the argparse documentation to complete the <code>parse_command_argspy -f -v TestDirDict</code> function. At minimum, your assignment should handle the following options and arguments:

* -h will print a usage message2. This will automatically be created by argparse itself, you will not need <code>get_total</code> needs to implement this. Howeveraccept your dictionary, refer carefully to and the sample output target directory, and ensure that your help message matches return the required output.* -H will print file sizes total size in Human readable format. For example, 1024 bytes will be printed as 1K, 1024 kilobytes will be printed as 1M, and so on. * -l <number> will set the maximum length of the bar graph. The default should be 20 character. This option will require an option argument that is an integer.* Your script will also require one positional argument which contains the target directory for scanning.

Your assignment should be able to produce * Use the followingto test your code:

<code><b>user@host ~ $ python3 duim.py -h</b></code><pre>usage: duim.py [-h] [-H] [-l LENGTH] [target] DU Improved -- See Disk Usage Report with bar charts positional arguments: target The directory to scan. optional arguments: -h, --help show this help message and exit -H, --human-readable print sizes in human readable format (e.g. 1K 23M 2G) -l LENGTH, --length LENGTH Specify the length of the graph. Default is 20. Copyright 2021</pre> Use the following to test your code: <code>python3 checkA2checkA1.py -f -v TestArgsTestTotal</code>

* In your <code>if __name__ == '__main__'</code> block, you will have to call accept a command line argument from the parse_command_args function. Experiment with print statements so that you understand how each option and argument are storeduser This will become your target directory.

* Pass the return value from that function to <code>create_dir_dict</code>.* You may wish Pass the dictionary into <code>get_total</code> to create one or more functions to do get the total size of the target.* For each item in your dictionary (excluding the followingtarget):

After completing the above, you are expected may choose to add some additional features. Some improvements you could make are:

It is expected that the additional features you provided should be useful, non-trivial, they should not require super-user privileges and should not require the installation of additional packages to work. (ie: I shouldn't have to run pip to make your assignment work). == The Assignment (due August 6November 4, 11:59pm) ==

| required functions design First Milestone || 5 10 ||

| required functions readability Second Milestone || 5 10 ||

| main loop percent function design || 10 ||

| main loop readability get total function design || 10 ||

| output function other functions design || 5 ||

| output function readability Error checking and exception handling || 5 10 ||

| additional features implemented required functions readability/variable naming || 20 5 ||

| docstrings and comments main loop design || 5 ||

| First Milestone main loop readability || 10 5 ||

| Second Milestone docstrings and comments || 10 15 ||

* [ ] your python script, named as 'duim.py', in your repository, and also '''submitted to Blackboard''', by August 6 November 4 at 11:59pm.