Skip to content

Python conventions improvements ideas #331

Description

@se7entyse7en

The current status of python conventions is a bit poor. Here are some of the things that I think could be decided and that would help to improve consistency across python projects:

  • supported versions: from some slack discussions it seems to be >=3.5, they could be tested only on travis or using for example tox
  • deps management, packaging and publishing: pip + requirements.txt, pipenv, poetry (I personally like poetry as it also handles packaging and publishing)
  • packaging and publishing: setup.py + twine, poetry
  • virtualenvs compatibility: should the project be compatible only with virtualenvs or maybe even conda?
  • best practices: a common configuration for flake, usage of other tools such as isort for imports sorting

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions