Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add IPython-SQL to conda-forge #1192

Merged
merged 3 commits into from Aug 24, 2016
Merged

Add IPython-SQL to conda-forge #1192

merged 3 commits into from Aug 24, 2016

Conversation

sodre
Copy link
Member

@sodre sodre commented Aug 6, 2016

Please add iPython-SQL to conda-forge.

@conda-forge-linter
Copy link

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/ipython-sql) and found some lint.

Here's what I've got...

For recipes/ipython-sql:

  • Failed to even lint the recipe (might be a conda-smithy bug) 😢

@@ -0,0 +1,46 @@
{$ set version = "0.3.6" %}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be {% set version = "0.3.6" %}.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small punctuation is our downfall again. 😆

@jakirkham
Copy link
Member

Looks pretty good @sodre. Few things to fix up, but they are all pretty easy. Thanks for the proposed addition.

@conda-forge-linter
Copy link

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

@msarahan
Copy link
Member

msarahan commented Aug 6, 2016

Circle failure appears related to trying to compile pexpect python3 file. I think/hope newer versions of conda-build will fix this. Not sure if you want to try with 1.21.11 from source, package seems to not be available yet.

@jakirkham
Copy link
Member

Didn't pip also work in this case?

@sodre
Copy link
Member Author

sodre commented Aug 6, 2016

let me know what/if you need me to change.

md5: {{ md5 }}

build:
number: 0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, if you want to just do Python 3.x, please add skip: true # [py2k]. If we need Python 3.5 only, we may need to change py2k to py35. Once this is done, please drop the changes to .CI/build_all from the PR.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Guessing this is not needed now, but have forgotten. Maybe a reminder would be nice please. 😁

@conda-forge-linter
Copy link

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/ipython-sql) and found some lint.

Here's what I've got...

For recipes/ipython-sql:

  • Failed to even lint the recipe (might be a conda-smithy bug) 😢

script: python setup.py install --single-version-externally-managed --record record.txt

skip:
true # [py2k]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So this should be in the build section, it should be one line, and the selector should have at least 2 spaces before it.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jakirkham,
Thanks so much for helping me out on this. is there an easy way to run the lint checker on my side before committing?

@sodre sodre force-pushed the master branch 2 times, most recently from 76043b7 to 7cb8d10 Compare August 6, 2016 22:42
@conda-forge-linter
Copy link

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/ipython-sql) and found some lint.

Here's what I've got...

For recipes/ipython-sql:

  • Selectors are suggested to take a <two spaces>#<one space>[<expression>] form.

@conda-forge-linter
Copy link

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

build:
number: 0
script: python setup.py install --single-version-externally-managed --record record.txt
skip: true # [py2k]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should be able to drop this skip line as conda-build version 1.21.11 is out and shouldn't run into the same issues.

@jakirkham
Copy link
Member

Hmm...seems we are still running into this issue on CircleCI still, but not the other CIs. Will try rebuilding the Docker image.

As for the other CIs, seems we may be running into some other sort of issue ( spyder-ide/spyder#3309 ). @ccordoba12, do you know anything about what is causing the AttributeError: module 'pkg_resources' has no attribute 'iter_entry_points'. It seems to only occur on Python 3.5. 😕

@jakirkham
Copy link
Member

Interestingly I don't run into this issue with setuptools alone or with pygments for that matter. There is something more going on that seems to be missing.

@jakirkham
Copy link
Member

Rebuilt the Docker container and now restarting CircleCI.

@jakirkham
Copy link
Member

@conda-forge/pygments, any ideas on this last error?

@jakirkham
Copy link
Member

As for the first error, could you please try updating master for the conda-forge remote and merging with it, @sodre? I expect this should fix it.

@ccordoba12
Copy link
Contributor

@jakirkham, @Carreau said in spyder-ide/spyder#3309 that this problem was a bug in IPython 5.0, and that it'll be fixed in 5.1.

@jakirkham
Copy link
Member

Ah, ok, sorry for being dense. Thanks for clarifying, @ccordoba12.

@Carreau
Copy link

Carreau commented Aug 8, 2016

Yes, Sorry I'm trying to push 5.1 / 5.0.1 through the door. I'm doing the best I can. Sorry about that.

@jakirkham
Copy link
Member

No worries. Just trying to narrow down the cause.

@jakirkham
Copy link
Member

If it would help alleviate some pressure, @Carreau, we could try applying a patch that fixes the issue to our ipython package. That is assuming the fix is known and available. Just let us know. 😄

@Carreau
Copy link

Carreau commented Aug 9, 2016

Ok, I had a deeper look and now I'm confused. Looking at the travis error, I have no clue why.

The issue @ccordoba12 linked to have 2 issues. One with AttributeError: module 'pkg_resources' has no attribute 'iter_entry_points' which is usually resolved by upgrading setuptools. The other ImportError: cannot import name 'NoOpContext' which was fixed there: ipython/ipython#9765

@jakirkham
Copy link
Member

Was referring to the latter issue. Though we are using the latest setuptools. Maybe switching to pip fixes this.

@conda-forge-linter
Copy link

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/ipython-sql, recipes/xray-vision) and found it was in an excellent condition.

@Carreau
Copy link

Carreau commented Aug 11, 2016

Btw, I think it is failing because IPython has been spelled with a lower case i in a few places, while it is IPython

@Carreau
Copy link

Carreau commented Aug 11, 2016

Dang, the joking tags are removed by GitHUb.

@sodre sodre changed the title Add iPython-SQL to conda-forge Add IPython-SQL to conda-forge Aug 11, 2016
@jakirkham
Copy link
Member

Must be GitHub's way of saying no more joking around. 😜

@sodre
Copy link
Member Author

sodre commented Aug 13, 2016

alright, it looks like the only issue left is with pygments for python 3.5, IPython 5 and win[64,32].
I will try with IPython 4 and see if it works for that platform.

@conda-forge-linter
Copy link

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

 - Win and Py35 require IPython<5
@sodre
Copy link
Member Author

sodre commented Aug 13, 2016

@jakirkham, It looks like the package is now ready to go.
What is the next step from my side?

- sql

about:
home: pypi.python.org/pypi/ipython-sql
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


about:
home: https://pypi.python.org/pypi/ipython-sql
license: MIT
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ideally we would include the license file. However, they don't provide one. 😞

Have raised issue ( catherinedevlin/ipython-sql#58 ) to track this. Could we please add a comment here to add the license_file once they have provided one?

We need to add the MIT license file when catherinedevlin/ipython-sql#58 closes.
@jakirkham jakirkham merged commit d7822d1 into conda-forge:master Aug 24, 2016
@jakirkham
Copy link
Member

Thanks everyone for your help getting this one worked out. Thanks @sodre for contributing it.

@jakirkham
Copy link
Member

Soon you should get an email that invites you to join conda-forge, @sodre. Once accepted you will be added to a team with the same name as this recipe. Those will give you permissions on the feedstock (repo) for this recipe.

Make sure when proposing any change that you go through the typical GitHub workflow of forking the feedstock and making changes in your fork that you PR back. Once merged CIs will build and deploy any changes you make. Please let us know if you have any questions and welcome to conda-forge.

@sodre
Copy link
Member Author

sodre commented Aug 24, 2016

Thanks! I will keep an eye out for the License fix.

Best,
Patrick

On Aug 23, 2016, at 11:20 PM, jakirkham notifications@github.com wrote:

Soon you should get an email that invites you to join conda-forge, @sodre https://github.com/sodre. Once accepted you will be added to a team with the same name as this recipe. Those will give you permissions on the feedstock (repo) for this recipe.

Make sure when proposing any change that you go through the typical GitHub workflow of forking the feedstock and making changes in your fork that you PR back. Once merged CIs will build and deploy any changes you make. Please let us know if you have any questions and welcome to conda-forge.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #1192 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AA_rVbTquKySrA5zY7A31G66ewXaHTvZks5qi7iLgaJpZM4JeWBH.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants