Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Min/MaxSupportedVersion andIsSupportedVersion onPythonEngine#1798

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
filmor merged 1 commit intopythonnet:masterfromlosttech:SupportedVersions
May 26, 2022

Conversation

lostmsu
Copy link
Member

Does this close any currently open issues?

fixes#1724

Checklist

Check all those that are applicable and complete.

  • Make sure to include one or more tests for your change
  • Updated theCHANGELOG

@lostmsu
Copy link
MemberAuthor

:/ I am puzzled. What does this change have to do with segfaults? Only on *nix? Ugh...

@@ -127,6 +127,10 @@ public static string PythonPath
}
}

public static Version MinSupportedVersion => new(3, 7);
public static Version MaxSupportedVersion => new(3, 10, int.MaxValue, int.MaxValue);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Maybe something more "readable", like 999 instead of maxint?

Copy link
MemberAuthor

@lostmsulostmsuMay 26, 2022
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I thought of that, but it won't work if there are builds of Python that use build number not as patch (e.g. patch .4), but in a Windows manner like .19041.365, or maybe doMaxSupportedVersionExclusive. Alternatively, we can only leave theIsSupportedVersion check and provide an error string in a separate property.

What do you think?

@filmor
Copy link
Member

:/ I am puzzled. What does this change have to do with segfaults? Only on *nix? Ugh...

Just tested it as well, it only happens on Mono...

@filmor
Copy link
Member

filmor commentedMay 26, 2022
edited
Loading

Further observations:

  • The culprit is the call, the comparisons in the tests seem fine
  • Only theenum conversions with max int/long/ulong fail, if I remove these, the tests run though
  • Only happens when all tests are run in order

@filmorfilmor merged commit1492d7d intopythonnet:masterMay 26, 2022
@lostmsulostmsu deleted the SupportedVersions branchMay 26, 2022 19:22
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@filmorfilmorfilmor left review comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@lostmsu@filmor

[8]ページ先頭

©2009-2025 Movatter.jp