Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Isn't cwd a filesystem property, not a path propery?

Open
  • Is something wrong?
#24 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
operating-systems

Research direction

Review the existing Path and filesystem abstraction to determine how the current working directory is represented. Investigate Windows drive-specific working directories and decide whether cwd belongs to each filesystem rather than each Path. Done means the ownership model is resolved and Windows behavior is covered, but the issue names no files or tests to start from.

Written by the indexing model from the issue text.

Description

It seems to me that the current working directory would be a property of a filesystem, not a Path. Each filesystem could have it's own working directory. On Windows, each drive actually has its own working directory... but anyways, whatever is up with that needs to be covered with finishing out Windows support.

Dominant language
Python
Stars
2
Forks
6
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Julian/Filesystems

All issues in Julian/Filesystems

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.