Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Using an out of place build directory with src paths like "../../../src/foo.pyx" doesn't work #2764
As per this Stackoverflow question, say you have a
When you try to build the Cython extension with, say, the following call:
and the path to
At this point, insanity breaks loose. Best case scenario,
added a commit
Dec 17, 2018
IMHO, insanity already starts when people use paths like
I agree that the PR improves the specifically described situation. It does not solve the general problem that people come up with weird build setups and expect the tools to magically make them work.
As they say, there's no accounting for taste. And I completely agree that the most general case is hopeless. Which is exactly why "weird build" functionality should be added in on the basis of reasonable(-ish) use cases. This is also why you should completely ignore the perverse ones (I thought of the
An "up-and-to-the-left-of-the-source" build is obviously not ideal, but I've run into similar situations myself. They usually involve in-house code that's needed as a dependency by 3 or 4 other in-house projects. I suppose the "correct" way to deal with those situations is something like Git submodule, but honestly that's not really that great a solution either. So I sympathize with the guy who asked about this on SO.