I also re-worded the README a bit.

@alalek Integers are supported -- as long as they are Python ints. It is NumPy data types that used to work and support for them has ceased.

Issue Type: <b>Bug</b>

When displaying an HTML link in IPython, the interactive window produces a link pointing to https://<uuid>.vscode-webview-test.com/vscode-resource/file///<path-to-project>/<url>. The expected behavior is to point to <url>.

Code sample:

# %%
from IPython.core.display import display, HTML

# %%
url = 'http://httpbin.org/ip'
text = 'Show my IP'
display(HTML(f'<a href="{url}">{text}</a>'))

Extension version: 2021.5.842923320 VS Code version: Code 1.56.2 (054a9295330880ed74ceaedda236253b4f39a335, 2021-05-12T17:13:13.157Z) OS version: Windows_NT x64 10.0.19042

Screen capture:

<!-- generated by issue reporter -->

Without relation to the issue itself, just to correct a mistake - I'll also mention that urllib.parse.quote() usage shown in the screen recording is wrong for this purpose. I removed it from the code example.

A workaround is to link to //<url-without-scheme>, e.g. url = '//httpbin.org/ip' in above code.

Issue Type: <b>Bug</b>

When displaying an HTML link in IPython, the interactive window produces a link pointing to https://<uuid>.vscode-webview-test.com/vscode-resource/file///<path-to-project>/<url>. The expected behavior is to point to <url>.

Code sample:

# %%
from IPython.core.display import display, HTML
import urllib

# %%
url = 'http://httpbin.org/ip'
text = 'Show my IP'
display(HTML(f'<a href="{urllib.parse.quote(url)}">{text}</a>'))

Extension version: 2021.5.842923320 VS Code version: Code 1.56.2 (054a9295330880ed74ceaedda236253b4f39a335, 2021-05-12T17:13:13.157Z) OS version: Windows_NT x64 10.0.19042

Screen capture:

<!-- generated by issue reporter -->

This is a problem with OpenCV 4.5.2. `cv2. Better stick to 4.5.1 for now. Reported here.

<!-- If you have a question rather than reporting a bug please go to https://forum.opencv.org where you get much faster responses. If you need further assistance please read How To Contribute.

This is a template helping you to create an issue which can be processed as quickly as possible. This is the bug reporting section for the OpenCV library. -->

System information (version)

<!-- Example

• OpenCV => 4.2

• Operating System / Platform => Windows 64 Bit

• Compiler => Visual Studio 2017 -->

• OpenCV => 4.5.2

• Operating System / Platform => python:3.8-buster Docker image (under Windows 10) / pip opencv-python-headless

• Compiler => Provided by Docker image, I assume gcc

Detailed description

cv2.pointPolygonTest() gives an error when the tuple contains NumPy int32 or int64 data types starting from version 4.5.2. Version 4.5.1.48 supports NumPy data types, and this is a breaking change.

It is relevant since many calculations for points from back from NumPy and need to be converted to a tuple to be fed into pointPolygonTest(). However, the most straight-forward way to do this (wrap with tuple()) gives tuple elemens which are NumPy data types (np.int32 or np.int64).

I suspect this commit https://github.com/opencv/opencv/commit/a0bdb78a996bb6fa090ab1d42a623f7ea862f7dc - but maybe I'm off. This bug was also encountered by others recently.

Steps to reproduce

import numpy as np
import cv2
print(cv2.__version__)
im = np.pad(np.ones((10,10), np.uint8)*255, 10)
cnts = cv2.findContours(im, cv2.RETR_EXTERNAL, cv2.CHAIN_APPROX_SIMPLE)[-2]
cnt = cnts[0]
pt = np.array([3.3, 4.4])  # from some calculation
pt = tuple(np.array(pt, np.int32))
print(cnt.dtype, pt[0].dtype)
cv2.pointPolygonTest(cnt, pt, False)

Outputs for 4.5.2:

4.5.2
int32 int32
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
cv2.error: OpenCV(4.5.2) :-1: error: (-5:Bad argument) in function 'pointPolygonTest'
> Overload resolution failed:
>  - Can't parse 'pt'. Sequence item with index 0 has a wrong type
>  - Can't parse 'pt'. Sequence item with index 0 has a wrong type

Output for 4.5.1.48:

4.5.1
int32 int32
-1.0

<!-- to add code example fence it with triple backticks and optional file extension .cpp // C++ code example or attach as .txt or .zip file -->

Issue submission checklist

• [x] I report the issue, it's not a question <!-- OpenCV team works with forum.opencv.org, Stack Overflow and other communities to discuss problems. Tickets with question without real issue statement will be closed. -->
• [x] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found solution <!-- Places to check:
  • OpenCV documentation: https://docs.opencv.org
  • FAQ page: https://github.com/opencv/opencv/wiki/FAQ
  • OpenCV forum: https://forum.opencv.org
  • OpenCV issue tracker: https://github.com/opencv/opencv/issues?q=is%3Aissue
  • Stack Overflow branch: https://stackoverflow.com/questions/tagged/opencv -->
• [x] I updated to latest OpenCV version and the issue is still there <!-- master branch for OpenCV 4.x and 3.4 branch for OpenCV 3.x releases. OpenCV team supports only latest release for each branch. The ticket is closed, if the problem is not reproduced with modern version. -->
• [x] There is reproducer code and related data files: videos, images, onnx, etc <!-- The best reproducer -- test case for OpenCV that we can add to the library. Recommendations for media files and binary files:
  • Try to reproduce the issue with images and videos in opencv_extra repository to reduce attachment size
  • Use PNG for images, if you report some CV related bug, but not image reader issue
  • Attach the image as archive to the ticket, if you report some reader issue. Image hosting services compress images and it breaks the repro code.
  • Provide ONNX file for some public model or ONNX file with with random weights, if you report ONNX parsing or handling issue. Architecture details diagram from netron tool can be very useful too. See https://lutzroeder.github.io/netron/ -->