Timeline



Oct 4, 2014:

8:17 PM Changeset [1585:654ffd48590d] by Stefan Schwarzer <sschwarzer@…>
"Also see" -> "See also".
7:16 PM Ticket #83 (Crash on ibiblio.org) closed by schwa
fixed: This should be fixed now (stretched out over several commits). If the …
7:12 PM Changeset [1584:589885ddb72e] by Stefan Schwarzer <sschwarzer@…>
Added announcement for next version, 3.2.
7:07 PM Changeset [1583:83918d4f5088] by Stefan Schwarzer <sschwarzer@…>
Updated `README.txt` with changes for new release.
6:43 PM Changeset [1582:8e468c5979b6] by Stefan Schwarzer <sschwarzer@…>
Update version to 3.2.
6:43 PM Changeset [1581:5c6832f729b7] by Stefan Schwarzer <sschwarzer@…>
Document special handling of pre-epoch datetimes for `stat`/`lstat`.
6:38 PM Changeset [1580:95647a76b6c5] by Stefan Schwarzer <sschwarzer@…>
Be explicit about unknown datetime precisions. Instead of relying on default handling of pre-epoch times, explicitly consider unknown precisions and in this case, consider the source file newer. That is, if in doubt, transfer the file (as was the assumption before).
6:20 PM Changeset [1579:7146d114d459] by Stefan Schwarzer <sschwarzer@…>
Use `UNKNOWN_PRECISION` for pre-epoch datetimes.
6:12 PM Changeset [1578:bca0ec28c76c] by Stefan Schwarzer <sschwarzer@…>
Move tests for valid unix lines before tests for invalid lines.
6:11 PM Changeset [1577:eebe89a0505b] by Stefan Schwarzer <sschwarzer@…>
Small formatting change for sole `]` for closing a list.
6:08 PM Changeset [1576:f2998542a221] by Stefan Schwarzer <sschwarzer@…>
Use named constants for datetime precisions. In unit tests, explicitly test for precision values.
5:46 PM Changeset [1575:87c82eae29b6] by Stefan Schwarzer <sschwarzer@…>
Added comment on pre-epoch datetimes.
5:36 PM Changeset [1574:b3b06ecffc0a] by Stefan Schwarzer <sschwarzer@…>
Added a test for MS parser for pre-epoch years (see ticket #83).
5:34 PM Changeset [1573:663b036bb8f7] by Stefan Schwarzer <sschwarzer@…>
Use more specific error handling when parsing datetimes.
5:14 PM Changeset [1572:79363bf644de] by Stefan Schwarzer <sschwarzer@…>
Raise a `ParserError` if the day value isn't an integer.
5:11 PM Changeset [1571:2d21406a6d7f] by Stefan Schwarzer <sschwarzer@…>
Fix error handling for invalid datetime components (e. g. day == 32).
4:59 PM Changeset [1570:2043671d14fa] by Stefan Schwarzer <sschwarzer@…>
Handle invalid datetime components and datetimes before the epoch (see ticket #83). If a component of a parsed datetime is invalid (for example, day is 32), raise a `ParserError`. If the datetime is before the epoch, set the float value for the last modification time to 0.0 .
4:56 PM Changeset [1569:20521872d3ff] by Stefan Schwarzer <sschwarzer@…>
Use more straightforward tests for datetimes before the epoch.
1:41 PM Changeset [1568:9f7123eafbab] by Stefan Schwarzer <sschwarzer@…>
Reverted Philippe's changes to `stat.py`. Using the same exception handling code three times is a bit much. :) Also, the approach doesn't handle "real" errors properly, like a month value 13. That said, the previous code by me doesn't handle this either as it turned out. For example, my Linux system "wraps" invalid values, so the month 13 in year y becomes the month 1 in year y+1. TODO: Use approach outlined in ticket #83: http://ftputil.sschwarzer.net/trac/ticket/83#comment:17
9:19 AM Ticket #85 (UnicodeDecodeError in FTPFile.close()) closed by schwa
fixed: The problem should be fixed in [406c84da6e3b]. Lacking an answer …

Sep 15, 2014:

10:41 AM Ticket #85 (UnicodeDecodeError in FTPFile.close()) created by ftputiluser
ftputil 3.1 Python 2.7.5 Stackless 3.1b3 Here is an extract of the …

Sep 9, 2014:

11:39 PM WikiStart edited by schwa
(diff)

Jul 23, 2014:

9:51 PM WikiStart edited by schwa
(diff)

Jul 15, 2014:

11:41 AM Ticket #84 (ftputil.sync.Syncer should check for local directory) created by ftputiluser
See sync, line 159: …
Note: See TracTimeline for information about the timeline view.