Dev environment has been removed, but docs aren't updated?

Open
#626 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Start by reading the repository's current setup instructions and checking how the development environment, conda, and tox are described. Confirm whether the referenced dev environment still exists, then update the documentation to explain the current setup and patch-submission workflow. Done means a newcomer can follow the revised instructions without relying on the removed environment.

Written by the indexing model from the issue text.

Description

Hey, fsspec! I'm trying to follow your setup instructions for submitting some patches, and i'm noticing that there's no dev environment as far as I can tell anymore. Is this intentional? What should the docs say instead?

I'm also a total noob at conda + tox, so this could be my bad :p

Dominant language
Python
Stars
1.4k
Forks
490
Avg merge
2d 3h
Merged PRs (30d)
38

Contributor guide

No contributing guide indexed for this repository

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 fsspec/filesystem_spec

All issues in fsspec/filesystem_spec

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.