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

Added Ultralytics' open-source AGPL-3.0 license headers to all Python files in the repository.

📊 Key Changes

• Inserted the Ultralytics 🚀 AGPL-3.0 License header into the top of all scripts and modules in the repository.
• Made minor formatting enhancements in test cases, improving code readability (e.g., assertion statement adjustments).

🎯 Purpose & Impact

• Purpose: To comply with Ultralytics’ licensing requirements and ensure proper attribution in the project. The AGPL-3.0 license promotes open-source collaboration while protecting intellectual property.
• Impact:
  • 🛡️ Brings the project in line with licensing standards, securing legal compliance.
  • 🌐 Encourages transparency and open usage for users and contributors.
  • Enhances maintainability with better code clarity in some test cases.

[UltralyticsAssistant]

👋 Hello @pderrenger, thank you for submitting a ultralytics/thop 🚀 pull request!
To help ensure a smooth review and integration process, here’s a quick checklist of best practices to follow:

• ✅ Define a Purpose: Please ensure your PR description clearly explains the purpose of your changes and the problem they aim to address. If this is related to an issue, kindly link to the relevant issue thread for better context.
• ✅ Limit Changes: Ensure that your changes are scoped to addressing the specific issue or addition and do not include unnecessary code modifications. This keeps the review focused!
• ✅ Synchronize with Source: Please confirm that your PR is up-to-date with the latest main branch of ultralytics/thop. If not, use git pull or click 'Update branch' to avoid conflicts.
• ✅ Pass CI Checks: Verify that all Continuous Integration (CI) checks have passed. If any fail, review the logs to identify and resolve issues.
• ✅ Improve Documentation: If relevant, update documentation in the repository to reflect your changes. Learn more about contributing guidelines here.
• ✅ Sign the CLA: If this is your first contribution to Ultralytics, please sign the Contributor License Agreement (CLA) by commenting "I have read the CLA Document and I sign the CLA".
• ✅ Include Tests: If applicable, ensure tests are added or updated to validate changes and confirm that all unit tests pass. This helps prevent any potential regressions.

🔄 Key tip: Consider reviewing your diff to trim any unrelated changes or formatting edits unless they are integral to your PR. As Bruce Lee once said, "Hack away the unessential." 😉

For help with resolving failed checks or merging conflicts, feel free to review our help guide.

📌 This is an automated response to help streamline contributions, but an Ultralytics engineer will review and assist with your PR soon. Thank you for contributing to the Ultralytics thop repository! 🚀

[UltralyticsAssistant]

🚀✨ The PR is officially merged — thank you, @pderrenger and @glenn-jocher, for your thoughtful contributions! Adding the Ultralytics AGPL-3.0 license headers is a meaningful step toward fostering open-source collaboration while protecting innovation. Your work ensures we continue to build a transparent, legally sound, and community-driven project.

As Marcus Aurelius once said, "What we do now echoes in eternity." Your efforts today empower countless developers tomorrow. 💡💻 Onward and upward! 🙌