weecology
Automatically copy the config file from deepforest_config.yml to deepforest/data
When you push to pypi, we package the config file for users. Right now we are copying that over before pushing a new release. This is an accident waiting to happen. I added a test to make sure that it matches.
https://github.com/weecology/DeepForest/pull/530
But we still want to cp this during pypi push.
Just to make sure I understand this issue. We want to include /deepforest_config.yaml in the package. Right now we are doing that by manually syncing /deepforest_config.yaml with /deepforest/data/deepforest_config.yaml and packaging the alter file using include_package_data=True and listing the file in MANIFEST.in. Is that right?
Yes, that is correct.
On Sun, Aug 11, 2024 at 9:01 AM Ethan White @.***> wrote:
Just to make sure I understand this issue. We want to include /deepforest_config.yaml in the package. Right now we are doing that by manually syncing /deepforest_config.yaml with /deepforest/data/deepforest_config.yaml and packaging the alter file using include_package_data=True and listing the file in MANIFEST.in. Is that right?
— Reply to this email directly, view it on GitHub https://github.com/weecology/DeepForest/issues/531#issuecomment-2282805407, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJHBLDORSELM5OSAFCPC4LZQ6DGVAVCNFSM6AAAAABMK3TCMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBSHAYDKNBQG4 . You are receiving this because you authored the thread.Message ID: @.***>
-- Ben Weinstein, Ph.D. Research Scientist University of Florida