fix: get_size should always return size as tuple of int

[fabien-michel]

self.picture.width (and height) are now float (since django-filer PR#1226)

Description

Since the following django-filer PR: django-cms/django-filer#1226
the FilerImageField width and height are now float.

We expect get_size to return always int.

Related resources

#108

Checklist

• I have opened this pull request against master
• I have added or modified the tests when changing logic
• I have followed the conventional commits guidelines to add meaningful information into the changelog
• I have read the contribution guidelines and I have joined #workgroup-pr-review on
  Slack to find a “pr review buddy” who is going to review my pull request.

[vinitkumar]

@fabien-michel What happens if someone updates the picture plugin and is still on the old version o filer? Will this break?

[fabien-michel]

No, I don't see any case where it can break something. The old filer version behavior was to return int, so parsing int to int is ok.

[marksweb]

@fabien-michel are you able to resolve conflicts please? We've not got permissions to modify this PR

[codecov]

Codecov Report

Merging #111 (42818c9) into master (de8a8cd) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #111   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           15        15           
  Lines          242       244    +2     
  Branches        45        45           
=========================================
+ Hits           242       244    +2     

Impacted Files	Coverage Δ
djangocms_picture/models.py	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[fsbraun]

I assume the tests would run through if you changed

djangocms-picture/tests/test_migrations.py

Line 22 in de8a8cd

call_command('makemigrations', **options)

to

 call_command('makemigrations', 'djangocms_picture', **options)

(The migration test creates migrations for django cms 3.9 which is not due to djangocms_picture. From my point of view it should be sufficient to test if this app has all migrations it needs.)

[fabien-michel]

@fsbraun Thanks for the suggestions on test fail. But I still dont understand why I need to do changes on test_migrations.py since I didn't change anything related to the database.

[marksweb]

@fabien-michel the suggestion to make the change is because the test is failing due to external apps creating migration files. So making the change suggested by @fsbraun causes the test to only try to create migrations for this app.