Skip to content

Commit ecdf789

Browse files
committed
Update changelog and jupyter page.
1 parent d33593f commit ecdf789

File tree

2 files changed

+6
-3
lines changed

2 files changed

+6
-3
lines changed

web2/cadabra2/source/changelog.html

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,9 @@ <h3>github master (2.3.3)</h3>
2424
to new symbols.</li>
2525
<li>Fix bug pulling with <tt>@(...)</tt> operator.</li>
2626
<li>Add option <tt>redundant</tt> to <tt>eliminate_metric</tt> to
27-
only eliminate metrics which have two dummy indices (David).</li>
27+
only eliminate metrics which have two dummy indices (David).</li>
28+
<li>Added option to export notebooks to Jupyter, and a command-line
29+
utility to do the same.</li>
2830
</ul>
2931

3032
<a name="2.3.2"></a>

web2/cadabra2/source/jupyter.html

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -67,8 +67,9 @@ <h2>Differences with Cadabra's own notebook</h2>
6767
that Jupyter notebooks (with extension <tt>.ipynb</tt>) and Cadabra
6868
notebooks (with extension <tt>.cnb</tt>) are not the same file
6969
format. You can read notebooks created in Jupyter into the Cadabra
70-
<tt>cadabra2-gtk</tt> client, but you cannot read Cadabra notebooks
71-
into Jupyter (at least not until a converter is written).
70+
<tt>cadabra2-gtk</tt> client, and you can (as of version 2.3.3)
71+
export Cadabra notebooks as Jupyter notebooks, but it is good to
72+
keep this in mind.
7273
</p>
7374
<p class="hyphenate">
7475
You <em>can</em>, however, make use of Cadabra packages inside the

0 commit comments

Comments
 (0)