Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve README #30

Open
buhtz opened this issue Sep 1, 2022 · 3 comments
Open

Improve README #30

buhtz opened this issue Sep 1, 2022 · 3 comments

Comments

@buhtz
Copy link

buhtz commented Sep 1, 2022

I found an ITP on the debian-python list about your project.
Sorry, I don't understand all details.

Can you improve your README and explain a bit more detailed what the package does and what the advantage is here. Currently I don't see an advantage.

I only see very simple path handling which could be done by or via pathlib itself also. What does your package add to the pathlib functionality?

@jamesmyatt
Copy link
Contributor

@buhtz
Copy link
Author

buhtz commented Sep 1, 2022

Sorry, I don't get it. I don't find it complicated but pretty simple.

The project folder is very the py-file is. Or when you store your py files on sub-folder done in your project folder to ../data/file.csv or something like that.

It is easier to understand if you would create an example and show the tree output. Maybe than it becomes clearer.

@jamesmyatt
Copy link
Contributor

jamesmyatt commented Nov 20, 2022

Best practice is to store the data files and notebooks/script files in separate directories, e.g. https://drivendata.github.io/cookiecutter-data-science/. For example, you might also use sub-directories within the "notebooks" directory to further organise the notebooks by purpose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants