On Friday, February 17, 2017 at 3:24:32 AM UTC+5:30, Terry Reedy wrote:
> On 2/15/2017 7:42 AM, poseidon wrote:
>
> > what are pth files for?
>
> They are for extending (mainly) lib/site-packages.
Hey Terry!
This needs to get into more public docs than a one-off post on a newsgroup/ML
--
htt
Thanks Erik,
On Thu, Feb 16, 2017 at 6:53 AM, Erik wrote:
> (which is what I think you mean by "proper size")
>
As I explained at my first post, I'm teaching Python to novice programmers.
Therefore refactoring example code should be in the size what they can
understand.
It is hard for them to
On 2/15/2017 7:42 AM, poseidon wrote:
what are pth files for?
They are for extending (mainly) lib/site-packages. To repeat what I
have posted before: every time I install a new version of Python, I add
(copy) python.pth containing 'F:/python' (without the quotes). This
makes my directory
On Thu, 16 Feb 2017 12:00:36 +0100, Cecil Westerhof wrote:
> On Thursday 16 Feb 2017 10:43 CET, alister wrote:
>
>> On Wed, 15 Feb 2017 19:08:59 -0800, Paul Rubin wrote:
>>
>>> Antoon Pardon writes:
On reason to use this is for some easy "logging"
>>>
>>> I think it's better to use the actu
On Thursday 16 Feb 2017 10:43 CET, alister wrote:
> On Wed, 15 Feb 2017 19:08:59 -0800, Paul Rubin wrote:
>
>> Antoon Pardon writes:
>>> On reason to use this is for some easy "logging"
>>
>> I think it's better to use the actual logging module. I generally
>> start a new program with print state
On Wed, 15 Feb 2017 19:08:59 -0800, Paul Rubin wrote:
> Antoon Pardon writes:
>> On reason to use this is for some easy "logging"
>
> I think it's better to use the actual logging module. I generally start
> a new program with print statements but convert them to logging after
> there's enough
