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

Update setup.py #2092

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update setup.py #2092

wants to merge 1 commit into from

Conversation

tejhande
Copy link

  1. File Handling Errors: Proper error handling added for file operations to handle scenarios like file not found or inaccessible.

  2. Dependency Resolution Issue: Improved method for parsing requirements.txt to ensure robustness and reliability.

  3. Entry Point Specification: Ensure correct definition of the console_scripts entry point and corresponding function or CLI.

  4. Documentation Improvement: Enhance documentation to provide clearer instructions and usage details.

  5. Versioning: Ensure adherence to Semantic Versioning guidelines for package versioning.

  6. Code Formatting: Consistent code formatting can be enforced using tools like black, flake8, and isort.

  7. Testing: Include unit tests to verify package functionality and prevent regressions.

  8. License File: Include a LICENSE file in the distribution to clarify licensing terms.

1. File Handling Errors: Proper error handling added for file operations to handle scenarios like file not found or inaccessible.

2. Dependency Resolution Issue: Improved method for parsing requirements.txt to ensure robustness and reliability.

3. Entry Point Specification: Ensure correct definition of the console_scripts entry point and corresponding function or CLI.

4. Documentation Improvement: Enhance documentation to provide clearer instructions and usage details.

5. Versioning: Ensure adherence to Semantic Versioning guidelines for package versioning.

6. Code Formatting: Consistent code formatting can be enforced using tools like black, flake8, and isort.

7. Testing: Include unit tests to verify package functionality and prevent regressions.

8. License File: Include a LICENSE file in the distribution to clarify licensing terms.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant