Release v3.0.1

[evhub]

See Coconut's documentation for more information on all of the features listed below.

This is a patch release primarily aimed at fixing #746, though it also brings a couple of new features and other fixes as well.

New features:

• Add syntax for passing a variable as a keyword argument of the same name #743: New f(...=long_name) syntax as a shorthand for f(long_name=long_name).
• Function composition should preserve the signature of the first function when possible #744: f ..> g will now preserve the signature of f when inspected using inspect.signature.

Language changes:

• fmap should raise an error rather than falling back to a default implementation for unknown objects #736: fmap will now raise TypeError rather than falling back to a default implementation when it encounters an unknown type. For backwards compatibility, the old behavior can be recovered with fmap$(fallback_to_init=True).
• Fix fmap for multiset #737: fmap now works properly on multiset.

Bugfixes:

• Syntax errors in the Jupyter kernel produce KeyError: 'point' #746: Syntax errors produced when using Coconut's Jupyter kernel will now present themselves nicely rather than causing an error.
• [xonsh] Coconut xontrib causes crash when using semi-separated commands #745 (thanks @Starwort!): xonsh will no longer fail on semicolon-seperated commands when using the Coconut extension.
• Standalone mode disables multiple jobs on compiling directory #739 (thanks @yggdr!): Compiling a single directory in --stand-alone mode will now properly make use of --jobs.
• 3.0.0: pep517 build warnings #742 (thanks @kloczek!): Fixed a deprecation warning when installing Coconut.

[Starwort]

I hate to say it, but I think this caused a regression on #724 - after updating, my xonshrc is not loading in any reasonable time-frame (I killed it after 6m16s)

[evhub]

@Starwort Yeah, I know—I have another release (#758) that should be out today that should fix it for real this time. I've been working on improving xonsh testing a bunch also so this doesn't keep happening. In the meantime, it's working on coconut-develop right now (pip uninstall coconut && pip install -U coconut-develop).