-
Notifications
You must be signed in to change notification settings - Fork 1
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
Request for Permission to Publish ALT-DSS Schema on PyPI #10
Comments
Hi, Aadil (and @KapilDuwadi),
Thanks for asking! If you're close to a deadline, go ahead and publish a release on PyPI. If you don't mind adding me as a maintainer, we can cooperate on future releases and try to ensure compatibility. There are upcoming changes that will affect the schema soon:
I don't know if these changes are enough for us to worry about supporting multiple schema versions ("2023-12-13", 2025-01-xx", 2025-02-xx", etc.) in the same package yet, but it's something to think about. I already ported most of the code related to the changes, and I plan to resume working on testing the upcoming release of the engine and most packages this Monday. Only a few remaining issues to handle. |
Hi Pedro, Thank you for the response. I will add you as a maintainer. "If you still have some time, I could finally review the changes you guys proposed -- either a PR or a link to the specific branch should work, but of course feel free to drop me an email too." That would be awesome. I will work on setting up a repository over the next week. My colleague Tarek ([email protected]) worked on the changes. He is currently out of office. I will ask him to connect with you once he is back. |
Hi Paulo,
At NREL, we are currently working on model conversion and have been utilizing the Pydantic models from your repository (NREL-Distribution-Suites/alt-dss-schema). We are now at the stage where we need to package these changes and publish the package on PyPI to add it as a dependency in other projects we are developing.
Until now, we’ve been using the repository internally, but external users are beginning to require access to the package. With your permission, we’d like to proceed with publishing the package and will ensure proper attribution to your work in the repository.
Best regards,
Aadil
@KapilDuwadi
The text was updated successfully, but these errors were encountered: