Thanks for the feedback.
I updated the PR to use get_platform and get_host_platform.
More testing is still needed before it's ready to merge to make sure it still
does what it was intended to do.
-Original Message-
From: Python-Dev On
Behalf Of Xavier de Gaye
Sent: Tuesday, February 19
On Fri, Feb 15, 2019 at 5:29 PM Paul Ganssle wrote:
> it allows you to use non-traditional units like weeks (timedelta(days=7))
>
Weeks are traditional:
>>> timedelta(weeks=1)
datetime.timedelta(7)
:-)
___
Python-Dev mailing list
Python-Dev@python.o
On Tue, Feb 19, 2019 at 12:45 PM Steve Dower wrote:
> On 19Feb2019 1141, Barry Warsaw wrote:
> > Steve Dower wrote on 2/16/19 14:34:>
> >> This is mostly about being able to assign blame when things break, so
> >> I'm totally okay with extension modules that want to play with internals
> >> decla
Hi,
If Python 3.4 was the current version when a bug was reported, I would
expect the version field of the bug set to Python 3.4. Maybe the bug
has been fixed in the meanwhile, maybe not. Closing all bugs affected
to 3.4 is a risk of loosing useful information on real bugs: closed
bugs are ignored
Hi Steve,
I reply on the mailing list
On 02/20, Steve Dower wrote:
It'll make same noise, sure, but if we schedule a bulk close of issues
that have not been touched since 3.6 was released then at least it'll be
easy to "mark all as read". And searching for current issues will become
easier.
As
I am against a mass changing the status of issue, since this will
generate an enormous amount of noise (to me at least). But you are
free to update issues one by one if you can to do some progress with
them.
Sure, I don't want to update them massively, just one by one.
But I prefer to ask befor
20.02.19 17:01, Stephane Wirtel пише:
As you know, Python 3.4 and 3.5 are in security mode and the EOL for
these versions are respectively 2019-03-16 and 2020-09-13.
Number of issues
3.4: 1530 issues
3.5: 1901 issues
But some issues are not related to the security.
Could we update these issue
On 20Feb.2019 0711, Stephane Wirtel wrote:
> After discussion with Victor, my proposal will generate noise with the
> ML, maybe for nothing.
>
> On 02/20, Stephane Wirtel wrote:
>> Hi,
>>
>> As you know, Python 3.4 and 3.5 are in security mode and the EOL for
>> these versions are respectively 201
After discussion with Victor, my proposal will generate noise with the
ML, maybe for nothing.
On 02/20, Stephane Wirtel wrote:
Hi,
As you know, Python 3.4 and 3.5 are in security mode and the EOL for
these versions are respectively 2019-03-16 and 2020-09-13.
Number of issues
3.4: 1530 issues
Hi,
As you know, Python 3.4 and 3.5 are in security mode and the EOL for
these versions are respectively 2019-03-16 and 2020-09-13.
Number of issues
3.4: 1530 issues
3.5: 1901 issues
But some issues are not related to the security.
Could we update these issues (non-security) to 3.6/3.7 & 3.8?
Timeout (360 seconds) reached; failed to start emulator
---> Device ready.
---> Install Python on the emulator.
/home/pydev/build/python-native/python -B
/home/pydev/abifa/Android/tools/install.py
error: device 'emulator-5556' not found
I can reproduce this error after removing the kvm kernel m
11 matches
Mail list logo
