On 2/4/2023 12:24 AM, dn via Python-list wrote:
The transform is likely dictated by your client's specification. So,
another separation. Hence Design 1.
There is a strong argument for suggesting that we're going out of our
way to imagine problems or future-changes (which may never happen). If
On 04/02/2023 16.24, Thomas Passin wrote:
On 2/3/2023 5:14 PM, 2qdxy4rzwzuui...@potatochowder.com wrote:
Keep It Simple: Put all four modules at the top level, and run with it
until you falsify it. Yes, I would give you that same advice no matter
what language you're using.
In my recent
On 2/3/2023 5:14 PM, 2qdxy4rzwzuui...@potatochowder.com wrote:
Keep It Simple: Put all four modules at the top level, and run with it
until you falsify it. Yes, I would give you that same advice no matter
what language you're using.
In my recent message I supported DESIGN 1. But I really
On 2/3/2023 4:18 PM, transreductionist wrote:
Here is the situation. There is a top-level module (see designs below)
containing code, that as the name suggests, manages an ETL pipeline. A
directory is created called etl_helpers that organizes several modules
responsible for making up the
On 2023-02-03 at 13:18:46 -0800,
transreductionist wrote:
> Here is the situation. There is a top-level module (see designs below)
> containing code, that as the name suggests, manages an ETL pipeline. A
> directory is created called etl_helpers that organizes several modules
> responsible for
Here is the situation. There is a top-level module (see designs below)
containing code, that as the name suggests, manages an ETL pipeline. A
directory is created called etl_helpers that organizes several modules
responsible for making up the pipeline. The discussion concerns the Python
On Thu, 2 Feb 2023 16:09:09 - (UTC), Muttley wrote:
> What if its not a few scripts? What if its 10s of thousands of lines of
> core production code? If the company it belongs to wants to add new
> Python 3 features it can't just plug them into the code because it won't
> run under Python 3,
