Skip to content

Deprecate legacy API in favor of traversable API (files) #80

Closed
@jaraco

Description

@jaraco

The files() API completely supersedes the earlier APIs through a simpler and more intuitive interface. In order to achieve "one and preferably only one" interface for the same behavior, it's desirable to remove the legacy API.

In GitLab by @jaraco on Feb 22, 2020, 09:33

Following from !76 and this comment, I'd like to explore what the implementation would look like with only the traversable API. In that comment, I wrote:

I've started stripping out [the legacy] functionality in the feature/drop-legacy-api branch. Progress was good, but I got stumped on Traversable.open() for zip files, which doesn't support text-decoding. This leads me to believe that's a feature zipp should support. This also suggests the Traversable API should include .open().

Plan

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions