Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pypy pypy
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 674
    • Issues 674
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PyPyPyPy
  • pypypypy
  • Merge requests
  • !428

Follow_symlinks

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Ronan Lamy requested to merge branch/follow_symlinks into branch/py3k Apr 16, 2016
  • Overview 14
  • Commits 19
  • Pipelines 0
  • Changes 3

Finish implementing the 3.3 extensions to existing os functions. All relevant CPython tests now pass (linux64).

I see 2 parts of this PR warranting discussion:

  • The creation of Path objects: I'm not too happy about it, but it mimics what CPython does and I could find no other reasonable way of reproducing CPython's behaviour.

  • space.bytes_w was changed to query the buffer protocol. This matches what CPython does in several cases, including every single function defined in posix.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: branch/follow_symlinks