These are chat archives for spyder-ide/public
ipykernel: 4.7.0-py36h2f9c1c0_0 --> 4.8.2-py36_0 ipython: 6.2.1-py36h9cf0123_1 --> 6.5.0-py36_0 jupyter_client: 5.2.1-py36_0 --> 5.2.3-py36_0 libpng: 1.6.32-h140d38e_4 --> 1.6.34-h79bbb47_0 pyqt: 5.6.0-py36hb5ed885_5 --> 5.9.2-py36ha878b3d_0 pyzmq: 16.0.3-py36he714bf5_0 --> 17.1.2-py36hfa6e2cd_0 qt: 5.6.2-vc14h6f8c307_12 --> 5.9.6-vc14h62aca36_0 qtconsole: 4.3.1-py36h99a29a9_0 --> 4.4.0-py36_0 sip: 4.18.1-py36h9c25514_2 --> 4.19.8-py36h6538335_0 spyder-kernels: 0.2.4-py36_0 --> 0.2.6-py36_0 sqlite: 3.20.1-h9eeafa9_2 --> 3.24.0-h7602738_0 tornado: 4.5.3-py36_0 --> 5.1-py36hfa6e2cd_0
jupyter_client; quite possibly it was some mutual corner-case between specific versions so it wasn't bad that you updated them all at once.
pyments. You could manually add the
pytextension as Python a number of different places in the code, or just do a hack to make it pretend to be
.pywhen feeding it through to Pygments, although its a pretty narrow use case (a vanity extension for an otherwise generic Python module for a specific closed, proprietary program with plenty of good open-source alternatives). Others might have better ideas; longer term it would be nice to have better support for configuring syntax highlighting language manually, or easily adding custom extensions.
spyder/widgets/sourcecode/codeeditor.pyfor places to fake Pygments into thinking its