Standardize license headers in Python files

[pderrenger]

This PR updates all Python file headers to use a standardized license format. 🔄

Changes:

• 📝 Standardized header: # Ultralytics 🚀 AGPL-3.0 License - https://ultralytics.com/license
• 🧹 Ensures consistent spacing after headers
• 🔍 Applies to all Python files except those in venv

Learn more about Ultralytics licensing 📚

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

This PR updates licensing headers across all source files in the YOLOv5 repository for clarity and consistency.

📊 Key Changes

• Updated license headers from "Ultralytics YOLOv5 🚀, AGPL-3.0 license" to "Ultralytics 🚀 AGPL-3.0 License - https://ultralytics.com/license" in all files.
• Slight restructuring of some assert and error messages for readability and formatting.

🎯 Purpose & Impact

• Purpose:

  • Provide a consistent and clear reference to the open-source AGPL-3.0 license and the Ultralytics licensing page.
  • Enhance uniformity in licensing documentation across the codebase.

• Impact:

  • Helps users, developers, and contributors better understand licensing terms.
  • No functional changes—users will not experience any behavior or performance differences. 📜✨

[UltralyticsAssistant]

👋 Hello @pderrenger, thank you for submitting a PR to the ultralytics/yolov5 🚀 repository! To help us streamline the review and integration process, please review the following checklist:

• ✅ Purpose: Clearly articulate the purpose of your PR. For example, does it address a bug, enhance functionality, or improve documentation? If related to an issue, link it in your description (i.e., relevant issues). Please confirm your commit messages are clear and follow the repository's conventions.
• ✅ Branch Synchronization: Ensure your branch is updated with the latest main branch. This can be done by clicking the 'Update branch' button on GitHub or running git pull and git merge main locally.
• ✅ Passing CI: Verify that all Continuous Integration (CI) checks pass. If they fail, please resolve the identified issues.
• ✅ Documentation: Update any relevant documentation to reflect the changes introduced by your PR.
• ✅ Testing: If applicable, please include new tests or updates to cover the proposed changes and confirm that they all pass.
• ✅ CLA: If this is your first time contributing, make sure to sign our Contributor License Agreement (CLA) by commenting "I have read the CLA Document and I sign the CLA" in this thread.
• ✅ Efficiency: Keep changes limited to the essential updates to address the scope of your PR. As Bruce Lee said, "Hack away at the unessential." 🥋

For detailed guidelines, please refer to our Contributing Guide. ⚡

PULL REQUEST TITLE:

Standardize license headers in Python files

PULL REQUEST DESCRIPTION:

This PR introduces a consistent license header format throughout the repository for better attribution and clarity. Thank you for taking the time to ensure our licensing information is uniform! 📜

REMINDER:

If your PR is addressing a bug, kindly provide a minimum reproducible example (MRE) if you haven’t done so already. This greatly assists us in validating the fix efficiently.

An Ultralytics engineer will review and provide feedback soon. Let us know if you need further assistance or have additional comments. Thanks again for supporting Ultralytics! 😊🚀

[UltralyticsAssistant]

🎉 The PR is officially merged—thank you, @pderrenger, with contributions from @glenn-jocher, for leveling up YOLOv5's licensing clarity and consistency! 🚀 These updates may seem subtle but carry profound importance, embodying transparency and accessibility for the community.

As Marcus Aurelius once said, "What we do now echoes in eternity." Your meticulous efforts today ensure that the spirit of open-source collaboration and shared understanding continues to thrive for future contributors and users alike. 🌟 Thank you for making a difference! 🙌