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

Restructure project to use relative imports, and have everything live in sub-packages #331

Closed
ducky64 opened this issue Apr 2, 2024 · 1 comment
Closed

Restructure project to use relative imports, and have everything live in sub-packages #331

ducky64 opened this issue Apr 2, 2024 · 1 comment

Comments

@ducky64
Copy link
Collaborator

ducky64 commented Apr 2, 2024 •
edited
Loading

... to allow this to be submoduled.

Likely involves moving everything from the root directory into the edg directory / package.

This will be destructive to any outstanding PRs, but should maintain API stability as far as import edg is concerned. Anything below that (like import edg_core) would be relying on internal / implementation behavior.
@ducky64
Copy link
Collaborator Author

ducky64 commented Jul 15, 2024

Resolved by #352

@ducky64 ducky64 closed this as completed Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ducky64