Prompt 1

- [Description]: This project revolves around creating a set of python scripts which we will use to parse CSV data. The CSV data represents Google Business Profile data. It was scraped from Google Maps. Our purpose is to clean this data up and prepare it for use with a toolkit of custom made python scripts. - [Project Root]: "/home/ld/mgk-scrapes" - [Current Dataset]: "[Project Root]/current-data/" - [Data Directory]: "[Current Dataset]/.data/" - [Parent Data]: "[Current Dataset]/"(All directories that do not begin with a period ".") - [Stage Directories]: "[Data Directory]/stage-#" (Where # is a number.) - [State Directories]: The state directories are the directories directly under one of the [Stage Directories]. These directories store data associated with a specific state. - [County Directories]: The coiunty directories are the directories directly under one of the [State Directories]. These directories store data associated with a specific county inside of the state the county directory is under. - [Stage 1]: "[Data Directory]/stage-1/" - [Stage 2]: "[Data Directory]/stage-2/" - [Stage 3]: "[Data Directory]/stage-3/" - [Stage 4]: "[Data Directory]/stage-4/" - [Stage 5]: "[Data Directory]/stage-5/" - [Stage 6]: "[Data Directory]/stage-6/" - [Binaries]: "[Project Root]/bin/" - [Stage 1 Binaries]: "[Binaries]/stage-1/" - [Stage 2 Binaries]: "[Binaries]/stage-2/" - [Stage 3 Binaries]: "[Binaries]/stage-3/" - [Stage 4 Binaries]: "[Binaries]/stage-4/" - [Stage 5 Binaries]: "[Binaries]/stage-5/" - [Stage 6 Binaries]: "[Binaries]/stage-6/" - [Bad Matching Services]: "[Data Directory]/bad-matching-services.txt" - [GBP Business Categories]: "[Data Directory]/gbp-business-categories.txt" - [GBP Matching Services]: "[Data Directory]/gbp-matching-services.txt" - [Unknown Blacklist]: "[Data Directory]/unknown-blacklist.txt" - [Rule 1]: All scripts need to be able to be ran from any directory. - [Rule 2]: All scripts need output what they are doing, as they are doing it. - [Rule 3]: All tasks should use halo to report successes and failures. - [Rule 4]: The python module "tqdm" can be used to report progress when appropriate. - [Rule 5]: Scripts must be heavily commented, describing the purpose of the script and what each code block inside the code is for. - [Rule 6]: Every script should begin with a hashbang "#!/usr/bin/env python". - [Rule 7]: Every script should have a name, and the name of the script should be immediately beneath the hashbang in a comment field prefixed by a string that reads "Script Name: ". - [Rule 8]: Scripts should generally have robust error checking.

Please be sure to reference project details above when factoring code, or answering questions.

I have the following script which you made earlier named "remove-empty-columns".

Item 1: I would like you to refactor it according to the above.

Item 2: This script should be able to be ran from anywhere. It will need to be able to be called upon different Stage's using a command line option like "remove-empty-columns.py stage-1".

Item 3: I would also like this script to use a spinner to report working being done rather than a progress bar. It should report to the user state by state, and not county by county as it does not.

item 4: This script should use pyfiglet to repor the script name as it runs as the first output.

Here is the script:

Prompt 2

Please be sure to reference project details above when factoring code, or answering questions.

I have the following script which you made earlier named "remove-empty-columns".

Item 1: I would like you to refactor it according to the above.

Item 2: This script should be able to be ran from anywhere. It will need to be able to be called upon different Stage's using a command line option like "remove-empty-columns.py stage-1".

Item 3: I would also like this script to use a spinner to report working being done rather than a progress bar. It should report to the user state by state, and not county by county as it does not.

item 4: This script should use pyfiglet to repor the script name as it runs as the first output.

Here is the script:

I would like to modify this script:

Item 1: It should tally up the deleted columns for each state, and report on that tally.

When reporting as:

Finsihed processing .

I want it instead to say:

Removed columns from . Columns removed:

Where is the tally of columns removed from that state.

Item 2: The first line of output besides the pyfiglet header is a line that reads:

<output line 1> Correcting column counts in /home/ld/mgk-scrapes/current-data/.data/stage-1... </output line 1>

This should report as:

<new output line 1> Removing empty columns in </new output line 1>

Where is the stage being operated on.

Item 3: I wish to modify this reporting line too:

Correcting CSV files in

I would like the above line to be modified to the following instead:

Searching for empty columns to delete in

Prompt 3

Please be sure to reference project details above when factoring code, or answering questions.

I wish to modify the "remove-empty-columns" script:

I would like this scripts pyfiglet function to be modified.

Before displaying the pyfiglet banner as the first output, I would like the string that is output to be modified first.

The hyphens in the script name should be replaced with spaces. Then the words that are left behind in the script name should be capitalized. Then we can print that version of the script name with pyfiglet.

20 KiB Raw Permalink Blame History

Prompt 1

Prompt 2

Prompt 3

20 KiB

Raw Permalink Blame History