Making my first real post on here 😬
And my first real blog post in a while, motivated by a workshop @gvwilson gave on writing
"Four tips for research groups sharing code on how to structure Python packages"
http://blog.nicholdav.info/four-tips-structuring-research-python/
Bit of an #RSEng post.
Would love to hear what ppl think.
@catch_me_coding @kelly_sovacool @benfulton @labarba @astrojuanlu @hdashnow @simon @brianokken @danielskatz @us_rse @tacaswell
@nicholdav welcome to #mastodon and great first post! I particularly like the point about the downsides of `from package import (... list of objects ...)` and how that can pollute the namespace. I do tend to still use that style of import statement in non-user facing modules, but even then I can get confused about where a name has come from if I am half way down a massive file. This is mitigated if your code editor has nice inference festures, but best not to rely on that too much, especially for novices that might not be using more advanced tooling.
@mattasdata thank you 🙏
Agreed a list of imports can be fine in non-user facing modules (hence "tips" not "rules") but I did run into a particularly egregious example that made me want to post about it