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

IronPython fails with obsure error message. #177

Closed
bb-migration opened this Issue Mar 26, 2014 · 5 comments

Comments

Projects
None yet
1 participant
@bb-migration

bb-migration commented Mar 26, 2014

Originally reported by: vernondcole (Bitbucket: vernondcole, GitHub: vernondcole)


I have been under the false impression that setuptools could not be used with IronPython -- which caused me no small problem when trying to configure more complex systems.
Today, I learned that by simply appending a command line switch, IronPython will play happily with the current version.

I suggest trapping the error with a friendly exception message making that fact known to affected users.


@bb-migration

This comment has been minimized.

bb-migration commented Mar 28, 2014

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):


Is there a function in the 'inspect' module that would serve better than the sys._getframe (either providing a better error message or enabling the functionality)?

@bb-migration

This comment has been minimized.

bb-migration commented Mar 30, 2014

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):


Allow install to proceed with an egg install on IronPython and any other environment that has no stack support. Fixes #177.

@bb-migration

This comment has been minimized.

bb-migration commented Mar 30, 2014

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):


I've taken the suggestion to "fail gracefully" a step further and decided instead to allow the install to proceed in environments where a call stack is not available, issuing a warning instead.

I believe this approach is suitable as (a) bdist_* commands are less frequently run and certainly less relied upon for the basic usage (installing setuptools), (b) a warning is issued in the case where this behavior might be problemmatic.

The value in allowing setuptools to install on IronPython outweighs any issue this might raise running bdist_* commands on other non-CPython environments.

@bb-migration

This comment has been minimized.

bb-migration commented Mar 30, 2014

Original comment by dblank (Bitbucket: dblank, GitHub: dblank):


Great job; many thanks!

@bb-migration

This comment has been minimized.

bb-migration commented Mar 30, 2014

Original comment by vernondcole (Bitbucket: vernondcole, GitHub: vernondcole):


I have shared your kind reply with the ironpython mailing list. Let me be
their spokesman in giving a big "Thank You" from all of us.

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