On 9/12/19 5:11 PM, DL Neil via Python-list wrote:
> On 12/09/19 8:22 PM, Barry Scott wrote:
>
>> In large projects with many modules import with side-effect can make
>> for a maintenance
>> burden.
>
>
> You seem to have unmasked an assumption under which I operate. (well
> done - you know what
On 13Sep2019 08:40, DL Neil wrote:
On 12/09/19 10:59 AM, Cameron Simpson wrote:
On 12Sep2019 08:24, DL Neil wrote:
In this day-and-age do you have a script in live/production-use,
which is also a module? What is the justification/use case?
Many. Many many.
1: Many of my modules run their
On 12/09/19 8:22 PM, Barry Scott wrote:
On 11 Sep 2019, at 21:24, DL Neil via Python-list
wrote:
In this day-and-age do you have a script in live/production-use, which is also
a module? What is the justification/use case?
(discounting distutils and similar installation tools, or unit
On 12/09/19 10:59 AM, Cameron Simpson wrote:
On 12Sep2019 08:24, DL Neil wrote:
In this day-and-age do you have a script in live/production-use, which
is also a module? What is the justification/use case?
Many. Many many.
1: Many of my modules run their unit tests if invoked as the main
On Thu, Sep 12, 2019 at 6:57 PM Barry Scott wrote:
> As scripts become more complex having it run on import might make debugging
> harder
> and prevents reuse.
>
> For example I will import a script at the REPL and examine it and call
> function in it to
> help me understand and fix problems.
> On 11 Sep 2019, at 21:24, DL Neil via Python-list
> wrote:
>
> In this day-and-age do you have a script in live/production-use, which is
> also a module? What is the justification/use case?
>
> (discounting distutils and similar installation tools, or unit testing
> methodology)
>
>
>
On 12/09/19 10:37 AM, Alan Bawden wrote:
DL Neil writes:
... However, reversing the question in my mind led me to ask (myself):
how many scripts do I have (in "production use") which are ever used
(also) as a module by some other script? I think the answer is/was:
"none"! Accordingly,
On 12Sep2019 08:24, DL Neil wrote:
In this day-and-age do you have a script in live/production-use,
which is also a module? What is the justification/use case?
Many. Many many.
1: Many of my modules run their unit tests if invoked as the main
programme.
2: Several modules are their own
DL Neil writes:
> ... However, reversing the question in my mind led me to ask (myself):
> how many scripts do I have (in "production use") which are ever used
> (also) as a module by some other script? I think the answer is/was:
> "none"! Accordingly, (spoiler alert: this statement may be
On Thu, Sep 12, 2019 at 7:34 AM DL Neil via Python-list
wrote:
>
> On 12/09/19 8:43 AM, Chris Angelico wrote:
> > Yes, absolutely. It's the easiest way to share code between two
> > scripts. Here's an example that I created recently:
> >
> >
On 12/09/19 8:43 AM, Chris Angelico wrote:
On Thu, Sep 12, 2019 at 6:34 AM DL Neil via Python-list
wrote:
In this day-and-age do you have a script in live/production-use, which
is also a module? What is the justification/use case?
Yes, absolutely. It's the easiest way to share code
On Thu, Sep 12, 2019 at 6:34 AM DL Neil via Python-list
wrote:
>
> In this day-and-age do you have a script in live/production-use, which
> is also a module? What is the justification/use case?
>
Yes, absolutely. It's the easiest way to share code between two
scripts. Here's an example that I
In this day-and-age do you have a script in live/production-use, which
is also a module? What is the justification/use case?
(discounting distutils and similar installation tools, or unit testing
methodology)
There are over 500 questions on StackOverflow which refer to Python's
if
13 matches
Mail list logo
