add initial recipe for snowflake-connector-python 1.6.12

[hajapy]

The Snowflake Connector for Python provides an interface for developing Python applications that can connect to Snowflake and perform all standard operations. It provides a programming alternative to developing applications in Java or C/C++ using the Snowflake JDBC or ODBC drivers.

The connector is a native, pure Python package that has no dependencies on JDBC or ODBC.

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

Here's what I've got...

For recipes/snowflake-connector-python:

• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [37, 38]
• noarch packages can't have selectors. If the selectors are necessary, please remove noarch: python.

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

[djsutherland]

You can resolve the merge error by force-pushing away 0a3b44d, now that #7009 is merged.

Also, you should probably add entry points for the entry points in setup.py. And you should remove --no-deps --ignore-installed --no-cache-dir from the pip line; --no-cache-dir is actually a bad idea, and conda-build now sets environment variables to do the others. Other than that, the recipe looks good to me.

[hajapy]

Regarding those extra args, such as --no-deps, it looks like pip is actually installing the dependencies in the build log without that arg, whereas I want/need the packages to be from conda-forge not pypi.

[djsutherland]

I was confused by that too; it doesn't actually install them, but it does cache them kind of wastefully. I'm fine with leaving --no-deps in to avoid that confusion + waste of time downloading, personally.

[hajapy]

Ok, that's very confusing. It also fills the log with so many unnecessary messages making it harder to read the log file.

I still don't know why the build succeeded on travis with --no-deps and failed without it. I'm waiting to see if the latest branch (with --no-deps again) succeeds on travis.

[hajapy]

Ah, so indeed the build passes on travis with --no-deps and fails without it. Any insights as to why that could happen?

[djsutherland]

From the full log, because -vvv makes it waaay too verbose to see anything (we should drop it to -vv or something):

error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool: changing install names or rpaths can't be redone for: /Users/travis/miniconda/conda-bld/snowflake-connector-python_1541683071515/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla/lib/python3.6/site-packages/cryptography/hazmat/bindings/_constant_time.abi3.so (for architecture x86_64) because larger updated load commands do not fit (the program must be relinked, and you may need to use -headerpad or -headerpad_max_install_names)

This makes me think that you do actually need --no-deps. I can't investigate further right now, but leave it in for now.

[hajapy]

Ok thanks, I've done that and incorporated your other suggestions.

[jakirkham]

This makes me think that you do actually need --no-deps.

Confirmed. Raised as issue ( conda/conda-build#3254 ) (though used a different recipe).

[hajapy]

@dougalsutherland Is there anything further needed on this PR then?

[hajapy]

@dougalsutherland is this ready?

[hajapy]

@conda-forge/staged-recipes could someone review/merge this?