Add virtual_dataframe package, version v0.1rc1

[pprados]

Checklist

• [x] Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• [x] License file is packaged (see here for an example).
• [x] Source is from official source.
• [x] 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).
• [x] If static libraries are linked in, the license of the static library is packaged.
• [x] Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• [x] Build number is 0.
• [x] A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• [x] GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• [x] When in trouble, please check our knowledge base documentation before pinging a team.

[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/virtual_dataframe) and found some lint.

Here's what I've got...

For recipes/virtual_dataframe:

• The top level meta key conda_build is unexpected
• The recipe must have some tests.
• license_file entry is missing, but is required.
• Recipe maintainer "[email protected]" does not exist
• The extra section contained an unexpected subsection name. copy_test_spirce_files is not a valid subsection name.
• The extra section contained an unexpected subsection name. copy_test_source_files is not a valid subsection name.
• requirements: run: python>=3.9 must contain a space between the name and the pin, i.e. python >=3.9
• requirements: run: pandas>=1.4 must contain a space between the name and the pin, i.e. pandas >=1.4
• noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

For recipes/virtual_dataframe:

• Jinja2 variable references are suggested to take a {{<one space><variable name><one space>}} form. See lines [22].
• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

[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/virtual_dataframe) and found some lint.

Here's what I've got...

For recipes/virtual_dataframe:

• Failed to even lint the recipe, probably because of a conda-smithy bug :cry:. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

[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/virtual_dataframe) and found some lint.

Here's what I've got...

For recipes/virtual_dataframe:

• Recipe maintainer "Philippe Prados" does not exist

[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/virtual_dataframe) and found it was in an excellent condition.

[pprados]

@conda-forge-daemon I receive an error in staged-recipes : No module named pip. I have

requirements:
  build:
    - python {{ PYTHON_VERSION }}
    - pip
    - setuptools
    - setuptools_scm

How I resolve this bug ?

[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/virtual_dataframe) and found some lint.

Here's what I've got...

For recipes/virtual_dataframe:

• The top level meta key channels is unexpected
• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [37]

[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/virtual_dataframe) and found it was in an excellent condition.

[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/virtual_dataframe) and found some lint.

Here's what I've got...

For recipes/virtual_dataframe:

• noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

[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/virtual_dataframe) and found it was in an excellent condition.

[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/virtual_dataframe) and found some lint.

Here's what I've got...

For recipes/virtual_dataframe:

• The test section contained an unexpected subsection name. script_env is not a valid subsection name.

[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/virtual_dataframe) and found it was in an excellent condition.

[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/virtual_dataframe) and found some lint.

Here's what I've got...

For recipes/virtual_dataframe:

• Failed to even lint the recipe, probably because of a conda-smithy bug :cry:. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

[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/virtual_dataframe) and found it was in an excellent condition.

[conda-forge-linter]

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

I was trying to look for recipes to lint for you, but couldn't find any. Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

[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/virtual_dataframe) and found it was in an excellent condition.

[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/virtual_dataframe) and found some lint.

Here's what I've got...

For recipes/virtual_dataframe:

• The recipe must have some tests.

[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/virtual_dataframe) and found it was in an excellent condition.

[conda-forge-linter]

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

I was trying to look for recipes to lint for you, but couldn't find any. Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

[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/virtual_dataframe) and found it was in an excellent condition.

[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/virtual_dataframe) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/virtual_dataframe:

• Jinja2 variable references are suggested to take a {{<one space><variable name><one space>}} form. See lines [94].

[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/virtual_dataframe) and found it was in an excellent condition.