-
This is a patch to get PyPerforce to compile with the 2009.1 API. I did this because I needed FreeBSD 7 support, and it is only available in that version. I have not done extensive testing, but for the most part it seems to work.
2009-08-12 21:19:52 UTC by ehuss
-
Here's a patch to setup.py which worked for me:
--- setup.py Mon Nov 10 23:26:44 2008 UTC
+++ setup.py Mon Nov 10 23:38:12 2008 UTC
@@ -13,6 +13,7 @@
('USE_CRLF', None)]
p4apiLibs = ['libclient', 'librpc', 'libsupp',
'oldnames', 'kernel32', 'wsock32', 'advapi32']
+ p4apiExtraLinkArgs = []
elif sys.platform == 'linux2':
# The...
2008-11-11 00:51:01 UTC by nobody
-
You can find the Perforce API files here:
ftp://ftp.perforce.com/perforce/r06.2/bin.macosx104x86/p4api.tar.
2008-11-11 00:46:55 UTC by nobody
-
I'll try to put up a compiled Win32 Python2.5 version of PyProtocols in the downloads section.
2008-08-08 22:08:02 UTC by lewisbaker
-
It would be nice to have some helper methods to simplify the process of authenticating with Perforce.
eg.
p4 = Connection()
p4.connect()
p4.login(password='secret')
In the simple case this could just map onto the call to p4.run("login", input='secret'). However, this call will result in an update to the P4TICKETS file which may not be ideal for certain types of scripts.
Perhaps...
2008-07-27 12:33:26 UTC by lewisbaker
-
I'm closing this as a "won't fix".
KeepAlive support has been added and any required exception behaviour can be implemented using this and by catching exceptions before they propagate back to ClientApi.run().
2008-07-27 12:17:37 UTC by lewisbaker
-
I've had a look at the code and it seems that many of the calls into Python ClientUser methods don't actually catch the exceptions and clear the exception state. This could be causing downstream Python API calls that check for an exception state to fail (perhaps causing isMethodOverridden to return false on a subsequent callback).
The obvious solution to this is to catch and clear any...
2008-07-27 12:13:33 UTC by lewisbaker
-
Fix now merged into trunk.
Should be fixed in 0.5 release.
2008-07-27 11:54:29 UTC by lewisbaker
-
If you use the IOutputConsumer interface, and one of your methods (such as outputRecord) raises an exception, the default Perforce method gets called (printing everything to stdout) before the exception is handled. This is confusing, especially if your command outputs a large amount of data.
I tried to track down the problem, but I couldn't figure out why it was behaving that way. For some...
2008-07-22 20:00:51 UTC by ehuss
-
You're right about the const_char thing, I had originally made these changes against an older version of the API long ago. Thanks!
2008-07-22 18:58:16 UTC by nobody
