[issue36439] Inconsistencies with datetime.fromtimestamp(t) when t < 0

2020-06-10 Thread Paul Anton Letnes


Paul Anton Letnes  added the comment:

I've encountered an issue on anaconda python on windows 10 v1909 which I 
suspect is related. It looks like no dates in 1970 can be converted to 
datetime.timestamp():

Python 3.8.2 (default, Apr 14 2020, 19:01:40) [MSC v.1916 64 bit (AMD64)]
Type 'copyright', 'credits' or 'license' for more information
IPython 7.13.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: import datetime

In [2]: datetime.datetime(1970, 1, 2, 0, 0, 1, 123456).timestamp()
---
OSError   Traceback (most recent call last)
 in 
> 1 datetime.datetime(1970, 1, 2, 0, 0, 1, 123456).timestamp()

OSError: [Errno 22] Invalid argument

In [3]: datetime.datetime(1971, 1, 2, 0, 0, 1, 123456).timestamp()
Out[3]: 31618801.123456

--
nosy: +Paul Anton Letnes

___
Python tracker 
<https://bugs.python.org/issue36439>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue38734] Python 3.7 and 3.8 in Windows Store do not start under git bash

2019-11-07 Thread Paul Anton Letnes


New submission from Paul Anton Letnes :

Python 3.7 and 3.8 installed from the  Windows Store do not start under git 
bash. Rather, they give some variation of this error message:

bash: /c/Users/pa/AppData/Local/Microsoft/WindowsApps/python: Permission denied

However, the permissions are rwxr-xr-x, or 755 if you prefer. The same error 
occurs if I try to run pip.

How can I run python under git bash? I use python and various pip-installed 
executables (e.g. black) for git hooks, so this has to work for my workflow.

--
components: Windows
messages: 356183
nosy: paul.moore, pletnes, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Python 3.7 and 3.8 in Windows Store do not start under git bash
type: crash
versions: Python 3.7, Python 3.8

___
Python tracker 
<https://bugs.python.org/issue38734>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue10708] Misc/porting should be folded into the development FAQ or the devguide

2015-08-03 Thread Paul Anton Letnes

Paul Anton Letnes added the comment:

I believe someone should also commit the following command:
hg rm Misc/porting
in the main python repository, since the contents of this file are now found in 
the devguide.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10708
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue10708] Misc/porting should be folded into the development FAQ or the devguide

2015-06-23 Thread Paul Anton Letnes

Paul Anton Letnes added the comment:

I created a patch to the devguide with some rewording as necessary. As I am not 
an expert on porting Python, it would be great if someone could point out any 
mistakes I made. The new FAQ is at the very bottom of the file, as I didn't 
find any other category to place it in.

If people port Python to new platforms on a regular basis, I suggest adding a 
hint to discuss it on some mailing list, or that this FAQ is expanded into a 
more substantial piece of documentation. But then, I guess few people have an 
issue with Python not building on their system these days?

Branch on bitbucket:
issue10708-move-porting-to-devguide

--
hgrepos: +314
keywords: +patch
nosy: +pletnes
Added file: 
http://bugs.python.org/file39786/issue10708-move-porting-to-devguide.patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10708
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue20741] Documentation archives should be available also in tar.xz format

2015-06-19 Thread Paul Anton Letnes

Paul Anton Letnes added the comment:

The format (xz vs bzip2) might not matter much, but I'd say consistency does. 
I'd make the formats identical just for the sake of standardization.

Where is this decided? In some (post)build script?

--
nosy: +pletnes

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20741
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com