Auto-Close Brackets not Working in Jupyterlab shared remote server - python

Settings --> 'Auto Close Brackets' is checked, however when I type '(', '[', etc., brackets do not auto-close.
jupyterlab version == 3.4.4 (installed via anaconda)
Server o/s: RHEL 7.9 (Maipo)
Is anyone else experiencing this? It was allegedly fixed back in version 3.1.* via https://github.com/jupyterlab/jupyterlab/pull/12508, but of course I still have the issue.

Related

How can I set PyPI index URL in PyCharm Community 2022.3? The "Manage Repositories" button was removed in this version

I've just upgrade my PyCharm Community from 2020.3 to 2022.3. I used to set a private PyPI index-url in PyCharm via File --> Setting --> Porject: xxx --> Python Interpreter --> "plus" sign --> Manage Repositories. But the button was removed from PyCharm Community 2022.3.
Old version of PyCharm with "Manage Repositories" button:
New 2022.3 version of PyCharm Community without "Manage Repositories" button:
I googled the case but can't get an answer, it seems that most of the articles assume that the "Manage Repositories" button still exists. I searched "manage", "repositor" in PyCharm Settings searching box, but no such configuration was found. I thought "Settings Repository" plug-in is what I want, but it seems that this plug-in is about sharing IDE settings rather than PyPI index-url.
I'm using PyCharm on Windows platform, the detail version information is:
PyCharm 2022.3 (Community Edition)
Build #PC-223.7571.203, built on November 30, 2022
Runtime version: 17.0.5+1-b653.14 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 10 10.0
GC: G1 Young Generation, G1 Old Generation
It has moved to View -> Tool Windows -> Python Packages

Upgrade with Python3.7.4 version in miniconda docker image

There is some security regression was discovered in python 3.7.3, which still allows an attacker to exploit.
An issue was discovered in urllib2 in Python. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the query string after a ? character) followed by an HTTP header or a Redis command.
Below are the refrences for the issue:
[https://bugs.python.org/issue30458][1]
[https://bugs.python.org/issue33529][1]
[https://bugs.python.org/issue35755][1]
https://bugs.python.org/issue35907
https://bugs.python.org/issue36742
https://bugs.python.org/issue37463
The solution is to use Python 3.7.4 , which is released 9th of july 2019. But conda distribution is not released yet for python 3.7.4.
Now the question is:- Is there any way to upgrade python with python-3.7.4 in miniconda docker image container?
Docker file is : -
FROM continuumio/miniconda3:4.6.14
I tried to put upgrade python command in docker file but it fails as Python 3.7.4 is not available in conda distribution
repo.anaconda.com/pkgs/main/linux-64

ipython (version 3.2.1) support in LightTable (version 0.7.2)

I've just started using Light Table and can't get iPython working under OSX 10.10. Relevant version numbers are iPython 3.2.1, Python 3.4.3 or 2.7.10, and LightTable version 0.7.2 (installed via a Homebrew Cask and .zip file).
Evaluating Python code works as I'd expect and I get nice tab-completion, but I can't get any graphical output. The "Connection Bar" shows a python connection rather than ipython even though ipython is available on the command line and I can successfully run ipython notebook and have it pop up a web-browser (this requires a working copy of pyzmq).
Neither Python 2.7 nor 3.4 work, and I've tried the official LT .zip as well as installing as brew cask install lighttable.
Changing my User.behaviours to explicitly reference the "correct" virtualenv:
[:app :lt.plugins.python/python-exe "/Users/smason/.virtualenvs/py3/bin/python"]
[:app :lt.plugins.python/ipython-exe "/Users/smason/.virtualenvs/py3/bin/ipython"]
doesn't seem to affect things (verified by getting appropriate errors when misspelling binary, and by running print(sys.version) and looking at output in console).
The problem was that iPython support with Light Table is pretty out of date. It is using features that were exposed in pre-1.0 versions of iPython and it's not been updated while iPython's API has changed.
The most minimal change to Light Table that fixed this for me is in:
https://github.com/LightTable/Python/pull/31
If you're patching your own install you would want to modify:
LightTable.app/Contents/Resources/app.nw/plugins/python/py-src/ltipy.py
but with iPython 4 being released yesterday more code needs to change—hopefully (if you're reading this) I'll get around to making this larger change.

google app engine not running after upgrading to yosemite

I recently upgraded my macbook to yosemite, and am having trouble starting the google app engine. When I try to run any app, I get a yellow clock, and all options are greyed out.
When I look in GAE prefs, the default python path is
/usr/local/bin/python2.7
but yosemite does not use that location
$ which python
/Library/Frameworks/Python.framework/Versions/2.7/bin/python
I have tried entering that value in the GAE prefs, but I still get the same issue. I also tried installing the newest ver of python, but it installed in the same loc, with no option to install in /usr/local/bin
Do I need to do something in terms of the symlinks? Has anyone else run across this issue?
thanks,
bp

NumPy on Python 3.3 on Windows 8

I am trying to get NumPy to work on my new Windows 8 installation, with Python 3.3 installed. When I try (both) installers from here, they crash when I click 'Install'.
Has anyone had success with the same setup?
EDIT: Error image:
It seems, from the capture, that your trying to instal version:
numpy-unoptimized-1.6.2.win32-py3.3.‌exe
However, I just checked the site this morning, and the latest available version is:
numpy-unoptimized-1.6.2.win32-py3.2.‌exe
Have you tried the installer again lately (using the latest build)?

Categories