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

should pephubclient become part of peppy to simplify things? #462

Open
Tracked by #457
donaldcampbelljr opened this issue Dec 5, 2023 · 2 comments
Open
Tracked by #457

should pephubclient become part of peppy to simplify things? #462

donaldcampbelljr opened this issue Dec 5, 2023 · 2 comments
Labels
enhancement - users refactor
Milestone
v0.50.0

Comments

@donaldcampbelljr
Copy link
Contributor

No description provided.

@donaldcampbelljr donaldcampbelljr mentioned this issue Dec 5, 2023
Closed
6 tasks
@khoroshevskyi
Copy link
Member

In my opinion, pephubclient shouldn't be part of peppy.

  1. It will be harder to maintain these two things.
  2. I want to avoid recursive dependency.

@nsheff
Copy link
Contributor

nsheff commented Dec 5, 2023

after some discussion in infrastructure, we think it might make sense to:

  • bring pephubclient into peppy as a submodule
  • bring eido back into peppy as a submodule
  • leave pepdbagent outside of peppy

@donaldcampbelljr donaldcampbelljr mentioned this issue Dec 12, 2023
Open
@nsheff nsheff added this to PEP Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement - users refactor
Projects
None yet
Milestone
v0.50.0
Development

No branches or pull requests
3 participants
@nsheff @khoroshevskyi @donaldcampbelljr