Skip to content

Conversation

@dargueta
Copy link
Contributor

@dargueta dargueta commented Jul 24, 2019

Type of changes

  • Bug fix
  • New feature
  • Documentation / docstrings
  • Tests
  • Other

Checklist

  • I've run the latest black with default args on new code.
  • I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
  • I've added tests for new code.
  • I accept that @willmcgugan may be pedantic in the code review.

Description

MemFS now immediately releases the memory used up by its files when close() is called, rather than when the file system gets garbage collected. Closes #308 .

@coveralls
Copy link

coveralls commented Jul 24, 2019

Coverage Status

Coverage decreased (-0.5%) to 99.078% when pulling d3c8d5a on dargueta:memoryfs-close into 37b46b4 on PyFilesystem:master.

posixpath.join(parent_dir, str(file_id)), UNICODE_TEXT
)

@unittest.skipIf(
Copy link
Member

Choose a reason for hiding this comment

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

Thorough test 👍

@dargueta
Copy link
Contributor Author

I know the contributors list is supposed to be sorted alphabetically but do I really need to put my name at the top? Feels weird.

@willmcgugan
Copy link
Member

@dargueta It's cool. The idea was that the order doesn't indicate significance of contribution.

PR looks good BTW, thanks. I'll give it another review soon.

@willmcgugan
Copy link
Member

Thanks

@willmcgugan willmcgugan merged commit ef8682b into PyFilesystem:master Jul 28, 2019
@mostafa
Copy link

mostafa commented Jul 28, 2019

Thanks

@dargueta dargueta deleted the memoryfs-close branch July 29, 2019 15:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Free memory on MemoryFS.close

5 participants