Skip to content
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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

Removing File-IO #28

Open
hayesall opened this issue Jun 5, 2022 · 0 comments
Open

Removing File-IO #28

hayesall opened this issue Jun 5, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@hayesall
Copy link
Member

hayesall commented Jun 5, 2022

Almost all file input-output traces through a few classes:

  • will.Utils.condor.CondorFile
  • will.Utils.NamedReader
  • will.Utils.NamedInputStream
  • BufferedReader
  • BufferedWriter

Removing the dependence on file-io means we no longer have to simulate an operating system under the code, and will make this much easier to test.
@hayesall hayesall added the enhancement New feature or request label Jun 5, 2022
@hayesall hayesall mentioned this issue Jun 5, 2022
Open
hayesall added a commit that referenced this issue Jun 5, 2022
@hayesall
🔥 Drop condor.chirp
25a6639 
These paths were invoked through a side-effect that loaded environment
variables and configuration files (in the user's home directory?).

I'm pretty sure from some prior reading that Chirp/Condor was a
utility for doing high-performance computing at University of
Madison-Wisconsin:
https://research.cs.wisc.edu/htcondor/

Part of #28
This was referenced Jun 5, 2022
Merged
Open
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hayesall