-
Notifications
You must be signed in to change notification settings - Fork 143
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
Rename Pipfile to Pipfile.toml #52
Comments
we had a long discussion about filenames already, and determined these filenames are best. |
@kennethreitz In that case suggesting this be opened here wasn't a good use of anyone's time. |
Well, other people may want to comment. |
Wish I had taken part in this discussion when it was going on. Would have really pushed for the very simple :( |
The |
Fine I'll bite:
Now we need to tell vim that Where did you guys disqus this BTW? I'll join for future reference. |
I wish I had taken part in this too; I personally really dislike these redundant idioms that thrive among software I see and use every day. It's rather redundant to suffix your files with "file" to be honest; but that I can totally live with It's not even Pythonic requiring a capital letter. :( |
@dstufft It's obviously not about software cope, but human cope. |
@kennethreitz Would you consider your stance on this based on the comments in the issue? |
I too find it very unfortunate that |
this is more relevant now that |
vim users: If you use vim-plug: Plug 'cespare/vim-toml' " Support for highlighting toml filetype
if executable('pipenv')
au BufNewFile,BufRead Pipfile setf toml
endif If you already have au BufNewFile,BufRead Pipfile setf toml You can also add support for au BufNewFile,BufRead Pipfile.lock setf json |
There is no benefit in not including the extension (a sense of mystery?).
In fact you will only have things to gain (editor highlighting, etc).
ref: Initially opened here.
The text was updated successfully, but these errors were encountered: