Update requirements.txt

[RANJITHROSAN17]

📋 Checklist

• I have tested the updated requirements.txt in a fresh environment
• All dependencies are compatible with Ultralytics v8
• Comments and structure are cleaned and clarified

📄 CLA Agreement

I have read the CLA Document and I 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

Improved the requirements.txt file by adding helpful comments, clarifying package purposes, and updating some version recommendations for better usability and clarity. 📝✨

📊 Key Changes

• Added descriptive comments next to each package to explain its role.
• Updated some package version requirements (e.g., matplotlib now >=3.5.0, psutil now >=5.9.0).
• Recommended Python 3.8 or higher.
• Grouped optional dependencies (for logging, export, deployment, and extras) with clear section headers and explanations.
• Enhanced readability and maintainability of the requirements file.

🎯 Purpose & Impact

• Easier for users to understand which packages are needed and why, making setup and troubleshooting simpler.
• Improves onboarding for new contributors and users by providing clear guidance.
• Reduces confusion about optional vs. required dependencies.
• Helps maintainers keep track of package roles and update requirements more efficiently.

[github-actions]

All Contributors have signed the CLA. ✅
_{Posted by the CLA Assistant Lite bot.}

[UltralyticsAssistant]

👋 Hello @RANJITHROSAN17, thank you for submitting a ultralytics/yolov3 🚀 PR! This is an automated response to help streamline the review process—an Ultralytics engineer will also assist you soon.

Please review the following checklist to ensure your PR is set up for a smooth integration:

• ✅ Define a Purpose: Make sure your PR description clearly states the purpose of your update and links to any relevant issues. Please keep commit messages clear and concise, following the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is up to date with the main branch of ultralytics/yolov3. If needed, update it by clicking 'Update branch' or running git pull and merging main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please resolve them.
• ✅ Update Documentation: For any new or modified features, update the relevant documentation.
• ✅ Add Tests: If your changes impact functionality, please add or update tests and confirm they all pass.
• ✅ Sign the CLA: Since you've indicated you've signed our Contributor License Agreement (CLA), thank you! If you haven't, please do so by writing "I have read the CLA Document and I sign the CLA" in a new comment.
• ✅ Minimize Changes: Please keep your changes to the minimum necessary for this update. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For detailed guidelines, see our Contributing Guide. If you have any questions, drop a comment here. Thank you for helping improve Ultralytics! 🌟🛠️

[RANJITHROSAN17]

I have read the CLA Document and I sign the CLA

[glenn-jocher]

@RANJITHROSAN17 looks great, thank you!

[UltralyticsAssistant]

🎉 Fantastic work, @RANJITHROSAN17 and @glenn-jocher! Your improvements to the requirements file bring clarity and ease to everyone working with Ultralytics YOLOv3. As Leonardo da Vinci said, "Simplicity is the ultimate sophistication"—and your thoughtful updates make onboarding smoother and maintaining dependencies much simpler for all users and contributors. Thank you for your dedication and attention to detail. Your contributions truly help strengthen the Ultralytics community! 🚀