Search results

Literal "+" characters in file paths are incorrectly converted to spaces

Status: Open.

#1413 In jpype-project/jpype;

· baxter-huntington opened on Jul 1, 2026

Test bench instability

Status: Open.

#1378 In jpype-project/jpype;

· Thrameos opened on May 29, 2026

Incorrect ambiguity report

Status: Open.

#1371 In jpype-project/jpype;

· Thrameos opened on May 20, 2026

Proxy efficiency Improvements

Status: Open.

#1369 In jpype-project/jpype;

· Thrameos opened on May 11, 2026

Documentation: best way to access numpy arrays from Java without copying

documentationIssue with our documentation (misleading, missing, bad)Issue with our documentation (misleading, missing, bad)

Status: Open.

#1341 In jpype-project/jpype;

· kno10 opened on Feb 3, 2026

File Windows fatal exception: access violation

need-info

Status: Open.

#1334 In jpype-project/jpype;

· tae898 opened on Jan 3, 2026

Unhandled exception on isinstance(..., JException)

questionQuestion on how to use JPypeQuestion on how to use JPype

Status: Open.

#1329 In jpype-project/jpype;

· pulkin opened on Nov 19, 2025

Accessing Java variables with illegal Python characters

Status: Open.

#1328 In jpype-project/jpype;

· ryanmkurtz opened on Nov 17, 2025

remove legacy (and or deprecated) code

Status: Open.

#1324 In jpype-project/jpype;

· marscher opened on Oct 29, 2025

Runtime error when moving from 1.5.2 to 1.6.0

java8_deprecation

Status: Open.

#1312 In jpype-project/jpype;

· mxufc29 opened on Jul 22, 2025

Restricted methods will be blocked in a future release unless native access is enabled

Status: Open.

#1310 In jpype-project/jpype;

· erbenson opened on Jul 15, 2025

Dealing with python object structure

enhancementImprovement in capability planned for future releaseImprovement in capability planned for future release

Status: Open.

#1299 In jpype-project/jpype;

· Thrameos opened on May 11, 2025