This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author db3l
Recipients db3l, loewis, ned.deily, tarek, titus
Date 2009-11-29.22:15:49
SpamBayes Score 0.00017013133
Marked as misclassified No
Message-id <1259532952.02.0.842358364406.issue7408@psf.upfronthosting.co.za>
In-reply-to
Content
> I think that's difficult to implement, as the files are not there
> anymore when the check is made (only the tarfile); somebody correct
> me if I'm wrong.

The files are created during setup, and I think exist through the
duration of the test, only being removed during tearDown (via
TempDirManager mixin) - otherwise this test couldn't be creating two
separate archives from the same sources.

Worst case though, just have setup grab the test file ownership
information and hang onto it in general.  But I think this specific test
could also check filesystem ownership at any point in the test.
History
Date User Action Args
2009-11-29 22:15:52db3lsetrecipients: + db3l, loewis, titus, tarek, ned.deily
2009-11-29 22:15:52db3lsetmessageid: <1259532952.02.0.842358364406.issue7408@psf.upfronthosting.co.za>
2009-11-29 22:15:50db3llinkissue7408 messages
2009-11-29 22:15:50db3lcreate