Create an initial catalystcoop.dbfread packaging recipe

[zaneselvans]

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml"
• License file is packaged (see here for an example)
• Source is from official source
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged)
• Build number is 0
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details)
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there

[zaneselvans]

Happy to be listed as maintainer.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/catalystcoop.dbfread) and found some lint.

Here's what I've got...

For recipes/catalystcoop.dbfread:

• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [15]
• There are 1 too many lines. There should be one empty line at the end of the file.
• noarch packages can't have selectors. If the selectors are necessary, please remove noarch: python.

[synapticarbors]

You shouldn't have to delete the files for catalystcoop.pudl since the CI during merge will take care of this.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/catalystcoop.dbfread) and found some lint.

Here's what I've got...

For recipes/catalystcoop.dbfread:

• There are 1 too many lines. There should be one empty line at the end of the file.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/catalystcoop.dbfread) and found it was in an excellent condition.

[zaneselvans]

@conda-forge/help-python The tests are failing on Windows, I believe it's because there's a command line utility called dbf2sqlite which is deployed on installation of the package, and I'm attempting to execute it via the test commands section of the meta.yaml:

test:
  imports:
    - dbfread
  source_files:
    - tests/
    - testcases/
  requires:
    - zipp
    - pytest
  commands:
    - pytest tests
    - dbf2sqlite --help

to ensure that it's runnable, as suggested in the documentation for contributing a package. But this seems to be generating this error:

'dbf2sqlite' is not recognized as an internal or external command,

The script appears to execute just fine on the Linux and OS X platforms. Is there an appropriate way to try and call a deployed python script on Windows? Or if not, to just skip that command on Windows?

[zaneselvans]

@synapticarbors Do you have any pointers on getting the included command line utility to execute in the tests on Windows? I haven't been able to find a similar example in other feedstocks or the documentation. It's installed using the scripts keyword in setup.py not console_scripts / entrypoints. Not sure if that matters.

[synapticarbors]

@zaneselvans -- since this is noarch: python and will only be actually built on linux, it may be ok to ignore this, but I'm not 100% sure. I'm not going to be able to look at this issue for a bit, so I'm going to ping @conda-forge/staged-recipes to see if someone else has a definitive answer concerning a command line utility built from setup.py's scripts option (vs an entry point) failing on windows.

[ocefpaf]

The problem on Windows is the exit code:

IF 9009 NEQ 0 exit /B 1

That is usually fine b/c on Windows sometimes a successful does not really returns 0.