Skip to content

Conversation

@nikomatsakis
Copy link
Contributor

@nikomatsakis nikomatsakis commented Feb 15, 2018

This makes it so that, when you ./x.py, you get errors relative to the location of x.py. I would also be fine with moving x.py into src, if that is deemed preferable. (Is this a good idea?) One or the other seems to make sense to me, but I'm curious what others think. =)

r? @alexcrichton
cc @pnkfelix

(I suppose one could also run ../x.py from the src directory, but then that creates src/build directory, which I don't particularly like.)

(Also, this is only minimally tested.)

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 15, 2018
@alexcrichton
Copy link
Member

@bors: r+

I think there's another PR to do this already as well though? It may need rebasing maybe

@bors
Copy link
Collaborator

bors commented Feb 16, 2018

📌 Commit 882ff7d has been approved by alexcrichton

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 16, 2018
GuillaumeGomez added a commit to GuillaumeGomez/rust that referenced this pull request Feb 16, 2018
…o-toml, r=alexcrichton

move Cargo.toml to live alongside x.py

This makes it so that, when you `./x.py`, you get errors relative to the location of `x.py`. I would also be fine with moving `x.py` into `src`, if that is deemed preferable. (Is this a good idea?) One of the other seems to make sense to me, but I'm curious what others think. =)

r? @alexcrichton
cc @pnkfelix

(I suppose one could also run `../x.py` from the `src` directory, but then that creates `src/build` directory, which I don't particularly like.)

(Also, this is only minimally tested.)
@pnkfelix
Copy link
Contributor

For the record, I believe the other PR that @alexcrichton is referring to is PR #47731

@pnkfelix
Copy link
Contributor

(which means ... is this likely to not pass bors unless it incorporates the fixups that have been incrementally added to #47731 ? hmm...)

@pnkfelix
Copy link
Contributor

(also it would be good if this were tagged with "Fix #47355", the same way that #47731 is.)

@Mark-Simulacrum
Copy link
Member

Yes, I'm going to just close this in favor of #47731.

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

Labels

S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants