conda-forge / mssql-scripter-feedstock

A conda-smithy repository for mssql-scripter.
BSD 3-Clause "New" or "Revised" License
0 stars 5 forks source link

Build package only for Python 3.6 and 3.7 #12

Closed borchero closed 1 year ago

borchero commented 1 year ago

Motivation

Unfortunately, the mssql-scripter is dependent on openssl=1.0 and Python >=3.8 depend on openssl>=1.1.

Checklist

conda-forge-webservices[bot] commented 1 year ago

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 (recipe) and found it was in an excellent condition.

borchero commented 1 year ago

@conda-forge-admin, please rerender

github-actions[bot] commented 1 year ago

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you but ran into some issues. Please check the output logs of the latest rerendering GitHub actions workflow run for errors. You can also ping conda-forge/core for further assistance or try re-rendering locally.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/mssql-scripter-feedstock/actions/runs/4941794642.

maresb commented 1 year ago

That's unfortunate. This looks like a potentially good use case for condax.

borchero commented 1 year ago

@maresb which problem does it solve exactly? :smile: I didn't quite get it while briefly skimming through its docs

borchero commented 1 year ago

In any case, I'll merge this PR once CI passes to restore (or, rather, enable?) the functionality of the package

maresb commented 1 year ago

Suppose you're working on a project where you're using Python 3.11 but you want to be able to call mssql-scripter from the command line. You can't install it into your project environment due to the version conflict. But you could instead run condax install mssql-scripter and condax will set up a separate environment just for mssql-scripter and put the executable in your PATH.

borchero commented 1 year ago

@maresb I see, makes sense ;) I resorted to just create a second conda environment for my use case :smile: