Code Cleanup

[Cabalist]

Hey there,

Just started using this. I noticed that files writes were not using a contextmanager and then fell down the rabbit hole of cleaning up some other things. Nothing should be a functional change and the with open(...) as ... will prevent any dangling filehandlers should an issue happen.

Each commit should be self contained to the issue it addresses for review instead of seeing a huge amount of thrash.

Ignoring whitespace in the compare is also helpful to cut down on the noise. :)

Cheers! Thanks for an awesome project!

[JamesH65]

Can you post the functional changes as a separate PR please. Also, I disagree with some of the whitespace changes, there was formatting in there for a reason. Hence separating from the functional changes.

[Cabalist]

Done. New PR opened (#33)

As for the purposeful whitespace formatting, I see

pico-project-generator/pico_project.py

Lines 47 to 62 in 3a1cdad

	features_list = {
	'spi' : ("SPI", "spi.c", "hardware/spi.h", "hardware_spi"),
	'i2c' : ("I2C interface", "i2c.c", "hardware/i2c.h", "hardware_i2c"),
	'dma' : ("DMA support", "dma.c", "hardware/dma.h", "hardware_dma"),
	'pio' : ("PIO interface", "pio.c", "hardware/pio.h", "hardware_pio"),
	'interp' : ("HW interpolation", "interp.c", "hardware/interp.h", "hardware_interp"),
	'timer' : ("HW timer", "timer.c", "hardware/timer.h", "hardware_timer"),
	'watch' : ("HW watchdog", "watch.c", "hardware/watchdog.h", "hardware_watchdog"),
	'clocks' : ("HW clocks", "clocks.c", "hardware/clocks.h", "hardware_clocks"),
	}
	stdlib_examples_list = {
	'uart': ("UART", "uart.c", "hardware/uart.h", "hardware_uart"),
	'gpio' : ("GPIO interface", "gpio.c", "hardware/gpio.h", "hardware_gpio"),
	'div' : ("Low level HW Divider", "divider.c", "hardware/divider.h", "hardware_divider")
	}

Are there any other places were whitespace has purpose/meaning that were overwritten?

[JamesH65]

I'll have to check again, that was the obvious example.

[lurch]

Has this been superseded by #39 ?