> On Feb 21, 2017, at 8:31 AM, jonathan vanasco wrote:
>
> Dropping 3.3 makes sense, as does deprecating 3.4
>
> The only thing I suggest/request is a webpage (and possibly txtfile in the
> source) that lists the supported Python versions. When people runs into
> issues, finding this info qui
Hi, so for my first post to the list I am going to ask a somewhat lame
question. Apologies if this is not the right list -- clues welcome.
I am doing a deploy of a server written in Python3 on Ubuntu 14.04. (14.04
for various reasons that are uninteresting to the list but DevOps has
good/histori
Dropping 3.3 makes sense, as does deprecating 3.4
The only thing I suggest/request is a webpage (and possibly txtfile in the
source) that lists the supported Python versions. When people runs into
issues, finding this info quickly is just so useful.
e.g.
Version Python2
>>> any idea why this does not work?
>>
>> Most likely you are being bitten by the recent change to not add '.'
>> to sys.path automatically.
>>
>> Does `PYTHONPATH=. trial ...` run your code as expected?
>>
> Yes, thanks very much. this kind of change really makes one doubt ones
> abilities.
>
Am Montag, den 20.02.2017, 18:16 -0800 schrieb Glyph Lefkowitz:
> > On Feb 20, 2017, at 5:02 AM, steven meiers
> > wrote:
> >
> > any idea why this does not work?
>
> Most likely you are being bitten by the recent change to not add '.'
> to sys.path automatically.
>
> Does `PYTHONPATH=. trial .
In general I'd say we should take into account LTS releases.
OTOH Python 3 adoption is still rather low and tends toward newer versions with
fast upgrading.
There's deadsnakes and there's SC and there's Docker. I think it's totally
fair to drop everything before 3.5 since that gives us nice g
