Message154273
| Author |
pitrou |
| Recipients |
brett.cannon, eric.snow, nadeem.vawda, ncoghlan, pitrou, skrah |
| Date |
2012年02月25日.17:07:12 |
| SpamBayes Score |
3.3002311e-06 |
| Marked as misclassified |
No |
| Message-id |
<1330189417.3400.4.camel@localhost.localdomain> |
| In-reply-to |
<1330189193.32.0.150795755914.issue14080@psf.upfronthosting.co.za> |
| Content |
Le samedi 25 février 2012 à 16:59 +0000, Stefan Krah a écrit :
> Bad version:
>
> $ ./python -m test test_dot
> [1/1] test_dot
> 1330188676.0 1330188676.0
This might be what triggers the issue, but it's not the cause. Even with
a bad mtime, the __file__ should still be the right one, so there must
be something else.
> It looks like os.stat.st_mtime returns full seconds here on Ubuntu:
It probably depends on the filesystem. |
|