You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wish I could just use link to #341 as #341 in MyST-Parser. To stay in scope I removed autodoc roles. Here is what it looks like when copy pasting (a lot of work to dredge out the issues):
libvcs 0.13.0 (unreleased)
Breaking changes
{issue}343: libvcs.cmd.core (including ~libvcs._internal.run.run) have been moved to libvcs._internal.run. It will be supported as an unstable, internal API.
{issue}361: ~libvcs._internal.run.run's params are now a pass-through to subprocess.Popen.
run(cmd, ...) is now run(args, ...) to match Popen's convention.
Command: Now support -C (which accepts .git dirs, see git's manual) in addition to cwd
(subprocess-passthrough), {issue}360
Bug fixes
Fix argument input for git commands, e.g. git config --get color.diff would not properly
pass-through to subprocess. {issue}360
Internals
{issue}345libvcs.utils -> libvcs._internal to make it more obvious the APIs are strictly
closed.
StrOrPath -> StrPath
{issue}336: ~libvcs._internal.subprocess.SubprocessCommand: Encapsulated subprocess call in a dataclasses.dataclass for introspecting, modifying, mocking
and controlling execution.
The text was updated successfully, but these errors were encountered:
tony
changed the title
(StackOverflow) Pasting MyST-Parser roles into an issue
(For StackOverflow) Pasting MyST-Parser roles into an issue
May 29, 2022
re: https://stackoverflow.com/questions/72424748/myst-parser-auto-linking-linkifying-references-to-bug-tracker-issues
I wish I could just use link to #341 as
#341
in MyST-Parser. To stay in scope I removed autodoc roles. Here is what it looks like when copy pasting (a lot of work to dredge out the issues):libvcs 0.13.0 (unreleased)
Breaking changes
{issue}
343
:libvcs.cmd.core
(including~libvcs._internal.run.run
) have been moved tolibvcs._internal.run
. It will be supported as an unstable, internal API.{issue}
361
:~libvcs._internal.run.run
's params are now a pass-through tosubprocess.Popen
.run(cmd, ...)
is nowrun(args, ...)
to matchPopen
's convention.What's new
Commands: Experimental command wrappers added ({issue}
346
):libvcs.cmd.git.Git
libvcs.cmd.git.Git.help
libvcs.cmd.git.Git.reset
libvcs.cmd.git.Git.checkout
libvcs.cmd.git.Git.status
libvcs.cmd.git.Git.config
via {issue}360
Command: Now support
-C
(which accepts.git
dirs, see git's manual) in addition tocwd
(subprocess-passthrough), {issue}
360
Bug fixes
git config --get color.diff
would not properlypass-through to subprocess. {issue}
360
Internals
{issue}
345
libvcs.utils
->libvcs._internal
to make it more obvious the APIs are strictlyclosed.
StrOrPath
->StrPath
{issue}
336
:~libvcs._internal.subprocess.SubprocessCommand
: Encapsulatedsubprocess
call in adataclasses.dataclass
for introspecting, modifying, mockingand controlling execution.
Dataclass helper:
~libvcs._internal.dataclasses.SkipDefaultFieldsReprMixin
Skip default fields in object representations.
Credit: Pietro Oldrati, 2022-05-08,
StackOverflow Post
Documentation
libvcs.types
The text was updated successfully, but these errors were encountered: