Hi @SoyGema , thank you again for your help!

For tests conditioned by the Python version number, you can use the skipIf method, so it will only be checked depending on the Python version in use. Since the tests in GitHub Actions are verified with all supported versions, both methods will be verified:
https://docs.python.org/3/library/unittest.html#skipping-tests-and-expected-failures
There is no test_utils.py file for the tests of utils.py yet, but you can create one in tests/test_utils.py.

To be able to use the dateutils module in Python 3.10 and earlier, it is necessary to add it to the requirements file, in case the user does not have the module installed. To do this, it is necessary to modify the requirements.in file and then run pip-compile (you need to install pip-tools first using pip install pip-tools!).

However, not all users need this dependency, only users with a version prior to Python 3.11. To do this, the best thing would be to include a line like the following: python-dateutil>=2.8.1; python_version < '3.11'. Remember that in your code, only dateutil should be imported for Python 3.10, so you should change the import to the conditional that Python 3.10 uses.

def parse_iso_datetime(iso_dt):
    if sys.version_info >= (3, 11):
        ...
    else:
        from dateutil import parser as dateutil_parser
        try:
            dt = datetime.fromisoformat(iso_dt)
        except ValueError:
            dt = dateutil_parser.isoparse(iso_dt)
    return dt

I have seen that the GitHub Actions lint is failing due to black validation. Remember to run black in your environment! If you use pre-commit, it is enabled automatically. If not, don't worry, I can check it and take care of it myself.
https://github.com/Nekmo/pip-rating/blob/master/.pre-commit-config.yaml
https://black.readthedocs.io/en/stable/getting_started.html

I know it's a lot to do, but don't worry, we're almost done. I think this should be all we need for the Pull Request. Likewise, I hope I was able to help, if you have any questions, let me know. Thanks for your contribution!

Marty: Doc, I'm starting to think that this ISO date format thing is a conspiracy by the future to keep us from traveling back in time.

Doc: That's a very interesting theory, Marty. But I think it's more likely that it's just a result of the different ways that Python has evolved over time.

Marty: Maybe. But I'm not so sure. I've been seeing some strange things lately. Like the other day, I saw a DeLorean parked in the driveway next to my house. But when I went to investigate, it was gone.

Doc: Marty, you're not imagining things, are you?

Marty: I don't know, Doc. But I'm starting to think that the future is closer than we think.

Doc: Well, if that's the case, we need to be prepared. We need to make sure that our code is ready for anything.

Marty: I'm on it, Doc. I'm going to start working on a new version of the DeLorean code that can handle any date format, past, present, or future.

Doc: Good luck, Marty. And be careful. The space-time continuum is a delicate thing.

Marty: I will, Doc. I will.

Hey!
Please confirm that all is correct and confirm if I'm missing something ? :

• Change import dateutil in function aab358b
• Create test_utils.py add tests with skipIf ( first time Im doing this ) Sorry I copy pasted from other test file and the commit is far from clean ... see the file
• Modified requirements.in 40c54ab

Can you take care of black ? Can you please send me more information about this so I can learn ? black is some sort of prettier reformat ?

Hey! Please confirm that all is correct and confirm if I'm missing something ? :

• Change import dateutil in function aab358b
• Create test_utils.py add tests with skipIf ( first time Im doing this ) Sorry I copy pasted from other test file and the commit is far from clean ... see the file
• Modified requirements.in 40c54ab

Can you take care of black ? Can you please send me more information about this so I can learn ? black is some sort of prettier reformat ?

Yes, this is correct :)

Remember that after adding the dependency to the requirements.in file, you must run pip-compile. This command will also update the requirements.txt file.

Black is a tool that checks if the code complies with the style guide. It automatically rewrites the code if it detects invalid code. You have integrations for different IDEs, but you can also run it manually using:

$ black <file_or_folder>

Install it using Pypi:

$ pip install black

Hello there @Nekmo ! As noted, I runed pip-compile in 62eeb55 and black in 2f8edd1

(base) ➜  pip_rating git:(python_version_iso_dateformat) black rating.py 
reformatted rating.py

All done! ✨ 🍰 ✨
1 file reformatted.

It´s so exciting this is moving forward!
Let me know if there´s something else I´m missing.

Learned a few things thanks to this PR, so thanks for giving me the opportunity to contribute. Thanks also for your guidance and support. Your empathy toward supporting contributors' growth affirms your commitment to the community.
Besides, all Lore has been fun and inspiring, and even though it can be seen as unexpected or abnormal, it really aligns with the contributions OSS values that research studies Fig2 show . Thanks for embodying a mature and supportive OSS governance model through learning, reciprocity, and fun.

Many thanks to you @SoyGema for your help! I'm glad to know that the experience has helped you :) I've re-run the tests for the PR, and as far as I can tell, black would need to be run on the files utils.py and test_utils.py.
https://github.com/Nekmo/pip-rating/actions/runs/6516639916/job/17704754903?pr=47

I need to check how to enable Github Actions tests for Pull Requests... Sorry for the inconvenience!

Marty: But why do we have to run black every time?
Doc: If we had used black from the beginning, we wouldn't have had to travel back in time to fix the problem in the future.
Marty: But then... we wouldn't have traveled back in time, and we wouldn't have had a movie.
Doc: That's also true.

Hey,
No worries at all.
Please check if the three-black-problem works now.

𝙼𝚊𝚛𝚝𝚢: 𝚈𝚘𝚞 𝚔𝚗𝚘𝚠, 𝙳𝚘𝚌, 𝚝𝚑𝚒𝚜 𝚓𝚘𝚞𝚛𝚗𝚎𝚢 𝚝𝚑𝚛𝚘𝚞𝚐𝚑 𝚝𝚑𝚎 𝚠𝚘𝚛𝚕𝚍 𝚘𝚏 𝙿𝚢𝚝𝚑𝚘𝚗 𝚊𝚗𝚍 𝙸𝚂𝙾 𝚍𝚊𝚝𝚎 𝚙𝚊𝚛𝚜𝚒𝚗𝚐 𝚖𝚊𝚍𝚎 𝚖𝚎 𝚊𝚙𝚙𝚛𝚎𝚌𝚒𝚊𝚝𝚎 𝚝𝚑𝚎 𝚙𝚘𝚠𝚎𝚛 𝚘𝚏 𝚊𝚍𝚊𝚙𝚝𝚊𝚋𝚒𝚕𝚒𝚝𝚢 𝚊𝚗𝚍 𝚝𝚑𝚎 𝚟𝚊𝚕𝚞𝚎 𝚘𝚏 𝚐𝚘𝚘𝚍 𝚘𝚕𝚍-𝚏𝚊𝚜𝚑𝚒𝚘𝚗𝚎𝚍 𝚙𝚛𝚘𝚋𝚕𝚎𝚖-𝚜𝚘𝚕𝚟𝚒𝚗𝚐.

𝙳𝚘𝚌: 𝚈𝚘𝚞'𝚟𝚎 𝚐𝚛𝚘𝚠𝚗, 𝙼𝚊𝚛𝚝𝚢. 𝙰𝚗𝚍 𝚛𝚎𝚖𝚎𝚖𝚋𝚎𝚛, 𝚒𝚗 𝚝𝚑𝚎 𝚠𝚘𝚛𝚕𝚍 𝚘𝚏 𝚙𝚛𝚘𝚐𝚛𝚊𝚖𝚖𝚒𝚗𝚐, 𝚎𝚟𝚎𝚛𝚢 𝚌𝚑𝚊𝚕𝚕𝚎𝚗𝚐𝚎 𝚢𝚘𝚞 𝚌𝚘𝚗𝚚𝚞𝚎𝚛 𝚋𝚛𝚒𝚗𝚐𝚜 𝚢𝚘𝚞 𝚘𝚗𝚎 𝚜𝚝𝚎𝚙 𝚌𝚕𝚘𝚜𝚎𝚛 𝚝𝚘 𝚋𝚎𝚌𝚘𝚖𝚒𝚗𝚐 𝚊 𝚝𝚛𝚞𝚎 𝚌𝚘𝚍𝚎 𝚝𝚒𝚖𝚎 𝚝𝚛𝚊𝚟𝚎𝚕𝚕𝚎𝚛.

𝙼𝚊𝚛𝚝𝚢: 𝚃𝚑𝚊𝚗𝚔𝚜, 𝙳𝚘𝚌. 𝚈𝚘𝚞'𝚛𝚎 𝚗𝚘𝚝 𝚓𝚞𝚜𝚝 𝚊 𝚐𝚛𝚎𝚊𝚝 𝚜𝚌𝚒𝚎𝚗𝚝𝚒𝚜𝚝; 𝚢𝚘𝚞'𝚛𝚎 𝚊 𝚐𝚛𝚎𝚊𝚝 𝚝𝚎𝚊𝚌𝚑𝚎𝚛, 𝚝𝚘𝚘.

𝙳𝚘𝚌: 𝙸𝚝'𝚜 𝚋𝚎𝚎𝚗 𝚊𝚗 𝚒𝚗𝚌𝚛𝚎𝚍𝚒𝚋𝚕𝚎 𝚊𝚍𝚟𝚎𝚗𝚝𝚞𝚛𝚎, 𝙼𝚊𝚛𝚝𝚢. 𝙱𝚞𝚝 𝚗𝚘𝚠, 𝚒𝚝'𝚜 𝚝𝚒𝚖𝚎 𝚝𝚘 𝚕𝚎𝚝 𝚢𝚘𝚞 𝚏𝚕𝚢 𝚘𝚗 𝚢𝚘𝚞𝚛 𝚘𝚠𝚗, 𝚠𝚒𝚝𝚑 𝚌𝚘𝚍𝚎 𝚊𝚜 𝚢𝚘𝚞𝚛 𝚝𝚛𝚞𝚜𝚝𝚢 𝚌𝚘𝚖𝚙𝚊𝚗𝚒𝚘𝚗.

𝙼𝚊𝚛𝚝𝚢: 𝙶𝚘𝚘𝚍𝚋𝚢𝚎, 𝙳𝚘𝚌. 𝙸'𝚕𝚕 𝚔𝚎𝚎𝚙 𝚎𝚡𝚙𝚕𝚘𝚛𝚒𝚗𝚐 𝚝𝚑𝚎 𝚝𝚒𝚖𝚎 𝚊𝚗𝚍 𝚜𝚙𝚊𝚌𝚎 𝚘𝚏 𝚌𝚘𝚍𝚎, 𝚊𝚗𝚍 𝙸'𝚕𝚕 𝚗𝚎𝚟𝚎𝚛 𝚏𝚘𝚛𝚐𝚎𝚝 𝚝𝚑𝚎 𝚕𝚎𝚜𝚜𝚘𝚗𝚜 𝙸'𝚟𝚎 𝚕𝚎𝚊𝚛𝚗𝚎𝚍 𝚑𝚎𝚛𝚎.

𝙳𝚘𝚌: 𝙵𝚊𝚛𝚎𝚠𝚎𝚕𝚕, 𝙼𝚊𝚛𝚝𝚢! 𝚁𝚎𝚖𝚎𝚖𝚋𝚎𝚛, 𝚝𝚑𝚎 𝚏𝚞𝚝𝚞𝚛𝚎 𝚒𝚜 𝚠𝚑𝚊𝚝 𝚢𝚘𝚞 𝚖𝚊𝚔𝚎 𝚘𝚏 𝚒𝚝. 𝙰𝚗𝚍 𝚠𝚑𝚘 𝚔𝚗𝚘𝚠𝚜, 𝚘𝚗𝚎 𝚍𝚊𝚢 𝚢𝚘𝚞 𝚖𝚒𝚐𝚑𝚝 𝚓𝚞𝚜𝚝 𝚛𝚎𝚠𝚛𝚒𝚝𝚎 𝚝𝚑𝚎 𝚏𝚞𝚝𝚞𝚛𝚎 𝚘𝚏 𝚙𝚛𝚘𝚐𝚛𝚊𝚖𝚖𝚒𝚗𝚐 𝚒𝚝𝚜𝚎𝚕𝚏!

𝙼𝚊𝚛𝚝𝚢: 𝙳𝚘𝚌, 𝚝𝚑𝚎 𝚌𝚘𝚍𝚎 𝚒𝚜 𝚖𝚢 𝙳𝚎𝙻𝚘𝚛𝚎𝚊𝚗. 𝚃𝚑𝚎 𝚊𝚍𝚟𝚎𝚗𝚝𝚞𝚛𝚎 𝚌𝚘𝚗𝚝𝚒𝚗𝚞𝚎𝚜.

Everything is fine, thanks! It's already merged :) I hope to be able to count on you in the future.

Doc: This adventure may have ended, but it is only the beginning of new adventures. As long as we can code, we will never stop enjoying and discovering new things.

Marty: And I hope to be there so that we can discover them together.

@SoyGema I have added you to the collaborators file. If you want me to remove you, let me know and I'll remove you :)

@SoyGema I have added you to the collaborators file. If you want me to remove you, let me know and I'll remove you :)

Hey Thanks! That means a lot 🥹