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.

Sign up for GitHub

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

Jump to bottom

[Housekeeping] Improve the way requirements are regenerated #3284

Closed
2 tasks done
cosmicBboy opened this issue Jan 25, 2023 · 1 comment
Closed
2 tasks done

[Housekeeping] Improve the way requirements are regenerated #3284

cosmicBboy opened this issue Jan 25, 2023 · 1 comment
Assignees
@eapolinario
Labels
housekeeping Issues that help maintain flyte and keep it tech-debt free
Milestone
1.4.0

Comments

@cosmicBboy
Copy link
Contributor

Describe the issue

TODO

regenerating requirements:

  • 1 requirements files per python version?
  • tox?
  • dockerize?
  • how to manage plugins requirements?

What if we do not do this?

TODO

Related component(s)

flytekit

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes
@cosmicBboy cosmicBboy added the housekeeping Issues that help maintain flyte and keep it tech-debt free label Jan 25, 2023
@cosmicBboy cosmicBboy added this to the 1.4.0 milestone Jan 29, 2023
@eapolinario eapolinario mentioned this issue Feb 17, 2023
Merged
8 tasks
@eapolinario
Copy link
Contributor

eapolinario commented Feb 27, 2023 •
edited
Loading

We might need to revisit this in the future, but the current solution of not forcing multiple requirements files covers all cases we care about.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eapolinario eapolinario

Labels
housekeeping Issues that help maintain flyte and keep it tech-debt free
Projects
None yet
Milestone
1.4.0
Development

No branches or pull requests
2 participants
@eapolinario @cosmicBboy