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 a new 'path' type, for filesystem paths. #981

Closed
wants to merge 4 commits into from

Conversation

rbarrois
Copy link

@rbarrois rbarrois commented Jun 5, 2013

Allows to properly handle ~user expansion for all paths.

See issue #980.

Review on Reviewable

Allows to properly handle ~user expansion for all paths.
"""optparse.Option subclass handling 'path' type.

See: http://docs.python.org/2/library/optparse#adding-new-types"""
TYPES = optparse.Option + ('path',)
Copy link
Member

Choose a reason for hiding this comment

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

This should probably be optparse.Option.TYPES + ('path',)

Copy link
Author

Choose a reason for hiding this comment

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

Yes, fixed in a later commit.

@msabramo
Copy link
Contributor

I wonder what @pfmoore thinks since he authored
#2455
Which also deals with ~user expansion in find-links.

@pfmoore
Copy link
Member

pfmoore commented Mar 10, 2015

I haven't looked into the option system much, so I can't comment really

@rbarrois
Copy link
Author

Hey, is there still interest in this?

@xavfernandez
Copy link
Member

@rbarrois sure :)

@dstufft dstufft closed this May 18, 2016
@dstufft
Copy link
Member

dstufft commented May 18, 2016

Accidentally closed this, reopening. Sorry!

@dstufft dstufft reopened this May 18, 2016
@BrownTruck
Copy link
Contributor

Hello!

As part of an effort to ease the contribution process and adopt a more standard workflow pip has switched to doing development on the master branch. However, this Pull Request was made against the develop branch so it will need to be resubmitted against master. Unfortunately, this pull request does not cleanly merge against the current master branch.

If you do nothing, this Pull Request will be automatically closed by @BrownTruck since it cannot be merged.

If this pull request is still valid, please rebase it against master (or merge master into it) and resubmit it against the master branch, closing and referencing the original Pull Request.

If you choose to rebase/merge and resubmit this Pull Request, here is an example message that you can copy and paste:

Allows to properly handle ~user expansion for all paths.

See issue #980.

---

*This was migrated from pypa/pip#981 to reparent it to the ``master`` branch. Please see original pull request for any previous discussion.*

@BrownTruck BrownTruck added asked to reparent auto-bitrotten PRs that died because they weren't updated labels May 19, 2016
@BrownTruck
Copy link
Contributor

This Pull Request was closed because it cannot be automatically reparented to the master branch and it appears to have bit rotted.

Please feel free to re-open it or re-submit it if it is still valid and you have rebased it onto master or merged master into it.

@BrownTruck BrownTruck closed this May 26, 2016
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 3, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-bitrotten PRs that died because they weren't updated auto-locked Outdated issues that have been locked by automation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants