Timeline


and

2014-10-04:

20:17 Changeset [1585:654ffd48590d] by Stefan Schwarzer <sschwarzer@…>
default"Also see" -> "See also".
19:16 Ticket #83 (Crash on ibiblio.org) closed by schwa
fixed: This should be fixed now (stretched out over several commits). If the …
19:12 Changeset [1584:589885ddb72e] by Stefan Schwarzer <sschwarzer@…>
defaultAdded announcement for next version, 3.2.
19:07 Changeset [1583:83918d4f5088] by Stefan Schwarzer <sschwarzer@…>
defaultUpdated `README.txt` with changes for new release.
18:43 Changeset [1582:8e468c5979b6] by Stefan Schwarzer <sschwarzer@…>
defaultUpdate version to 3.2.
18:43 Changeset [1581:5c6832f729b7] by Stefan Schwarzer <sschwarzer@…>
defaultDocument special handling of pre-epoch datetimes for `stat`/`lstat`.
18:38 Changeset [1580:95647a76b6c5] by Stefan Schwarzer <sschwarzer@…>
defaultBe 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).
18:20 Changeset [1579:7146d114d459] by Stefan Schwarzer <sschwarzer@…>
defaultUse `UNKNOWN_PRECISION` for pre-epoch datetimes.
18:12 Changeset [1578:bca0ec28c76c] by Stefan Schwarzer <sschwarzer@…>
defaultMove tests for valid unix lines before tests for invalid lines.
18:11 Changeset [1577:eebe89a0505b] by Stefan Schwarzer <sschwarzer@…>
defaultSmall formatting change for sole `]` for closing a list.
18:08 Changeset [1576:f2998542a221] by Stefan Schwarzer <sschwarzer@…>
defaultUse named constants for datetime precisions. In unit tests, explicitly test for precision values.
17:46 Changeset [1575:87c82eae29b6] by Stefan Schwarzer <sschwarzer@…>
defaultAdded comment on pre-epoch datetimes.
17:36 Changeset [1574:b3b06ecffc0a] by Stefan Schwarzer <sschwarzer@…>
defaultAdded a test for MS parser for pre-epoch years (see ticket #83).
17:34 Changeset [1573:663b036bb8f7] by Stefan Schwarzer <sschwarzer@…>
defaultUse more specific error handling when parsing datetimes.
17:14 Changeset [1572:79363bf644de] by Stefan Schwarzer <sschwarzer@…>
defaultRaise a `ParserError` if the day value isn't an integer.
17:11 Changeset [1571:2d21406a6d7f] by Stefan Schwarzer <sschwarzer@…>
defaultFix error handling for invalid datetime components (e. g. day == 32).
16:59 Changeset [1570:2043671d14fa] by Stefan Schwarzer <sschwarzer@…>
defaultHandle 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 .
16:56 Changeset [1569:20521872d3ff] by Stefan Schwarzer <sschwarzer@…>
defaultUse more straightforward tests for datetimes before the epoch.
13:41 Changeset [1568:9f7123eafbab] by Stefan Schwarzer <sschwarzer@…>
defaultReverted 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
09:19 Ticket #85 (UnicodeDecodeError in FTPFile.close()) closed by schwa
fixed: The problem should be fixed in [406c84da6e3b]. Lacking an answer from …

2014-09-15:

10:41 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 …

2014-09-09:

23:39 WikiStart edited by schwa
(diff)

2014-07-23:

21:51 WikiStart edited by schwa
(diff)

2014-07-15:

11:41 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.