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

Naming conflict with "sync" module #50

Open
Jbalkind opened this issue Jul 26, 2019 · 1 comment
Open

Naming conflict with "sync" module #50

Jbalkind opened this issue Jul 26, 2019 · 1 comment
Assignees
Milestone

Comments

@Jbalkind
Copy link

We're making use of sync_wedge and thus sync in our design (specifically, it's used in the CLINT from Ariane). The naming used to be nicely prefixed (pulp_) to not have any conflicts, but the name sync is generic enough that we're getting naming conflicts when working with Amazon's F1 infrastructure.

We tried using pulp_sync instead but the interface changed so we had to tinker some and it means we need to keep a fork for little good reason.

Is there any chance you could rename this upstream or adopt a SV package to avoid such conflicts?

@zarubaf
Copy link
Contributor

zarubaf commented Jul 26, 2019

Yeah, that was very unwise naming. We are planning a major bump (which allows us to break API). Is it okay to put this issue down as one of the todos?

@zarubaf zarubaf added this to the v2.0 milestone Jul 26, 2019
@zarubaf zarubaf self-assigned this Jul 26, 2019
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

No branches or pull requests

2 participants