consistently use self.mktemp() to create a temporary directory in tests #2432
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#2432
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently we use a hotchpotch of methods to create a temporary directory for a test -- specifying the name manually, using a
workdir
method, usingself.mktemp()
fromtwisted.trial.unittest.TestCase
, etc. (It is usually consistent within a test module but not across modules.)We should just use
self.mktemp()
, or if there is something wrong with that then we should consistently use our own mixin.I agree it's a bit of a mess. My only two concerns:
Trial puts everything in
./_trial_temp
, andrmtree
s it at the beginning of each test run. This provides a predictable location, and an upper bound (of size=1) on the litter.So I guess I'm in favor of using our own mixin that uses the (fully-qualified) name of the test case to produce a subdirectory of
_trial_temp
.Replying to warner:
mktemp()
fromtwisted.trial.unittest.TestCase
already does that.The one thing I don't like about
mktemp()
is that the path it generates is not deterministic, due to its use ofmkdtemp
(implementation in Twisted v15.2.0). What I actually want isos.path.dirname(os.path.dirname(self.mktemp())
, I think. Maybe it would be better to have a mixin to shorten that, so that if we want to change it, we only need to do so in one place.Also, I think I'd prefer for our mixin method to return an absolute Unicode path, rather than a relative
str
path.Milestone renamed
moving most tickets from 1.12 to 1.13 so we can release 1.12 with magic-folders
Probably switch to testtools and use the TempDir fixture.
Moving open issues out of closed milestones.
Ticket retargeted after milestone closed