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

Utilizes proper python types rather than numpy types #100

Merged
merged 1 commit into from
Mar 5, 2023

Conversation

elijahbenizzy
Copy link
Collaborator

Numpy switched over. While pyspark still requires an older version it seems, we can upgrade what we have now.

[Short description explaining the high-level reason for the pull request]

Changes

How I tested this

Notes

Checklist

  • PR has an informative and human-readable title (this will be pulled into the release notes)
  • Changes are limited to a single goal (no scope creep)
  • Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
  • Any change in functionality is tested
  • New functions are documented (with a description, list of inputs, and expected output)
  • Placeholder code is flagged / future TODOs are captured in comments
  • Project documentation has been updated if adding/changing functionality.

Numpy switched over. While pyspark still requires an older version it
seems, we can upgrade what we have now.
@elijahbenizzy elijahbenizzy marked this pull request as ready for review March 5, 2023 19:42
@elijahbenizzy elijahbenizzy requested a review from skrawcz March 5, 2023 19:42
@elijahbenizzy elijahbenizzy merged commit 4e8bca2 into main Mar 5, 2023
@elijahbenizzy elijahbenizzy deleted the fix-examples branch March 5, 2023 19:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants