Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork939
Allow mmap not just for py2.6, 2.7 and 3.6+ but also 3.0+#736
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
Uh oh!
There was an error while loading.Please reload this page.
Conversation
codecov-io commentedMar 18, 2018
Codecov Report
@@ Coverage Diff @@## master #736 +/- ##==========================================- Coverage 94.66% 94.66% -0.01%========================================== Files 60 60 Lines 9340 9338 -2 ==========================================- Hits 8842 8840 -2 Misses 498 498
Continue to review full report at Codecov.
|
What a great catch! Thanks a lot for your contribution! |
…heckAllow mmap not just for py2.6, 2.7 and 3.6+ but also 3.0+
This version check only checks the minor number: the
y
in Pythonx.y
.So mmap is available for Python 2.6 and 2.7, and 3.6+, but not for 3.0 to 3.5.
But I think the intent was to have memory maps for Python 2.6 and up, including all of Python 3.x (and 4.x etc.).
As Python 2.6 is the minimum supported version, the
allow_mmap
is alwaysTrue
for supported versions.