Fix too many open files error

[armallen]

Bugfix for #271
Opening all files at once does not seem necessary. fix_files already handles str file paths and opens them automatically.

Also,

• maison 2.0.0 was released today and introduces breaking changes (maison.schema does not exist anymore), so dependency rules are updated to be a bit more restrictive. Updated to maison 2.0.0 will require a separate PR.
• black is updated to >=24.3 to fix a vulnerability issue detected by safety
• a .safety-policy.yml file is generated to ignore a jinja2 3.1.4 vulnerability that can probably be ignored since we don't use jinja2's from_string function?

Checklist

• Add test cases to all the changes you introduce -> No new test needed
• Update the documentation for the changes -> No update needed

[coveralls]

Pull Request Test Coverage Report for Build 10491853708

Details

• 7 of 7 (100.0%) changed or added relevant lines in 3 files are covered.
• 3 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.6%) to 98.984%

---

Files with Coverage Reduction	New Missed Lines	%
src/yamlfix/services.py	3	93.65%

Totals
Change from base Build 6968562450:	-0.6%
Covered Lines:	487
Relevant Lines:	492

---

💛 - Coveralls

[armallen]

make sure we don't use neither maison 2.0.0 (breaks interface) nor maison 1.4.3 (which updates to pydantic 2.X and causes other incompatibilities with other dependencies).

[lyz-code]

Hi @armallen can you please either:

• Fix the code to support maison > 2.0.0
• Open an issue to support maison > 2.0.0 and add a comment above the line you edited in the PR?

[gandhis1]

It would have been ideal to have first released a version that pinned maison to <1.4.3 and still supported Python 3.8 before subsequently releasing a version that dropped support for Python 3.8 with the latest maison. This would have allowed people who are still on Python 3.8 to pin their yamlfix version. As it stands, I don't think any existing version of yamlfix will work with Python 3.8 because of the maison issue.

Is this still possible?

[lyz-code]

Hi @gandhis1, you are right, sorry for the inconveniences. I've created a new branch python3.8 and released version 1.16.1 with the fixed dependencies.

[armallen]

@lyz-code do you have time to review this in the following weeks by any chance? 🙏

[lyz-code]

Thank you @armallen for your contribution and the clear comments in the PR (•‿•)

I do not like upper pinning dependencies without a reason, would you mind addressing the comment I've done?

Thank you

[lyz-code]

Hi @armallen can you please either:

• Fix the code to support maison > 2.0.0
• Open an issue to support maison > 2.0.0 and add a comment above the line you edited in the PR?

[armallen]

@lyz-code I went for the update to maison 2.0.0, which requires updating python min version to 3.9.1 and adding pydantic as a dependency.

[lyz-code]

Wow, awesome! thank you so much for the contribution

[lyz-code]

Available since 1.17.0 thanks @armallen