Update requirements.txt

[Acenath]

Thank you 🙏 for your contribution to Ultralytics 🚀! Your effort in enhancing our repositories is greatly appreciated. To streamline the process and assist us in integrating your Pull Request (PR) effectively, please follow these steps:

1. Check for Existing Contributions: Before submitting, kindly explore existing PRs to ensure your contribution is unique and complementary.

2. Link Related Issues: If your PR addresses an open issue, please link it in your submission. This helps us better understand the context and impact of your contribution.

3. Elaborate Your Changes: Clearly articulate the purpose of your PR. Whether it's a bug fix or a new feature, a detailed description aids in a smoother integration process.

4. Ultralytics Contributor License Agreement (CLA): To uphold the quality and integrity of our project, we require all contributors to sign the CLA. Please confirm your agreement by commenting below:

   I have read the CLA Document and I hereby sign the CLA

For more detailed guidance and best practices on contributing, refer to our ✅ Contributing Guide. Your adherence to these guidelines ensures a faster and more effective review process.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

This PR updates dependencies and streamlines API and logger documentation for YOLOv5.

📊 Key Changes

• Upgraded the minimum required version of matplotlib from 3.3 to 3.4 in requirements.txt.
• Improved formatting and removed unnecessary white spaces in README.md files of Flask REST API, ClearML, and Comet logger utilities.

🎯 Purpose & Impact

• Upgrading matplotlib: Ensures compatibility with newer features and improvements in data visualization 📈.
• Documentation cleanup: Provides clearer, more concise instructions for using REST APIs and logging utilities, improving user experience and facilitating integration with YOLOv5 for model exposure, experiment tracking, and hyperparameter optimization 📚.
• These changes are mostly non-functional but can potentially improve the ease-of-use, maintainability of the codebase, and enhancement of user learning for those integrating YOLOv5 into their projects 🤖.

[github-actions]

👋 Hello @Acenath, thank you for submitting a YOLOv5 🚀 PR! To allow your work to be integrated as seamlessly as possible, we advise you to:

• ✅ Verify your PR is up-to-date with ultralytics/yolov5 master branch. If your PR is behind you can update your code by clicking the 'Update branch' button or by running git pull and git merge master locally.
• ✅ Verify all YOLOv5 Continuous Integration (CI) checks are passing.
• ✅ Reduce changes to the absolute minimum required for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

[Acenath]

For experiment only not important

[glenn-jocher]

@Acenath hi there!

Thank you so much for your willingness to contribute to the YOLOv5 project! 🌟 Your efforts are truly valued by the entire community.

To proceed with your PR for updating the requirements.txt, please ensure you've followed the steps you've outlined:

1. Check for any existing PRs that might already address the same update to avoid duplication.
2. If your PR is related to an open issue, make sure to link it for context.
3. Provide a clear and concise description of the changes you're proposing.
4. Lastly, confirm your acceptance of our CLA with a comment: "I have read the CLA Document and I hereby sign the CLA".

Once you've taken care of these steps, we'll be in a great position to review and potentially merge your changes.

For any further details on contributing, our contributing guide is always available for reference. Thanks again for your support! 🚀