Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test Python 3.8/3.11 + backup multiprocessing to get geodata #178

Closed
wants to merge 70 commits into from

Conversation

tfardet
Copy link
Collaborator

@tfardet tfardet commented Nov 19, 2023

Fixes #172 and #175

@hadrilec are these the main changes you had included in #162? If not, feel free to include whatever is missing.

tfardet and others added 30 commits July 18, 2023 13:13
- credentials are stored in the dict
- proxies are also taken from there

Removed all writing to environment except for the token.
Cleaned up bare excepts and imports.
- credentials are stored in the dict
- proxies are also taken from there

Removed all writing to environment except for the token.
Cleaned up bare excepts and imports.
@tfardet tfardet added the bugfix Fixes a bug label Nov 19, 2023
@tfardet
Copy link
Collaborator Author

tfardet commented Nov 19, 2023

@hadrilec Well, it seems we now know where the 4h-long tests come from ^^"

@tfardet
Copy link
Collaborator Author

tfardet commented Nov 20, 2023

@hadrilec I won't have time to look at this for the moment, so if you can have a look, it would be worth checking what makes the multiprocessing fail.
I also wonder whether this is the best way to handle this and if we shouldn't rather move to something like this, might be just as fast (faster?) and more reliable.

@hadrilec
Copy link
Contributor

Thanks for the link, I will have a look. I agree async should be the way to go.

@hadrilec
Copy link
Contributor

I did a mistake by pushing commits from the other PR, my bad, I will clean this up

@tfardet
Copy link
Collaborator Author

tfardet commented Dec 19, 2023

@hadrilec do you know when you'd have time to finish this part?

@hadrilec
Copy link
Contributor

hi @tfardet, I plan to wrap this up before the 1st of January. In any case, a new release of the package must be created by next year because IGN and INSEE/SIREN APIs are changing.

@tfardet
Copy link
Collaborator Author

tfardet commented Dec 19, 2023

Great, let me know if you want me to force push or create another branch with my local version of fix-tests in case cleaning up turns up to be complicated

EDIT: actually, just in case, https://github.com/tfardet/pynsee/tree/fix-test-backup

@hadrilec
Copy link
Contributor

nice, I will start from there

@tfardet tfardet closed this Dec 27, 2023
@tfardet tfardet deleted the fix-tests branch August 8, 2024 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix Fixes a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Test against relevant python versions
3 participants