fails to install xonsh: "setup.py --name" includes logo about pipsi

[RonnyPfannschmidt]

this is a bug i also just recently noticed, pipsi currently expects to install pypi packages, with optional version specs

the solution is of course not to do requirement parsing in the case an actual path is involved
however this brings us to a very dire problem

if a path is used, pipsi has no idea what package i did just install

this is a fundamental shortcoming i hope we can tackle after #52 is solved

[RonnyPfannschmidt]

on further investigation it seems i might be misstaken

[RonnyPfannschmidt]

xonsh printing the logo completely breaks expected tooling behaviour

[untitaker]

We had a similar issue in khal because its setup.py created (used to create) a version.py and printed debugging information.

[scopatz]

@untitaker, I agree. I don't think that this is xonsh-specific issue. I could not find anything in the Python setup.py docs that disallows the setup script from taking other actions (such as printing) other than calling the setup() function. Forcing all packages into this mode is probably not a sustainable system, given how many packages there are.

Other tools like conda build and pip itself handle setup.py files that print extra information without error.

I am happy to help implement another hook in xonsh to find the package name, if you let me know what to do. I want my tool to work with your tool. Maybe a pipsi config file would be beneficial?

[RonnyPfannschmidt]

pip forces setuptools onto all packages and extracts the first egg_info it finds,
such hack is a rather complex pain,
it tends to be way more sustainable to just report issues to packages that play the fancy card because they can,
because one of the reasons why packaging is such a mess is because packages to whatever they want if they can

[untitaker]

I don't think this is an issue that can be fixed in pipsi. Packages that break like this have to be fixed.

[RonnyPfannschmidt]

actually i fixed 1-2 weeks ago (xonsh)