##// END OF EJS Templates
mergestate: don't pop stateextras when there are no conflicts on filemerge...
mergestate: don't pop stateextras when there are no conflicts on filemerge Even if `filemerge.filemerge()` didn't result in conflicts, we should not remove stateextras for a file since we now use that for more things than just merge time information. We use stateextras to store information which is required to be used by commit. I tracked this down while finding why a patch of mine which adds more commit related information does not work as expected and looses the extras in mergestate. Differential Revision: https://phab.mercurial-scm.org/D10148

File last commit:

r43346:2372284d default
r47539:1099ca17 default
Show More
pypi.py
21 lines | 551 B | text/x-python | PythonLexer
# pypi.py - Automation around PyPI
#
# Copyright 2019 Gregory Szorc <gregory.szorc@gmail.com>
#
# This software may be used and distributed according to the terms of the
# GNU General Public License version 2 or any later version.
# no-check-code because Python 3 native.
from twine.commands.upload import upload as twine_upload
from twine.settings import Settings
def upload(paths):
"""Upload files to PyPI.
`paths` is an iterable of `pathlib.Path`.
"""
settings = Settings()
twine_upload(settings, [str(p) for p in paths])