Closed grgmiller closed 3 years ago
Hey @grgmiller I've been looking into how we could get these path related issues working on Windows, and more generally how we could run all of the automated tests on Windows through GitHub Actions, and it's not looking like a particularly straightforward process, given the kinds of packages that PUDL depends on.
Would you be willing to try installing the Windows Subsystem for Linux (WSL2 with Ubuntu version 20.04) and the Windows Terminal (to provide a command line interface to the WSL) and setting up PUDL within that environment? I suspect this will give us the most uniform environment, and make debugging issues easier, since the underlying PyData tools (and our development experience) are fairly centered on a unix-like OS environment, and we would be able to walk you through the setup process there in great detail.
For folks who are just users of PUDL, I think we're moving toward using Docker to standardize the software/OS environment, but I don't think this arrangement is going to work very well if you're also doing a bunch of development, editing the code, etc. Though maybe @rousik who is helping us work out the containerization stuff would know better.
Describe the bug
I am running
ferc1_to_sqlite settings/ferc1_to_sqlite.yml --sandbox
using the development setup (pudl based on current dev branch) and am getting the following error:Bug Severity
How badly is this bug affecting you?
To Reproduce
Steps to reproduce the behavior -- ideally including a code snippet that causes the error to appear. I downloaded the datastore locally using
pudl_datastore --sandbox --verbose --loglevel DEBUG
, and the ferc1 data is stored in a folder called "10.5072-zenodo.656695" Text doc containing yml file info: ferc1_to_sqlite.txtSoftware Environment?
Additional context
Zane's Guess: My guess is that the real problem here is that your machine (Windows) has one way of specifying path separators, but inside the unzipped Zipfile, it's not a Windows filesystem, and it's expecting another type of path separator (forward-slash) or something like that.