01-notebooks

import%20marimo%0A%0A__generated_with%20%3D%20%220.13.15%22%0Aapp%20%3D%20marimo.App()%0A%0Awith%20app.setup%3A%0A%20%20%20%20import%20marimo%20as%20mo%0A%0A%0A%40app.cell(hide_code%3DTrue)%0Adef%20_()%3A%0A%20%20%20%20mo.md(r%22%22%22%0A%20%20%20%20%23%20Python%20Notebooks%0A%0A%20%20%20%20Python%20notebooks%20are%20basically%20your%20interactive%20coding%20documents.%20While%20we%20don't%20always%20use%20them%20in%20research%20(we%20tend%20to%20favour%20standalone%20scripts%20for%20reproducibility)%2C%20they%20are%20really%20useful%20for%20data%20processing%20and%20explorations.%20The%20notebooks%20for%20the%20workshops%20run%20in%20your%20browser%20-%20so%20**make%20sure%20to%20save%20all%20relevant%20files**%20(Python%20files%2C%20plots%20-%20all%20in%20the%20Files%20pane%20to%20the%20left)%20to%20your%20computer%20before%20shutting%20it%20down!%0A%0A%20%20%20%20%3E%20**Note**%3A%20the%20earlier%20notebooks%20are%20a%20bit%20more%20read-through%2C%20but%20the%20level%20of%20engagement%20and%20your%20contributions%20will%20increase.%20If%20you%20are%20already%20familiar%20with%20Python%2C%20there%20should%20be%20some%20more%20advanced%20examples%20and%20concepts%20as%20we%20go%2C%20so%20make%20sure%20to%20at%20least%20quickly%20go%20through%20all%20the%20workshops!%0A%0A%20%20%20%20%23%23%20Types%20of%20cells%0A%0A%20%20%20%20They%20can%20be%20a%20mix%20of%20_Python%20cells_%20and%20_Markdown%20cells_.%20Python%20cells%20contain%20code%20that%20can%20be%20run%20inside%20the%20notebook%20with%20any%20output%20of%20the%20code%20(values%2C%20text%2C%20plots)%20appearing%20directly%20below.%0A%0A%20%20%20%20%3E%20**Recommendation**%3A%20You%20can%20use%20the%20plus%20buttons%20above%20and%20below%20a%20cell%20to%20add%20new%20cells%20-%20great%20way%20to%20play%20around%20with%20some%20code!%0A%0A%20%20%20%20%23%23%23%20Markdown%0A%0A%20%20%20%20Markdown%20cells%20(like%20this%20one)%20are%20used%20to%20help%20to%20convey%20information.%20They%20are%20not%20executed%20and%20support%20formatting%20in%20%5BMarkdown%5D(https%3A%2F%2Fwww.markdownguide.org%2Fbasic-syntax%2F).%20We%20denote%20headings%20with%20the%20hash%20signs%20%E2%80%93%20the%20more%20%60%23%60%2C%20the%20higher%20the%20heading%20level.%20Text%20can%20be%20**bolded**%20with%20double%20asterisks%20(%60**text**%60)%20and%20*emphasised*%20in%20italics%20with%20single%20asterisks%20(%60*text*%60).%20You%20can%20also%20make%20%5Blinks%5D(https%3A%2Fhttps%3A%2F%2Fduckduckgo.com%2F)%20and%20lists.%20The%20guide%20above%20gives%20you%20more%20formatting%20syntax.%20Note%20that%20common%20shortcuts%20for%20bold%2Fitalics%20work%20well%20here%20too!%0A%0A%20%20%20%20%23%23%23%20LaTeX%0A%0A%20%20%20%20%5BLaTeX%5D(https%3A%2F%2Fen.wikibooks.org%2Fwiki%2FLaTeX%2FBasics)%20is%20useful%20for%20writing%20out%20mathematical%20equations%20in%20your%20text.%20We%20include%20it%20in-line%20with%20text%20by%20encapsulating%20expressions%20with%20dollar%20signs%2C%20e.g.%20%24E%3Dmc%5E2%24%20and%20can%20also%20have%20separated%20block%20equations%20separated%20between%20%60%5C%5B%60%20and%20%60%5C%5D%60%2C%20as%20below%3A%0A%0A%20%20%20%20%5C%5B%0A%20%20%20%20%20%20%20%20%20%20%20%20f(x)%20%3D%201%20%2B%20x%20%2B%20%5Cfrac%7Bx%5E2%7D%7B2!%7D%20%2B%20%5Cfrac%7Bx%5E3%7D%7B3!%7D%20%2B%20%5Cldots.%0A%20%20%20%20%5C%5D%0A%0A%20%20%20%20See%20the%20source%20code%20for%20this%20cell%20for%20a%20LaTeX%20example%2C%20otherwise%20the%20Internet%20is%20a%20great%20resource%20to%20learn%20how%20to%20use%20it!%0A%0A%20%20%20%20%23%23%20Example%20use%0A%0A%20%20%20%20You%20can%20see%20that%20Python%20notebooks%20can%20be%20quite%20useful%20to%20present%20your%20results.%20You%20can%20generate%20plots%20from%20your%20data%20directly%20with%20Python%20cells%20and%20then%20provide%20some%20discussion%20in%20the%20following%20Markdown%20cell.%20The%20beauty%20of%20that%20is%20that%20you%20can%20easily%20reuse%20your%20code%20and%20don't%20need%20to%20keep%20pasting%20plots%20from%20Excel!%0A%0A%20%20%20%20%23%23%20Explore%20and%20interact%0A%0A%20%20%20%20To%20see%20the%20Markdown%20code%20used%20to%20generate%20this%20cell%2C%20click%20on%20the%20three%20dots%20and%20select%20%22Show%20code%22%20(or%20click%20%60Ctrl%20%2B%20H%60%20with%20the%20cell%20highligted).%20You%20can%20also%20double-click%20on%20the%20text.%20To%20add%20a%20new%20cell%2C%20click%20on%20the%20small%20%60%2B%60%20sign%20to%20the%20left.%20To%20execute%20and%20move%20to%20the%20next%20cell%2C%20press%20%60Shift%20%2B%20Enter%60.%0A%0A%20%20%20%20%3E%20**Recommendation**%3A%20You%20can%20use%20the%20plus%20buttons%20above%20and%20below%20a%20cell%20to%20add%20new%20cells%20-%20great%20way%20to%20play%20around%20with%20some%20code!%20Try%20to%20execute%20**all**%20cells%20in%20the%20workbooks.%0A%0A%20%20%20%20%23%23%20Getting%20help%0A%0A%20%20%20%20If%20you%20type%20%60help(command)%60%20in%20a%20cell%2C%20you%20will%20get%20a%20description%20of%20how%20to%20use%20the%20%60command%60.%0A%20%20%20%20%22%22%22)%0A%20%20%20%20return%0A%0A%0A%40app.cell%0Adef%20_()%3A%0A%20%20%20%20help(sorted)%0A%20%20%20%20return%0A%0A%0A%40app.cell(hide_code%3DTrue)%0Adef%20_()%3A%0A%20%20%20%20mo.md(r%22%22%22%0A%20%20%20%20%23%23%20AI%20and%20LLMs%0A%0A%20%20%20%20Large%20Language%20Models%20have%20changed%20the%20way%20we%20code%20in%20real%20life%2C%20but%20they%20do%20**not**%20eliminate%20the%20need%20to%20understand%20how%20coding%20and%20basic%20algorithms%20function%20%E2%80%93%20they%20are%20great%20to%20help%20you%20draft%20a%20function%20or%20troubleshoot%20your%20code%2C%20but%20it%20is%20crucial%20for%20you%20to%20learn%20how%20to%20ask%20the%20question%20in%20the%20best%20possible%20way.%20Understanding%20of%20the%20underlying%20principles%20or%20syntax%20rules%20helps%20you%20maximise%20the%20potential%20of%20new%20technologies.%20Additionally%2C%20the%20skill%20of%20abstracting%20a%20problem%20to%20basic%20components%20and%20algorithms%20in%20order%20to%20approach%20it%20is%20essential%20throughout%20science.%0A%0A%20%20%20%20I%20recommend%20that%20for%20these%20workshops%20you%20do%20not%20use%20LLMs%20%E2%80%93%20there%20are%20plenty%20of%20links%20to%20original%20resources%20scattered%20throughout%20the%20notebooks%20to%20give%20you%20some%20background%20information%20about%20what%20we%20cover.%0A%0A%20%20%20%20%23%23%20Using%20%60marimo%60%20as%20a%20standalone%20tool%0A%0A%20%20%20%20%23%23%23%20%60molab%60%20cloud%0A%0A%20%20%20%20You%20can%20create%20and%20upload%20existing%20%60marimo%60%20notebooks%20using%20their%20free%20cloud%20server%3A%20https%3A%2F%2Fmolab.marimo.io%2Fnotebooks.%20I%20recommend%20creating%20an%20account%20with%20GitHub%2C%20so%20that%20you%20can%20link%20notebooks%20there%20as%20well%20-%20this%20way%20you%20can%20easily%20share%20and%20collaborate%20on%20them!%0A%0A%20%20%20%20You%20can%20explore%20and%20play%20with%20the%20notebooks%20in%20these%20workshops%20directly%20in%20your%20browser%2C%20but%20keep%20in%20mind%20that%20you%20will%20not%20be%20able%20to%20save%20any%20code%20or%20your%20progress.%20An%20easy%20way%20to%20come%20back%20to%20them%20in%20the%20future%2C%20is%20to%20import%20them%20directly%20into%20your%20%60molab%60%20cloud.%20You%20can%20find%20all%20the%20notebooks%20most%20up-to-date%20version%20%5Bdirectly%20on%20GitHub%5D(https%3A%2F%2Fgithub.com%2Fszczypinski-group%2Fpython-for-chemists%2Ftree%2Fmain%2Fnotebooks).%20Just%20copy%20a%20link%20to%20the%20notebook%20from%20there%20and%20import%20in%20%60molab%60%3A%0A%0A%20%20%20%20!%5BImporting%20GitHub%20notebooks%20into%20molab%5D(public%2Fimport-notebook-1.png)%0A%20%20%20%20!%5BImporting%20GitHub%20notebooks%20into%20molab%5D(public%2Fimport-notebook-2.png)%0A%0A%20%20%20%20%3E%20**Tip**%3A%20You%20can%20open%20any%20notebook%20from%20GitHub%20directly%20with%20%60molab%60%20by%20changing%20the%20%60https%3A%2F%2Fgithub.com%2F%60%20part%20of%20the%20URL%20with%20%60https%3A%2F%2Fmolab.marimo.io%2Fgithub%2F%60%2C%20e.g.%2C%20%5B%60https%3A%2F%2Fmolab.marimo.io%2Fgithub%2Fszczypinski-group%2Fpython-for-chemists%2Ftree%2Fmain%2Fnotebooks%2F02-variables.py%60%5D(https%3A%2F%2Fmolab.marimo.io%2Fgithub%2Fszczypinski-group%2Fpython-for-chemists%2Ftree%2Fmain%2Fnotebooks%2F02-variables.py)%20instead%20of%20%60https%3A%2F%2Fgithub.com%2Fszczypinski-group%2Fpython-for-chemists%2Ftree%2Fmain%2Fnotebooks%2F02-variables.py%60.%20You%20can%20then%20%22fork%20it%22%20to%20save%20it%20into%20your%20own%20%60molab%60%20space%20and%20keep%20the%20edits!%0A%0A%20%20%20%20In%20the%20future%2C%20you%20might%20want%20to%20be%20%22mirroring%22%20a%20notebook%20directly%20-%20so%20that%20you%20can%20synchronise%20the%20changes%20with%20GitHub.%20There%20is%20an%20option%20to%20do%20that%20directly%20when%20adding%20a%20notebook%20into%20%60molab%60.%0A%0A%20%20%20%20!%5BMirroring%20GitHub%20notebooks%20in%20molab%5D(public%2Fmolab.png)%0A%0A%20%20%20%20%3E%20**Recommendation**%3A%20If%20you%20do%20not%20have%20a%20GitHub%20account%2C%20it%20is%20a%20good%20idea%20to%20create%20one%20now.%20Go%20to%20https%3A%2F%2Fgithub.com%2F%2C%20sign%20up%2C%20create%20a%20new%20(private%20if%20you%20wish)%20repository%20called%20%22python-introduction%22%2C%20and%20upload%20this%20notebook%20there%20(download%20it%20from%20the%20%60Files%60%20tab%20on%20the%20left).%20You%20can%20then%20load%20it%20up%20in%20%5B%60molab%60%5D(https%3A%2F%2Fmolab.marimo.io%2Fnotebooks)%20and%20use%20it%20as%20a%20base%20for%20all%20Python%20in%20these%20workbooks%20or%20create%20new%20repositories%20if%20needed%2C%20e.g.%2C%20for%20lab%20write-ups%20or%20your%20MChem%20project!%0A%0A%20%20%20%20%23%23%23%20Local%20installation%0A%0A%20%20%20%20If%20you%20don't%20want%20to%20use%20the%20browser-based%20notebooks%20in%20the%20future%20but%20have%20a%20locally%20availably%20%60marimo%60%20notebooks%2C%20you%20can%20install%20them%20as%20a%20standalone%20tool%20(that%20is%20what%20I%20do).%0A%0A%20%20%20%20%3E%20**Note**%3A%20this%20cannot%20be%20done%20on%20University-managed%20Windows%20machines%20yet.%20You%20can%20do%20it%20on%20Linux%20or%20on%20your%20personal%20computer.%0A%0A%20%20%20%20For%20installing%20anything%20Python-related%2C%20I%20**very%20strongly%20recommend**%20the%20%60uv%60%20package%20(unfortunately%2C%20you%20cannot%20get%20it%20from%20AppsAnywhere%20yet).%20Installation%20instructions%20for%20all%20platforms%20are%20%5Bhere%5D(https%3A%2F%2Fdocs.astral.sh%2Fuv%2Fgetting-started%2Finstallation%2F).%20Once%20you%20have%20%60uv%60%20installed%2C%20you%20can%20use%20marimo%20extremely%20easily%20-%20check%20the%20%5Bwebsite%5D(https%3A%2F%2Fdocs.astral.sh%2Fuv%2Fguides%2Fintegration%2Fmarimo%2F)%20for%20instructions%20but%20they%20basically%20boil%20down%20to%20typing%20in%20Terminal%3A%0A%0A%20%20%20%20%60%60%60sh%0A%20%20%20%20uvx%20marimo%20edit%20--sandbox%20my_notebook.py%0A%20%20%20%20%60%60%60%0A%20%20%20%20%22%22%22)%0A%20%20%20%20return%0A%0A%0A%40app.cell(hide_code%3DTrue)%0Adef%20_()%3A%0A%20%20%20%20mo.md(r%22%22%22%0A%20%20%20%20%23%20Advanced%20topics%0A%0A%20%20%20%20%23%23%20Version%20control%0A%0A%20%20%20%20Modern%20coding%20projects%20use%20%5Bversion%20control%5D(https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FVersion_control)%20for%20controlling%20and%20tracking%20different%20version%20of%20the%20source%20code.%20Probably%20the%20most%20widespread%20version%20control%20system%20is%20%5BGit%5D(https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FGit)%20-%20it%20was%20developed%20by%20Linus%20Torvalds%20for%20the%20development%20of%20the%20Linux%20kernel.%0A%0A%20%20%20%20GitHub%20is%20one%20of%20the%20most%20populars%20developer%20platforms%20for%20storing%2C%20managing%2C%20and%20sharing%20code.%20It%20uses%20Git%20and%20provides%20a%20number%20of%20other%20useful%20features.%20Since%202018%20it%20has%20been%20owned%20by%20Microsoft%2C%20so%20feel%20free%20to%20%5Bexplore%20alternatives%5D(https%3A%2F%2Feuropean-alternatives.eu%2Fcategory%2Fversion-control-services)%20if%20you%20disagree%20with%20Microsoft%20practices.%0A%0A%20%20%20%20My%20recommendation%20for%20my%20research%20group%20is%20that%20**all%20**code%20development%20should%20be%20done%20with%20version%20control%20on%20GitHub%20-%20you%20might%20have%20noticed%20that%20these%20workbooks%20are%20also%20a%20GitHub%20repository!%20Best%20practice%20is%20to%20work%20on%20the%20non-%60main%60%20branch%20for%20any%20actual%20development%20and%20then%20create%20a%20%22pull%20request%22%20for%20the%20tested%20code%20to%20be%20included%20in%20the%20main%20branch.%20For%20more%20information%20about%20how%20to%20use%20GitHub%2C%20see%3A%20https%3A%2F%2Fdocs.github.com%2Fen%2Fget-started%2Fstart-your-journey%2Fhello-world%2F.%0A%20%20%20%20%22%22%22)%0A%20%20%20%20return%0A%0A%0A%40app.cell(hide_code%3DTrue)%0Adef%20_()%3A%0A%20%20%20%20mo.md(r%22%22%22%0A%20%20%20%20%23%23%20Python%20projects%3A%20complete%20workflow%0A%0A%20%20%20%20This%20is%20a%20**_much_%20more%20advanced%20topic**.%20You%20might%20want%20to%20skip%20it%20as%20you%20will%20not%20be%20able%20to%20currently%20do%20this%20on%20a%20University-managed%20Windows%20computer.%20However%2C%20I%20am%20including%20it%20for%20your%20future%20reference%20as%20I%20believe%20it%20is%20very%20important%20and%20useful.%20You%20should%20be%20able%20to%20do%20it%20on%20a%20Linux%20machine%20or%20your%20personal%20computer.%0A%0A%20%20%20%20For%20implementing%20different%20versions%20of%20Python%20and%20packages%2C%20use%20the%20%60pip%60%20interface%20from%20the%20%60uv%60%20package.%20Installation%20instructions%20for%20all%20platforms%20are%20%5Bhere%5D(https%3A%2F%2Fdocs.astral.sh%2Fuv%2Fgetting-started%2Finstallation%2F).%20Most%20of%20your%20code%20should%20probably%20be%20what%20%60uv%60%20considers%20a%20%5Blibrary%5D(https%3A%2F%2Fdocs.astral.sh%2Fuv%2Fconcepts%2Fprojects%2Finit%2F%23libraries)%2C%20i.e.%20isolated%20code%20with%20%60src%60%20layour%2C%20%60py.typed%60%20indicator%2C%20and%20metadata%20stored%20in%20a%20%60pyproject.toml%60%20file.%0A%0A%20%20%20%20%60%60%60sh%0A%20%20%20%20uv%20init%20--lib%20YOUR-PROJECT%0A%20%20%20%20%60%60%60%0A%0A%20%20%20%20And%20that%20is%20basically%20it.%20For%20any%20dependency%20(e.g.%20%60matplotlib%60)%20just%20use%3A%0A%0A%20%20%20%20%60%60%60sh%0A%20%20%20%20uv%20add%20matplotlib%0A%20%20%20%20%60%60%60%0A%0A%20%20%20%20If%20you%20want%20the%20dependency%20to%20only%20be%20added%20to%20a%20specific%20group%20(e.g.%2C%20developer%20dependencies%20are%20only%20installed%20if%20you%20get%20you%20software%20as%20%60pip%20install%20package%5Bdev%5D%60)%3A%0A%0A%20%20%20%20%60%60%60sh%0A%20%20%20%20uv%20add%20--dev%20pre-commit%0A%20%20%20%20%60%60%60%0A%0A%20%20%20%20%3E%20**Note**%3A%20have%20a%20look%20at%20our%20%5BpyMultiwfn%20repository%5D(https%3A%2F%2Fgithub.com%2Fszczypinski-group%2FpyMultiwfn)%20for%20a%20real-life%20example.%20In%20particular%2C%20have%20a%20look%20at%20the%20contents%20of%20the%20%60.pre-commit-config.yaml%60%20(which%20defines%20the%20settings%20of%20%60pre-commit%60)%20and%20the%20%60pyproject.toml%60%20file%20(all%20other%20metadata%2C%20including%20Python%20versions%2C%20linting%20settings%2C%20etc.).%20Don't%20worry%20about%20%60uv.lock%60%20-%20this%20is%20added%20automatically%20by%20%60uv%60.%20I%20highly%20recommend%20having%20a%20%60README.md%60%20(which%20is%20then%20rendered%20on%20the%20GitHub%20repository%20main%20page)%20and%20%60LICENSE%60%20(for%20copyright%20protection).%0A%0A%20%20%20%20%23%23%23%20Depositing%20with%20GitHub%0A%0A%20%20%20%20Once%20you%20have%20created%20your%20code%2C%20it%20is%20important%20to%20add%20in%20to%20GitHub.%20Create%20a%20**new%20repository**%20(top%20right)%2C%20give%20it%20a%20name%2C%20and%20set%20its%20visibility%20(probably%20**Private**%20to%20begin%20with).%20**Do%20not%20initialise**%20with%20any%20files%20(README%2C%20etc.)%20as%20you%20will%20already%20have%20them%20on%20your%20local%20computer.%0A%0A%20%20%20%20Then%2C%20on%20your%20local%20machine%20where%20you%20crated%20the%20code%20(see%20section%20above)%3A%0A%0A%20%20%20%20%60%60%60sh%0A%20%20%20%20%23%20Navigate%20to%20the%20folder%0A%20%20%20%20cd%20PATH%2FTO%2FYOUR-PROJECT%0A%20%20%20%20%23%20Initialise%20the%20repository%0A%20%20%20%20git%20init%0A%20%20%20%20%23%20Set%20up%20the%20main%20branch%0A%20%20%20%20git%20branch%20-M%20main%0A%20%20%20%20%60%60%60%0A%0A%20%20%20%20You%20might%20want%20to%20add%20files%20to%20%60.gitignore%60%20so%20that%20theyy%20are%20not%20versioned%20by%20git%2C%20you%20can%20do%20it%20by%20editing%20the%20file%20or%20from%20the%20command%20line%20e.g.%3A%0A%0A%20%20%20%20%60%60%60sh%0A%20%20%20%20echo%20%22__pycache__%2F%22%20%3E%20.gitignore%0A%20%20%20%20%60%60%60%0A%0A%20%20%20%20And%20when%20you%20are%20ready%2C%20make%20the%20first%20commit%3A%0A%0A%20%20%20%20%60%60%60sh%0A%20%20%20%20%23%20Stage%20all%20modified%20files%0A%20%20%20%20git%20add%20.%0A%20%20%20%20%23%20Commit%20with%20a%20message%0A%20%20%20%20git%20commit%20-m%20%22Initial%20commit%22%0A%20%20%20%20%60%60%60%0A%0A%20%20%20%20You%20will%20also%20need%20to%20add%20the%20GitHub%20repository%20as%20%60remote%60.%20Copy%20the%20address%20from%20GitHub%20(big%20%60%3C%3E%20Code%60%20button)%20and%20then%3A%0A%0A%20%20%20%20%60%60%60sh%0A%20%20%20%20git%20remote%20add%20origin%20git%40github.com%3AUSERNAME%2Fyour-repo-name.git%0A%20%20%20%20git%20push%20-u%20origin%20main%0A%20%20%20%20%60%60%60%0A%0A%20%20%20%20%23%23%23%20Linting%20and%20testing%0A%0A%20%20%20%20As%20mentioned%20above%2C%20make%20sure%20you%20have%20%60ruff%60%20installed%3A%0A%0A%20%20%20%20%60%60%60sh%0A%20%20%20%20uv%20tool%20install%20ruff%40latest%0A%20%20%20%20uv%20add%20--dev%20ruff%0A%20%20%20%20%60%60%60%0A%0A%20%20%20%20and%20same%20for%20%60pre-commit%60%3A%0A%0A%20%20%20%20%60%60%60sh%0A%20%20%20%20uv%20add%20--dev%20pre-commit%0A%20%20%20%20uv%20run%20pre-commit%20install%0A%20%20%20%20%60%60%60%0A%0A%20%20%20%20Now%20%60git%60%20will%20stop%20you%20from%20committing%20code%20that%20does%20not%20conform%20to%20the%20standards%20set%20up%20in%20the%20package%20specification.%0A%0A%20%20%20%20%23%23%20Best%20practices%0A%0A%20%20%20%20%3E%20**Important**%3A%20Commit%20often%20in%20small%20hunks%20-%20**code%20dumps%20are%20almost%20impossible%20to%20review!**%0A%0A%20%20%20%201.%20We%20try%20to%20follow%20appropriate%20style%20guides%20(e.g.%2C%20%5BPython%20PEP8%5D(https%3A%2F%2Fpeps.python.org%2Fpep-0008%2F)%2C%20%5BMarkdown%5D(https%3A%2F%2Fgoogle.github.io%2Fstyleguide%2Fdocguide%2Fstyle.html)%2C%20%5BConventional%20Commits%5D(https%3A%2F%2Fwww.conventionalcommits.org%2Fen%2Fv1.0.0%2F)).%0A%20%20%20%202.%20Install%20a%20linter%20for%20your%20IDE%2C%20I%20recommend%20%5Bruff%5D(https%3A%2F%2Fdocs.astral.sh%2Fruff%2Finstallation%2F)%20with%20some%20good%20default%20settings%20(see%20example%20%60pyproject.toml%60).%0A%20%20%20%203.%20Structure%20your%20code%20as%20a%20Python%20project%20and%20install%20%5Bpre-commit%5D(https%3A%2F%2Fpre-commit.com%2F)%20to%20ensure%20consistency.%20**Use%20%5Buv%5D(https%3A%2F%2Fdocs.astral.sh%2Fuv%2F)%20for%20package%20and%20environment%20managing.**%0A%20%20%20%204.%20Use%20%5Btype-checking%5D(https%3A%2F%2Fdocs.python.org%2F3%2Flibrary%2Ftyping.html)%20in%20your%20Python%20code%20(by%20including%20%60py.typed%60%20file)%2C%20make%20sure%20that%20you%20write%20docstrings%20(%60interrogate%60)%20and%20tests%20(%60pytest%60)%20as%20you%20go.%20Comment%20often%20to%20help%20others%20understand%20your%20intentions.%0A%20%20%20%205.%20Familiarise%20yourself%20with%20command%20line%20editors%20such%20as%20%60vim%60%20or%20%60nano%60%20for%20quick%20edits%20on%20the%20supercomputing%20cluster.%0A%20%20%20%206.%20Follow%20%5Bgit%20best%20practices%5D(https%3A%2F%2Fdocs.github.com%2Fen%2Fget-started%2Fusing-git).%20**Commit%20often**%2C%20branch%2Ffork%20actively!%20If%20your%20commit%20is%20getting%20too%20large%2C%20**use%20patch%20mode**%3A%20%60git%20add%20--patch%20--interactive%60.%0A%20%20%20%207.%20Use%20the%20%5BPython%20standard%20library%5D(https%3A%2F%2Fdocs.python.org%2F3%2Flibrary%2Findex.html)%20whenever%20possible%20(e.g.%2C%20%60time%60%2C%20%60pathlib%60)%20instead%20of%20external%20codes%20to%20reduce%20complexity%20and%20dependencies.%0A%20%20%20%20%22%22%22)%0A%20%20%20%20return%0A%0A%0Aif%20__name__%20%3D%3D%20%22__main__%22%3A%0A%20%20%20%20app.run()%0A