Skip to content

Add requirements.txt and .gitignore #3

@prateekj117

Description

@prateekj117

It's always better to have a requirements.txt file as it helps to make sure everyone is using the correct version of the dependency. It can otherwise lead to a massacre when a community is helping out with a project and can lead to a lot of confusion. It can lead to some people experiencing errors which are not actually related to project but because of different version of a dependency being used. It would also help with the easier setup of a virtual environment addressed in #2.

We should also add a .gitignore so that files that should not be committed don't get committed. For example .idea and .code files. I also see database.sqlite3 committed here which should not be done.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions