New submission from Mba :
Steps to reproduce the bug:
```
>>> import sys
>>> sys.version
'3.6.7 (v3.6.7:6ec5cf24b7, Oct 20 2018, 13:35:33) [MSC v.1900 64 bit (AMD64)]'
>>> import datetime
>>> print(datetime.datetime.now().astimezone().tzinfo)
datetime
Mba added the comment:
> I don't think that a filesystem produce inodes larger than 2^63-1
The problem is real: the large inode number was assigned to a file created by
MacOS on a share exported via CIFS, and then stated by Linux using NFS exp
Changes by Mba <mba.ogo...@gmail.com>:
--
components: -Library (Lib)
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue29619>
___
_
New submission from Mba:
ino_t is of type 'unsigned long' or 'unsigned long long'. Casting it to signed
type means that negative values are incorrectly returned for large inodes.
--
components: Library (Lib)
messages: 288355
nosy: mba
priority: normal
severity: normal
status: open
