P4OO.File#
P4OOFile
dataclass
#
Bases: _P4OOBase
Perforce File Object
The P4OOFile object does not have a first-class equivalent in Perforce.
It is just used to manage a path to a local file, or a depot file,
or a revision range, or... Anything used to communicate filenames to
Perforce really.
Within P4OO.py, P4OOFile objects are used to track and connect output
from one Perforce operation to the next, carrying your _P4OOConnection
object(s) along for the ride.
id Required: Yes
See Also
Perforce Helix Core Command Reference: https://www.perforce.com/manuals/cmdref/Content/CmdRef/p4_files.html
P4OOFileSet
dataclass
#
Bases: _P4OOSet
P4OOSet of P4OOFile objects
query(archived=False, allrevisions=False, excludeDeleted=False, maxresults=None, files=None, **kwargs)
#
Executes p4 files query
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
archived |
bool
|
List all revisions in specified range |
False
|
allrevisions |
bool
|
Limit output to files in archive depots |
False
|
excludeDeleted |
bool
|
Exclude deleted/archived files. archive depots |
False
|
maxresults |
int
|
Return only the first [max] results |
None
|
files |
P4OOFileSet | P4OOFile | str
|
The set of file revisions to query |
None
|
Returns:
| Type | Description |
|---|---|
P4OOFileSet
|
|
See Also
Perforce Helix Core Command Reference: https://www.perforce.com/manuals/cmdref/Content/CmdRef/p4_files.html