From tickets at pyamf.org Thu Jan 1 22:50:24 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 1 22:51:05 2009 Subject: [pyamf-tickets] #343: Refactor the test suite to be python implementation independent In-Reply-To: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> References: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> Message-ID: <041.449e177701411c9fbc239d32308554b9@pyamf.org> #343: Refactor the test suite to be python implementation independent -------------------------+-------------------------------------------------- Reporter: nick | Owner: thijs Type: enhancement | Status: assigned Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.3.1 Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * keywords: => review * status: new => assigned * owner: nick => thijs Comment: All tests have now been refactored to be python implementation independent. There are still Jython tests failing but these are unrelated. -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 16:13:51 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 2 16:16:34 2009 Subject: [pyamf-tickets] #398: Add SQLAlchemy buildstep In-Reply-To: <033.5541fbd65b967b59eb46f6c8811a5633@pyamf.org> References: <033.5541fbd65b967b59eb46f6c8811a5633@pyamf.org> Message-ID: <042.cb068bb82f27f91063061f028625e4da@pyamf.org> #398: Add SQLAlchemy buildstep ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: closed Priority: major | Milestone: 0.4 Component: Testing | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by thijs): * status: accepted => closed * resolution: => fixed Old description: > The upcoming SQLAlchemyAdapter should be tested on both SQLAlchemy 0.4.x > and the latest 0.5.x New description: The upcoming SQLAlchemyAdapter should be tested on both SQLAlchemy 0.4.x and the latest 0.5.x release. -- Comment: Fixed with r1945 -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 16:37:15 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 2 16:37:35 2009 Subject: [pyamf-tickets] #409: Update copyright headers In-Reply-To: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> References: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> Message-ID: <042.43283f6d1a7e10bfca2480a40e747893@pyamf.org> #409: Update copyright headers ---------------------------+------------------------------------------------ Reporter: thijs | Owner: feisley Type: defect | Status: accepted Priority: blocker | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Changes (by feisley): * status: new => accepted * owner: thijs => feisley -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 16:47:20 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 2 16:47:38 2009 Subject: [pyamf-tickets] #410: Support for SQLAlchemy 0.4.0 Message-ID: <032.1f628095e45e344a1a6d84bb2b92080f@pyamf.org> #410: Support for SQLAlchemy 0.4.0 ----------------------+----------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- When using SQLAlchemy 0.4.0 the following traceback occurs when running the test suite. {{{ #!python Traceback (most recent call last): File "./setup.py", line 139, in "Topic :: Software Development :: Libraries :: Python Modules", File "C:\Python25\lib\distutils\core.py", line 151, in setup dist.run_commands() File "C:\Python25\lib\distutils\dist.py", line 974, in run_commands self.run_command(cmd) File "C:\Python25\lib\distutils\dist.py", line 994, in run_command cmd_obj.run() File "build\bdist.win32\egg\setuptools\command\test.py", line 121, in run File "build\bdist.win32\egg\setuptools\command\test.py", line 101, in with_project_on_sys_path File "./setup.py", line 35, in run_tests self.run_twisted() File "./setup.py", line 25, in run_twisted r.run(suite()) File "c:\buildbot\pyamf\x86-win2003-py25\build\pyamf\tests\__init__.py", line 35, in suite suite.addTest(mod.suite()) File "c:\buildbot\pyamf\x86-win2003-py25\build\pyamf\tests\test_adapters.py", line 78, in suite mod = __import__('.'.join(base_mod)) File "c:\buildbot\pyamf\x86-win2003-py25\build\pyamf\tests\adapters\test_sqlalchemy.py", line 17, in import pyamf.flex File "c:\buildbot\pyamf\x86-win2003-py25\build\pyamf\flex\__init__.py", line 203, in metadata=['external', 'amf3']) File "c:\buildbot\pyamf\x86-win2003-py25\build\pyamf\__init__.py", line 816, in register_class alias_klass = util.get_class_alias(klass) File "c:\buildbot\pyamf\x86-win2003-py25\build\pyamf\util\__init__.py", line 584, in get_class_alias if kl(klass) is True: File "c:\buildbot\pyamf\x86-win2003-py25\build\pyamf\adapters\_sqlalchemy.py", line 125, in is_class_sa_mapped class_mapper(klass) File "c:\buildbot\pyamf\x86-win2003-py25\build\sqlalchemy\orm\util.py", line 386, in class_mapper raise exceptions.InvalidRequestError("Class '%s' entity name '%s' has no mapper associated with it" % (class_.__name__, entity_name)) sqlalchemy.exceptions.InvalidRequestError: Class 'ArrayCollection' entity name 'None' has no mapper associated with it }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 16:53:04 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 2 16:55:03 2009 Subject: [pyamf-tickets] #411: GAE buildslave - ValueError: No JSON object could be decoded Message-ID: <033.983707531c8c10d93bfb23317d9c9bff@pyamf.org> #411: GAE buildslave - ValueError: No JSON object could be decoded ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.5 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Sometimes the GoogleAppEngine buildslave fails with the following error: {{{ #!python Traceback (most recent call last): File "client.py", line 216, in x = GAETestRunner(options.url) File "client.py", line 71, in __init__ self.get_all_tests() File "client.py", line 87, in get_all_tests ret = simplejson.loads(self._get_url('tests')) File "build/bdist.linux-x86_64/egg/simplejson/__init__.py", line 262, in loads File "build/bdist.linux-x86_64/egg/simplejson/decoder.py", line 251, in decode File "build/bdist.linux-x86_64/egg/simplejson/decoder.py", line 270, in raw_decode ValueError: No JSON object could be decoded }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 17:00:46 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 2 17:07:44 2009 Subject: [pyamf-tickets] #410: Support for SQLAlchemy 0.4.0 In-Reply-To: <032.1f628095e45e344a1a6d84bb2b92080f@pyamf.org> References: <032.1f628095e45e344a1a6d84bb2b92080f@pyamf.org> Message-ID: <041.8f123244aed365b3e5547ac2fdcc6475@pyamf.org> #410: Support for SQLAlchemy 0.4.0 ----------------------+----------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: accepted Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by nick): * status: new => accepted Comment: Branching to source:pyamf/branches/sqlalchemy-four-point-oh-410. -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 17:07:54 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 2 17:13:49 2009 Subject: [pyamf-tickets] #409: Update copyright headers In-Reply-To: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> References: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> Message-ID: <042.93cccee05c66a04d37f7c0bc65cf9f1a@pyamf.org> #409: Update copyright headers ---------------------------+------------------------------------------------ Reporter: thijs | Owner: feisley Type: defect | Status: accepted Priority: blocker | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Comment(by feisley): Branching to source:pyamf/branches/2009-copyright-409 -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 17:11:40 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 2 17:18:04 2009 Subject: [pyamf-tickets] #412: Cosmetic updates for GAE buildslave Message-ID: <033.bec95add736ebd98febc2855279b9457@pyamf.org> #412: Cosmetic updates for GAE buildslave -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: new Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Some cosmetic changes to make the output more readable: 1. The app starts with a checkout like this: {{{ A . A app A app/manage.py A app/app.yaml A app/assets }}} Would be better if it first prints a start message with the full repository path like: {{{ Google App Engine buildslave (v0.x) ====================== 1. Google App Engine - SVN Checkout: http://svn.pyamf.org/pyamf/trunk A . A app A app/manage.py A app/app.yaml A app/assets }}} 2. When it finishes the first checkout it goes on with the next checkout like: {{{ A client.py Exported revision 1947. A app/pyamf A app/pyamf/tests }}} This would read better (like the first checkout): {{{ A client.py Exported revision 1947. 2. PyAMF - SVN Checkout: http://svn.etc A app/pyamf A app/pyamf/tests }}} 3. Add a break after the checkout: {{{ A app/pyamf/flex/__init__.py Exported revision 1947. Scanning files on local disk. }}} 4. Add these statements on their own line and separate them with a break: {{{ Password for gae-buildslave@pyamf.org: Traceback (most recent call last): }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 17:27:27 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 2 17:27:43 2009 Subject: [pyamf-tickets] #409: Update copyright headers In-Reply-To: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> References: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> Message-ID: <042.e20317d3f285112d91b0f56b0d4d760e@pyamf.org> #409: Update copyright headers ---------------------------+------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: review | ---------------------------+------------------------------------------------ Changes (by feisley): * keywords: => review * status: accepted => assigned * owner: feisley => nick Comment: Changes complete, please review. -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 17:30:37 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 2 17:31:16 2009 Subject: [pyamf-tickets] #413: Cosmetic updates for GAE buildslave In-Reply-To: <033.ae8cde3cf18b67a5def408e3debaa669@pyamf.org> References: <033.ae8cde3cf18b67a5def408e3debaa669@pyamf.org> Message-ID: <042.acb32a4e4ad558e678b6ce5118605a4a@pyamf.org> #413: Cosmetic updates for GAE buildslave --------------------------+------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: closed Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.4 Resolution: duplicate | Keywords: --------------------------+------------------------------------------------- Changes (by thijs): * status: new => closed * resolution: => duplicate Comment: #412 -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 17:32:18 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 2 17:32:35 2009 Subject: [pyamf-tickets] #410: Support for SQLAlchemy 0.4.0 In-Reply-To: <032.1f628095e45e344a1a6d84bb2b92080f@pyamf.org> References: <032.1f628095e45e344a1a6d84bb2b92080f@pyamf.org> Message-ID: <041.26bdad544ba0e9e9c8db4a049bc4846b@pyamf.org> #410: Support for SQLAlchemy 0.4.0 ----------------------+----------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: accepted Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Comment(by thijs): Fixed with r1951 -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 17:32:36 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 2 17:33:22 2009 Subject: [pyamf-tickets] #410: Support for SQLAlchemy 0.4.0 In-Reply-To: <032.1f628095e45e344a1a6d84bb2b92080f@pyamf.org> References: <032.1f628095e45e344a1a6d84bb2b92080f@pyamf.org> Message-ID: <041.c863995d3bd84214d36f30425e14e88a@pyamf.org> #410: Support for SQLAlchemy 0.4.0 -----------------------+---------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: closed Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Resolution: fixed | Keywords: -----------------------+---------------------------------------------------- Changes (by thijs): * status: accepted => closed * resolution: => fixed -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 17:38:52 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 2 17:39:09 2009 Subject: [pyamf-tickets] #409: Update copyright headers In-Reply-To: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> References: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> Message-ID: <042.c4312f188d832588f576a3a0c202df36@pyamf.org> #409: Update copyright headers ---------------------------+------------------------------------------------ Reporter: thijs | Owner: feisley Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Changes (by nick): * keywords: review => * owner: nick => feisley Comment: Updates look good, please merge. -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 18:08:50 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 2 18:09:07 2009 Subject: [pyamf-tickets] #409: Update copyright headers In-Reply-To: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> References: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> Message-ID: <042.e9e45c2d1f286a63a02ab94c8c01e51c@pyamf.org> #409: Update copyright headers ---------------------------+------------------------------------------------ Reporter: thijs | Owner: feisley Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Comment(by feisley): We forgot to do the examples so... Branching to source:examples/branches/2009-copyright-409 -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 18:09:43 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 2 18:10:01 2009 Subject: [pyamf-tickets] #409: Update copyright headers In-Reply-To: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> References: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> Message-ID: <042.837b7d05e8f9e19a1b3268da33d003c0@pyamf.org> #409: Update copyright headers ---------------------------+------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: review | ---------------------------+------------------------------------------------ Changes (by feisley): * keywords: => review * owner: feisley => nick -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 18:17:35 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 2 18:17:52 2009 Subject: [pyamf-tickets] #409: Update copyright headers In-Reply-To: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> References: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> Message-ID: <042.66b312314ac22344941bfab36a01b164@pyamf.org> #409: Update copyright headers ---------------------------+------------------------------------------------ Reporter: thijs | Owner: darkhorse Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Changes (by nick): * keywords: review => * owner: nick => darkhorse Comment: Examples look good too :) -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 19:49:12 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 2 19:49:30 2009 Subject: [pyamf-tickets] #409: Update copyright headers In-Reply-To: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> References: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> Message-ID: <042.4845e7a1b423ea3dc60700b18a2a6ada@pyamf.org> #409: Update copyright headers ---------------------------+------------------------------------------------ Reporter: thijs | Owner: feisley Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Changes (by nick): * owner: darkhorse => feisley -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 19:50:50 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 2 19:51:43 2009 Subject: [pyamf-tickets] #409: Update copyright headers In-Reply-To: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> References: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> Message-ID: <042.558f9bb2910b0397c911c147e8ad34e6@pyamf.org> #409: Update copyright headers ----------------------------+----------------------------------------------- Reporter: thijs | Owner: feisley Type: defect | Status: closed Priority: blocker | Milestone: 0.4 Component: Documentation | Version: 0.4 Resolution: fixed | Keywords: ----------------------------+----------------------------------------------- Changes (by feisley): * status: assigned => closed * resolution: => fixed Comment: Fixed in r1957 and r1959 -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 19:58:20 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 2 19:58:39 2009 Subject: [pyamf-tickets] #320: UnknownClassAlias: NetDebugConfig In-Reply-To: <033.e56ef1fb78caf978d51f8969004d5db1@pyamf.org> References: <033.e56ef1fb78caf978d51f8969004d5db1@pyamf.org> Message-ID: <042.571e232e8a005792b5df8062ca1db942@pyamf.org> #320: UnknownClassAlias: NetDebugConfig ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: defect | Status: assigned Priority: minor | Milestone: 0.5 Component: Remoting | Version: 0.3.1 Keywords: | ----------------------+----------------------------------------------------- Changes (by nick): * owner: nick => thijs * status: new => assigned Comment: Using 0.4rc2 this now gives: {{{ #!python }}} So this is now invalid? -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 3 14:05:59 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 3 14:06:16 2009 Subject: [pyamf-tickets] #353: Bytearray test hack showing in Jython In-Reply-To: <033.7ab88d6b724bc380e58306e1cbfc2367@pyamf.org> References: <033.7ab88d6b724bc380e58306e1cbfc2367@pyamf.org> Message-ID: <042.aad050a3b93f48a2c7b3138ce047c6dc@pyamf.org> #353: Bytearray test hack showing in Jython ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: task | Status: accepted Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.3.1 Keywords: | ---------------------+------------------------------------------------------ Changes (by nick): * priority: major => minor * status: new => accepted * type: defect => task Comment: This turns out to be a compatibility issue with Jython. It raises `java.util.zip.DataFormatException` instead of zlib.error. I have raised this issue in Jython's [http://bugs.jython.org/issue1217 bug tracker]. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 4 00:36:31 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 4 00:36:55 2009 Subject: [pyamf-tickets] #343: Refactor the test suite to be python implementation independent In-Reply-To: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> References: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> Message-ID: <041.06c268b9c818c3a82b06f11185e2004d@pyamf.org> #343: Refactor the test suite to be python implementation independent -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: assigned Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.3.1 Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * keywords: review => * owner: thijs => nick Comment: EchoTest dies for me with: {{{ AMF error received (after 0.02 sec): description: error code: Channel.Call.Failed details: NetConnection.Call.Failed: HTTP: Failed Error: ReferenceError: Error #1069: Property 0 not found on String and there is no default value. at org.red5.samples.echo::EchoTest/onRemotingError() at echotest/__echoService_fault() at flash.events::EventDispatcher/dispatchEventFunction() at flash.events::EventDispatcher/dispatchEvent() at mx.rpc::AbstractService/dispatchEvent() at mx.rpc.remoting.mxml::RemoteObject/dispatchEvent() at mx.rpc::AbstractOperation/http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent() at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faultHandler() at mx.rpc::Responder/fault() at mx.rpc::AsyncRequest/fault() at NetConnectionMessageResponder/channelFaultHandler() at flash.events::EventDispatcher/dispatchEventFunction() at flash.events::EventDispatcher/dispatchEvent() at mx.messaging.channels::AMFChannel/statusHandler() }}} Might be related to an old version of the EchoTest swf. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 4 04:33:21 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 4 04:33:56 2009 Subject: [pyamf-tickets] #388: Exclude third-party class(es) in our API documentation (was: Exclude Twisted class(es) in our API documentation) In-Reply-To: <033.f71ccf163a21187c1cf6d3618880074f@pyamf.org> References: <033.f71ccf163a21187c1cf6d3618880074f@pyamf.org> Message-ID: <042.3b00c3a09d96c36eea970ce052c09221@pyamf.org> #388: Exclude third-party class(es) in our API documentation ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: defect | Status: accepted Priority: major | Milestone: 0.5 Component: Documentation | Version: 0.3.1 Keywords: | ---------------------------+------------------------------------------------ -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 4 04:37:08 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 4 04:37:27 2009 Subject: [pyamf-tickets] #414: Support for the NetConnection Debugger panel Message-ID: <033.fb87f58ac69af005f99f0918b90cd93f@pyamf.org> #414: Support for the NetConnection Debugger panel ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: new Priority: minor | Milestone: At some point Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- The NetDebug object is the ActionScript 2.0 object that powers the NetConnection Debugger panel, allowing a developer to view and trace output to and from the application server. Would be nice to have this standard Remoting class available in PyAMF (like AMFPHP and others). -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 4 04:39:16 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 4 04:39:42 2009 Subject: [pyamf-tickets] #320: UnknownClassAlias issue with .sol files (was: UnknownClassAlias: NetDebugConfig) In-Reply-To: <033.e56ef1fb78caf978d51f8969004d5db1@pyamf.org> References: <033.e56ef1fb78caf978d51f8969004d5db1@pyamf.org> Message-ID: <042.df5c76447bc7ce26ca0aeeb4814f67ab@pyamf.org> #320: UnknownClassAlias issue with .sol files ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: defect | Status: assigned Priority: minor | Milestone: 0.5 Component: Shared Object | Version: 0.3.1 Keywords: | ---------------------------+------------------------------------------------ Changes (by thijs): * component: Remoting => Shared Object Old description: > The > [http://etutorials.org/Macromedia/Fash+remoting.+the+definitive+guide/Part+III+Advanced+Flash+Remoting/Chapter+15.+Flash+Remoting+API/NetDebug+Object/ > NetDebug] object is the !ActionScript 2.0 object that powers the > !NetConnection Debugger panel, allowing a developer to view and trace > output to and from the application server. Would be nice to have this > standard Remoting class available in PyAMF (like AMFPHP and others). > While testing the attached .sol [attachment:TestMovie_Config_Info.sol > file] like this: > > {{{ > #!python > from pyamf import sol > > path = 'TestMovie_Config_Info.sol' > lso = sol.load(path) > > print lso > }}} > > I'm getting this error: > {{{ > Traceback (most recent call last):', ' > File "/pyamf/trunk/pyamf/remoting/amf0.py", line 100, in __call__ > response.body = self._getBody(request, response, service_request, *args, > **kwargs)', ' > File "/pyamf/trunk/pyamf/remoting/amf0.py", line 56, in _getBody > return self.gateway.callServiceRequest(service_request, *request.body, > **kwargs)', ' > File "/pyamf/trunk/pyamf/remoting/gateway/__init__.py", line 471, in > callServiceRequest return service_request(*args)', ' > File "/pyamf/trunk/pyamf/remoting/gateway/__init__.py", line 208, in > __call__ return self.service(self.method, args)', ' > File "/pyamf/trunk/pyamf/remoting/gateway/__init__.py", line 110, in > __call__ return func(*params)', ' > File "/workspace/pyamf-temp2/sol/python/service.py", line 90, in > getDetails lso = sol.load(path)', ' > File "/pyamf/trunk/pyamf/sol.py", line 163, in load name, values = > decode(f.read())', ' > File "/pyamf/trunk/pyamf/sol.py", line 83, in decode value = > decoder.readElement()', ' > File "/pyamf/trunk/pyamf/__init__.py", line 486, in readElement return > func()', ' > File "/pyamf/trunk/pyamf/amf0.py", line 296, in readTypedObject alias > = pyamf.load_class(classname)', ' > File "/pyamf/trunk/pyamf/__init__.py", line 777, in load_class raise > UnknownClassAlias, "Unknown alias %s" % alias', > 'UnknownClassAlias: Unknown alias NetDebugConfig' > }}} New description: While testing the attached .sol [attachment:TestMovie_Config_Info.sol file] like this: {{{ #!python from pyamf import sol path = 'TestMovie_Config_Info.sol' lso = sol.load(path) print lso }}} I'm getting this error: {{{ Traceback (most recent call last):', ' File "/pyamf/trunk/pyamf/remoting/amf0.py", line 100, in __call__ response.body = self._getBody(request, response, service_request, *args, **kwargs)', ' File "/pyamf/trunk/pyamf/remoting/amf0.py", line 56, in _getBody return self.gateway.callServiceRequest(service_request, *request.body, **kwargs)', ' File "/pyamf/trunk/pyamf/remoting/gateway/__init__.py", line 471, in callServiceRequest return service_request(*args)', ' File "/pyamf/trunk/pyamf/remoting/gateway/__init__.py", line 208, in __call__ return self.service(self.method, args)', ' File "/pyamf/trunk/pyamf/remoting/gateway/__init__.py", line 110, in __call__ return func(*params)', ' File "/workspace/pyamf-temp2/sol/python/service.py", line 90, in getDetails lso = sol.load(path)', ' File "/pyamf/trunk/pyamf/sol.py", line 163, in load name, values = decode(f.read())', ' File "/pyamf/trunk/pyamf/sol.py", line 83, in decode value = decoder.readElement()', ' File "/pyamf/trunk/pyamf/__init__.py", line 486, in readElement return func()', ' File "/pyamf/trunk/pyamf/amf0.py", line 296, in readTypedObject alias = pyamf.load_class(classname)', ' File "/pyamf/trunk/pyamf/__init__.py", line 777, in load_class raise UnknownClassAlias, "Unknown alias %s" % alias', 'UnknownClassAlias: Unknown alias NetDebugConfig' }}} -- Comment: Updating ticket description and moving most of it to a second ticket (#414). -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 4 04:42:14 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 4 04:42:30 2009 Subject: [pyamf-tickets] #320: UnknownClassAlias issue with .sol files In-Reply-To: <033.e56ef1fb78caf978d51f8969004d5db1@pyamf.org> References: <033.e56ef1fb78caf978d51f8969004d5db1@pyamf.org> Message-ID: <042.0217e074eb516616f630fa3040f8b711@pyamf.org> #320: UnknownClassAlias issue with .sol files ----------------------------+----------------------------------------------- Reporter: thijs | Owner: thijs Type: defect | Status: closed Priority: minor | Milestone: 0.4 Component: Shared Object | Version: 0.3.1 Resolution: fixed | Keywords: ----------------------------+----------------------------------------------- Changes (by thijs): * status: assigned => closed * resolution: => fixed * milestone: 0.5 => 0.4 Comment: I'm getting a similar output for the 2nd attached file. Replying to [comment:2 nick]: > So this is now invalid? I'm marking it as fixed cause it was broken before..... ;) -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 4 04:44:11 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 4 04:44:30 2009 Subject: [pyamf-tickets] #377: Porting C-Extension Module to Python 3.0 In-Reply-To: <033.89ff9943ac068869772f5a3137a306d4@pyamf.org> References: <033.89ff9943ac068869772f5a3137a306d4@pyamf.org> Message-ID: <042.521230a220f9e97e4ed7581b52edfcba@pyamf.org> #377: Porting C-Extension Module to Python 3.0 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: assigned Priority: minor | Milestone: Python 3000 Component: C-Extension | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * priority: major => minor * type: task => enhancement -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 4 04:47:08 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 4 04:47:25 2009 Subject: [pyamf-tickets] #123: Create benchmark sub-project In-Reply-To: <033.6c9ac6cdf6866be5fdb85665218e2d22@pyamf.org> References: <033.6c9ac6cdf6866be5fdb85665218e2d22@pyamf.org> Message-ID: <042.8233697eceb8dcc60792ba07dc268a89@pyamf.org> #123: Create benchmark sub-project ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: task | Status: new Priority: major | Milestone: 0.5 Component: Testing | Version: 0.1a Keywords: | ---------------------+------------------------------------------------------ Changes (by thijs): * milestone: At some point => 0.5 Comment: Good to have this now that there's a C-extension. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 01:04:25 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 5 01:04:42 2009 Subject: [pyamf-tickets] #415: Jython C-extension warning Message-ID: <033.73320f1720c8c11616fd38b85c4e88fe@pyamf.org> #415: Jython C-extension warning -------------------------+-------------------------------------------------- Reporter: thijs | Owner: gerard Type: enhancement | Status: new Priority: major | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Zope 3.5 or newer has a C-extension warning for Jython, might be a good idea to have something similar, instead of silently skipping the build_ext. {{{ ******************************************************************************** WARNING: An optional code optimization (C extension) could not be compiled. Optimizations for this package will not be available! Compiling extensions is not supported on Jython ******************************************************************************** }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 01:07:22 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 5 01:07:39 2009 Subject: [pyamf-tickets] #415: Jython C-extension warning In-Reply-To: <033.73320f1720c8c11616fd38b85c4e88fe@pyamf.org> References: <033.73320f1720c8c11616fd38b85c4e88fe@pyamf.org> Message-ID: <042.e9d9faca6434a30137efae96e3dd7a00@pyamf.org> #415: Jython C-extension warning -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: assigned Priority: minor | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * owner: gerard => nick * priority: major => minor * status: new => assigned -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 02:12:24 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 5 02:12:40 2009 Subject: [pyamf-tickets] #415: Jython C-extension warning In-Reply-To: <033.73320f1720c8c11616fd38b85c4e88fe@pyamf.org> References: <033.73320f1720c8c11616fd38b85c4e88fe@pyamf.org> Message-ID: <042.5cf063b8bfd0ac89374cab368c60bedc@pyamf.org> #415: Jython C-extension warning -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: assigned Priority: minor | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Description changed by thijs: Old description: > Zope 3.5 or newer has a C-extension warning for Jython, might be a good > idea to have something similar, instead of silently skipping the > build_ext. > > {{{ > ******************************************************************************** > WARNING: > > An optional code optimization (C extension) could not be > compiled. > > Optimizations for this package will not be available! > > Compiling extensions is not supported on Jython > ******************************************************************************** > }}} New description: Zope Interface 3.5 or newer has a C-extension warning for Jython, might be a good idea to have something similar, instead of silently skipping the build_ext. {{{ ******************************************************************************** WARNING: An optional code optimization (C extension) could not be compiled. Optimizations for this package will not be available! Compiling extensions is not supported on Jython ******************************************************************************** }}} -- -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 12:04:45 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 5 12:05:01 2009 Subject: [pyamf-tickets] #416: Release 0.4rc2 Message-ID: <033.fb458379f13bcedeea8fdf3c6d9ac259@pyamf.org> #416: Release 0.4rc2 ---------------------+------------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: new Priority: blocker | Milestone: 0.4 Component: Website | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Release PyAMF 0.4rc2 to the world. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 12:06:03 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 5 12:06:19 2009 Subject: [pyamf-tickets] #417: Release 0.4 final Message-ID: <033.a073f642c43fd4a9856ebdd72d5e1b46@pyamf.org> #417: Release 0.4 final ---------------------+------------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: new Priority: blocker | Milestone: 0.4 Component: Website | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Release 0.4 final to the world and maintain the [source:pyamf/branches/release-0.4 0.4] branch. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 12:59:21 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 5 12:59:37 2009 Subject: [pyamf-tickets] #418: Setup nightly builds page Message-ID: <033.c4ed5a69d76333c7af3ec68f3aefd46c@pyamf.org> #418: Setup nightly builds page ---------------------+------------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: new Priority: major | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Would be nice to have something similar to [http://nightly.webkit.org webkit]'s nightly builds page. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 18:22:24 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 5 18:22:42 2009 Subject: [pyamf-tickets] #407: Update SQLAlchemy Adapter docs In-Reply-To: <033.29e29526964e0174ddcd46cae5cc0be1@pyamf.org> References: <033.29e29526964e0174ddcd46cae5cc0be1@pyamf.org> Message-ID: <042.d47fb0aa40cc91a0228ae18d1d1dd4f2@pyamf.org> #407: Update SQLAlchemy Adapter docs ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: assigned Priority: major | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: review | ---------------------------+------------------------------------------------ Comment(by dthompso): I just copy and pasted from my code that uses a custom class that extends AbstractOperation. I'll change the example to Operation. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 19:18:59 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 5 19:19:29 2009 Subject: [pyamf-tickets] #407: Update SQLAlchemy Adapter docs In-Reply-To: <033.29e29526964e0174ddcd46cae5cc0be1@pyamf.org> References: <033.29e29526964e0174ddcd46cae5cc0be1@pyamf.org> Message-ID: <042.0ca9655703e3b14fe064525b497b7a3f@pyamf.org> #407: Update SQLAlchemy Adapter docs ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: assigned Priority: major | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: review | ---------------------------+------------------------------------------------ Comment(by dthompso): I changed the example to use RemoteObject in the methods. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 20:57:43 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 5 20:57:59 2009 Subject: [pyamf-tickets] #419: Put the changelog in the API docs Message-ID: <033.209be78cfaf0e68649600fc3e938e6ea@pyamf.org> #419: Put the changelog in the API docs ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: enhancement | Status: new Priority: major | Milestone: 0.5 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Would be nice to have the [source:pyamf/trunk/CHANGES.txt changelog] (and perhaps more files) generated to html and included in the API docs. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 21:00:33 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 5 21:01:07 2009 Subject: [pyamf-tickets] #420: Create example that uses the SQLAlchemy Adapter Message-ID: <033.50980369e7f89a7c2776b18e6efa6bcf@pyamf.org> #420: Create example that uses the SQLAlchemy Adapter ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: new Priority: major | Milestone: 0.5 Component: Examples | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Now that there's a [wiki:SQLAlchemyAdapter] it would be nice to have a python/flex|flash|air example that shows the use of the adapter. Could be anything really, perhaps some fictional address book thing, allowing you to delete/update/remove contacts? -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 21:03:50 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 5 21:04:09 2009 Subject: [pyamf-tickets] #420: Create example that uses the SQLAlchemy Adapter In-Reply-To: <033.50980369e7f89a7c2776b18e6efa6bcf@pyamf.org> References: <033.50980369e7f89a7c2776b18e6efa6bcf@pyamf.org> Message-ID: <042.3e665f5210ff47f36ffa8dbca054df2d@pyamf.org> #420: Create example that uses the SQLAlchemy Adapter ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: new Priority: major | Milestone: 0.5 Component: Examples | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by thijs): * cc: dthompso (added) Comment: Also see #407, which means the [wiki:SQLAlchemyAdapter] page needs to be updated when this ticket closes. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 21:05:22 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 5 21:05:39 2009 Subject: [pyamf-tickets] #416: Release 0.4rc2 In-Reply-To: <033.fb458379f13bcedeea8fdf3c6d9ac259@pyamf.org> References: <033.fb458379f13bcedeea8fdf3c6d9ac259@pyamf.org> Message-ID: <042.f195e15d0d76a578851e6b2cec8b57e8@pyamf.org> #416: Release 0.4rc2 ---------------------+------------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: accepted Priority: blocker | Milestone: 0.4 Component: Website | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Changes (by thijs): * status: new => accepted Comment: I updated the release date (today) in r1979, and uploaded new tarballs to the server. Will now update the [wiki:Download] page. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 21:11:45 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 5 21:12:01 2009 Subject: [pyamf-tickets] #421: Add note about optional adapter/gateway dependencies in the installation instructions Message-ID: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> #421: Add note about optional adapter/gateway dependencies in the installation instructions ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: enhancement | Status: new Priority: major | Milestone: 0.5 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Would be good to point out the various dependencies in the [source:pyamf/trunk/INSTALL.txt INSTALL.txt] and also including url's on the [wiki:Install] page. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 21:16:09 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 5 21:16:29 2009 Subject: [pyamf-tickets] #407: Update SQLAlchemy Adapter docs In-Reply-To: <033.29e29526964e0174ddcd46cae5cc0be1@pyamf.org> References: <033.29e29526964e0174ddcd46cae5cc0be1@pyamf.org> Message-ID: <042.088629d4d26f6f440562cefa0c5b6da3@pyamf.org> #407: Update SQLAlchemy Adapter docs ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: accepted Priority: major | Milestone: 0.5 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Changes (by thijs): * keywords: review => * status: assigned => accepted * milestone: 0.4 => 0.5 Comment: Replying to [comment:4 dthompso]: > I changed the example to use RemoteObject in the methods. Thanks. I opened #420 for a complete example in [source:examples/trunk] and will close this ticket when we finished that one. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 21:19:30 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 5 21:19:53 2009 Subject: [pyamf-tickets] #416: Release 0.4rc2 In-Reply-To: <033.fb458379f13bcedeea8fdf3c6d9ac259@pyamf.org> References: <033.fb458379f13bcedeea8fdf3c6d9ac259@pyamf.org> Message-ID: <042.fe626168bcc215a0a068797fd353148d@pyamf.org> #416: Release 0.4rc2 ---------------------+------------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: accepted Priority: blocker | Milestone: 0.4 Component: Website | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Comment(by thijs): Download page is fixed, the blog post is also ready, which will be used for the announce mails to lists.pyamf.org. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 6 04:11:56 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 6 04:12:12 2009 Subject: [pyamf-tickets] #422: Add read/write_24bit_uint to util.DataTypeMixIn. Message-ID: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> #422: Add read/write_24bit_uint to util.DataTypeMixIn. ---------------------+------------------------------------------------------ Reporter: nick | Owner: nick Type: defect | Status: new Priority: minor | Milestone: 0.5 Component: Utility | Version: Keywords: | ---------------------+------------------------------------------------------ Not used so much in PyAMF but useful as an all-rounder and to be part of cpyamf -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 6 04:16:18 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 6 04:16:36 2009 Subject: [pyamf-tickets] #423: Add a consume method that will chop the head off the data stream at the current stream position. Message-ID: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> #423: Add a consume method that will chop the head off the data stream at the current stream position. ---------------------+------------------------------------------------------ Reporter: nick | Owner: nick Type: defect | Status: new Priority: minor | Milestone: 0.5 Component: Utility | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ The areas that will be affected: `pyamf.util.StringIOProxy` `cpyamf.util.BufferedByteStream` -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 6 04:17:42 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 6 04:17:57 2009 Subject: [pyamf-tickets] #424: Move IndexedCollection to cpyamf Message-ID: <032.a2f076997e96a30e1e40a8a864c5d2e0@pyamf.org> #424: Move IndexedCollection to cpyamf -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: new Priority: major | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- `pyamf.util.IndexedCollection` is the class used in all reference lookups so should be as fast as possible. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 6 04:49:22 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 6 04:49:46 2009 Subject: [pyamf-tickets] #343: Refactor the test suite to be python implementation independent In-Reply-To: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> References: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> Message-ID: <041.f1ff72c133b822d3cead30a02ba55ba9@pyamf.org> #343: Refactor the test suite to be python implementation independent -------------------------+-------------------------------------------------- Reporter: nick | Owner: thijs Type: enhancement | Status: assigned Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.3.1 Keywords: | -------------------------+-------------------------------------------------- Changes (by nick): * owner: nick => thijs Comment: I downloaded the [http://red5.googlecode.com/svn/flash/trunk/deploy/echo_test.swf latest echo_test] and i could not reproduce this? `HTTP AMF0` `HTTP AMF3` and `mx:RemoteObject` all worked without a hitch using this branch .. Can you double check? -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 6 15:38:45 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 6 15:39:05 2009 Subject: [pyamf-tickets] #425: Policy for Adobe Flash references Message-ID: <033.21b4efa73ec49f726ebe964b76f38d8c@pyamf.org> #425: Policy for Adobe Flash references ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: new Priority: critical | Milestone: 0.5 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Check the [http://www.adobe.com/misc/pdfs/flash_3rd_party_trademark_guidelines_020708.pdf Adobe Flash trademark guidelines] that describe how to refer to the Adobe Flash Player in our documentation and announcements. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 6 17:12:12 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 6 17:12:32 2009 Subject: [pyamf-tickets] #416: Release 0.4rc2 In-Reply-To: <033.fb458379f13bcedeea8fdf3c6d9ac259@pyamf.org> References: <033.fb458379f13bcedeea8fdf3c6d9ac259@pyamf.org> Message-ID: <042.16c8bf5fbed1ab5130e4c1908d063f0f@pyamf.org> #416: Release 0.4rc2 ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: closed Priority: blocker | Milestone: 0.4 Component: Website | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by thijs): * status: accepted => closed * resolution: => fixed Comment: Fixed with r1984 -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 00:07:37 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 00:07:54 2009 Subject: [pyamf-tickets] #426: ElementTree serialized to ObjectProxy, not XML Message-ID: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> #426: ElementTree serialized to ObjectProxy, not XML -----------------------------------------+---------------------------------- Reporter: jhaislip | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.5 Component: Remoting | Version: 0.4 Keywords: ElementTree ObjectProxy XML | -----------------------------------------+---------------------------------- I recently setup pyAMF with mod_python. I wrote test services that return the various datatypes of interest (DateTime, List, Bool, etc). I then accessed those services from a Flex application and saw that the serialization into Flex data types was working (Date, Array, Bool, etc). All of the data types I tested worked as they are supposed to except for one: ElementTree. In my service, I have: {{{ from pyamf.remoting.gateway.wsgi import WSGIGateway import elementtree.ElementTree as ET def getXML(): root = Element("root") SubElement(root, "one") SubElement(root, "two") SubElement(root, "three") SubElement(root, "four") return root # Expose our services: services = { 'service.getXML': getXML } GatewayController = WSGIGateway(services) }}} Here is the Flex: {{{ }}} When I access the service from Flex, it returns an ObjectProxy and not an XML. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 00:13:57 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 00:14:15 2009 Subject: [pyamf-tickets] #426: ElementTree serialized to ObjectProxy, not XML In-Reply-To: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> References: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> Message-ID: <045.33a60ca12c641fb96f58c460b3ed989e@pyamf.org> #426: ElementTree serialized to ObjectProxy, not XML -----------------------------------------+---------------------------------- Reporter: jhaislip | Owner: nick Type: defect | Status: new Priority: critical | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: ElementTree ObjectProxy XML | -----------------------------------------+---------------------------------- Changes (by thijs): * priority: major => critical * milestone: 0.5 => 0.4 Old description: > I recently setup pyAMF with mod_python. I wrote test services that return > the various datatypes of interest (DateTime, List, Bool, etc). I then > accessed those services from a Flex application and saw that the > serialization into Flex data types was working (Date, Array, Bool, etc). > All of the data types I tested worked as > they are supposed to except for one: ElementTree. > > In my service, I have: > > {{{ > from pyamf.remoting.gateway.wsgi import WSGIGateway > import elementtree.ElementTree as ET > > def getXML(): > root = Element("root") > > SubElement(root, "one") > SubElement(root, "two") > SubElement(root, "three") > SubElement(root, "four") > return root > > # Expose our services: > services = { > 'service.getXML': getXML > } > > GatewayController = WSGIGateway(services) > }}} > > Here is the Flex: > > {{{ > horizontalAlign="center" > verticalAlign="middle"> > > endpoint="http://localhost:80/services" destination="service" > result="displayResult(event)" fault="remoteFault(event)"> > > > > > > > > import mx.utils.ObjectUtil; > import mx.rpc.events.ResultEvent; > import mx.rpc.events.FaultEvent; > > private function displayResult(re:ResultEvent): void { > result.text = ObjectUtil.toString(re.result) + "\n"; > } > private function remoteFault(fault:FaultEvent): void { > result.text = ObjectUtil.toString(fault); > } > private function handleGetXML(evt:MouseEvent):void { > remoteObj.getXML() > } > ]]> > > > > }}} > > > When I access the service from Flex, it returns an ObjectProxy and not an > XML. New description: I recently setup pyAMF with mod_python. I wrote test services that return the various datatypes of interest (!DateTime, List, Bool, etc). I then accessed those services from a Flex application and saw that the serialization into Flex data types was working (Date, Array, Bool, etc). All of the data types I tested worked as they are supposed to except for one: !ElementTree. In my service, I have: {{{ #!python from pyamf.remoting.gateway.wsgi import WSGIGateway import elementtree.ElementTree as ET def getXML(): root = Element("root") SubElement(root, "one") SubElement(root, "two") SubElement(root, "three") SubElement(root, "four") return root # Expose our services: services = { 'service.getXML': getXML } GatewayController = WSGIGateway(services) }}} Here is the Flex: {{{ #!xml }}} When I access the service from Flex, it returns an ObjectProxy and not an XML. -- Comment: Moving to [milestone:0.4 milestone 0.4]. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 00:43:29 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 00:43:45 2009 Subject: [pyamf-tickets] #426: ElementTree serialized to ObjectProxy, not XML In-Reply-To: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> References: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> Message-ID: <045.307c9f263a6da4214054b39bd3e438ed@pyamf.org> #426: ElementTree serialized to ObjectProxy, not XML -----------------------------------------+---------------------------------- Reporter: jhaislip | Owner: nick Type: defect | Status: new Priority: critical | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: ElementTree ObjectProxy XML | -----------------------------------------+---------------------------------- Comment(by thijs): It was confirmed (on IRC) that this is working with 0.3.1 and a 0.4/trunk issue only. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 10:08:56 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 10:09:15 2009 Subject: [pyamf-tickets] #427: elementree is not a supported XML lib Message-ID: <032.b36b78413346ea1a06c8aa9cdf9bbdf9@pyamf.org> #427: elementree is not a supported XML lib ---------------------+------------------------------------------------------ Reporter: nick | Owner: nick Type: defect | Status: new Priority: minor | Milestone: 0.4 Component: Utility | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ {{{ !#python >>> import pyamf >>> import xml.etree.ElementTree as ET >>> pyamf.encode(ET.Element('a', foo='bar'), encoding=pyamf.AMF3).getvalue() '\x0b\x1f' }}} Which is correct, however: {{{ >>> import pyamf >>> import elementtree.ElementTree as ET >>> pyamf.encode(ET.Element('a', foo='bar'), encoding=pyamf.AMF3).getvalue() '\n\x0b\x01\rattrib\n\x0b\x01\x07foo\x06\x07bar\x01\x07tag\x06\x03a\x13_children\t\x01\x01\x01' }}} Isn't. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 10:10:15 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 10:10:31 2009 Subject: [pyamf-tickets] #427: elementree is not a supported XML lib In-Reply-To: <032.b36b78413346ea1a06c8aa9cdf9bbdf9@pyamf.org> References: <032.b36b78413346ea1a06c8aa9cdf9bbdf9@pyamf.org> Message-ID: <041.32547d816fab4780fdce03f207337b73@pyamf.org> #427: elementree is not a supported XML lib ---------------------+------------------------------------------------------ Reporter: nick | Owner: nick Type: defect | Status: accepted Priority: minor | Milestone: 0.4 Component: Utility | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Changes (by nick): * status: new => accepted Old description: > {{{ > !#python > >>> import pyamf > >>> import xml.etree.ElementTree as ET > >>> pyamf.encode(ET.Element('a', foo='bar'), > encoding=pyamf.AMF3).getvalue() > '\x0b\x1f' > }}} > > Which is correct, however: > > {{{ > >>> import pyamf > >>> import elementtree.ElementTree as ET > >>> pyamf.encode(ET.Element('a', foo='bar'), > encoding=pyamf.AMF3).getvalue() > '\n\x0b\x01\rattrib\n\x0b\x01\x07foo\x06\x07bar\x01\x07tag\x06\x03a\x13_children\t\x01\x01\x01' > }}} > > Isn't. New description: {{{ #!python >>> import pyamf >>> import xml.etree.ElementTree as ET >>> pyamf.encode(ET.Element('a', foo='bar'), encoding=pyamf.AMF3).getvalue() '\x0b\x1f' }}} Which is correct, however: {{{ #!python >>> import pyamf >>> import elementtree.ElementTree as ET >>> pyamf.encode(ET.Element('a', foo='bar'), encoding=pyamf.AMF3).getvalue() '\n\x0b\x01\rattrib\n\x0b\x01\x07foo\x06\x07bar\x01\x07tag\x06\x03a\x13_children\t\x01\x01\x01' }}} Isn't. -- -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 11:06:04 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 11:06:20 2009 Subject: [pyamf-tickets] #427: elementree is not a supported XML lib In-Reply-To: <032.b36b78413346ea1a06c8aa9cdf9bbdf9@pyamf.org> References: <032.b36b78413346ea1a06c8aa9cdf9bbdf9@pyamf.org> Message-ID: <041.cd4dd29961077ef55760320311ba2479@pyamf.org> #427: elementree is not a supported XML lib ------------------------+--------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: closed Priority: minor | Milestone: 0.4 Component: Utility | Version: 0.4 Resolution: duplicate | Keywords: ------------------------+--------------------------------------------------- Changes (by nick): * status: accepted => closed * resolution: => duplicate Comment: Duplicate of #426. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 11:23:49 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 11:24:05 2009 Subject: [pyamf-tickets] #426: ElementTree serialized to ObjectProxy, not XML In-Reply-To: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> References: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> Message-ID: <045.78a074efe0b927b51bf1e22d85d0e12d@pyamf.org> #426: ElementTree serialized to ObjectProxy, not XML -----------------------------------------+---------------------------------- Reporter: jhaislip | Owner: nick Type: defect | Status: accepted Priority: critical | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: ElementTree ObjectProxy XML | -----------------------------------------+---------------------------------- Changes (by nick): * status: new => accepted Comment: Branching to source:pyamf/branches/etree-checking-426 -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 11:30:59 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 11:31:14 2009 Subject: [pyamf-tickets] #428: Move ubuntu buildslaves Message-ID: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> #428: Move ubuntu buildslaves ---------------------+------------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: new Priority: major | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Currently the BuildBot farm is running buildslaves as well as the buildmaster, but also the website/svn/mailinglist etc. This is causing too much load on the server so it would be a good idea to move those amd64-ubuntu-* slaves to a different server. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 11:53:02 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 11:53:17 2009 Subject: [pyamf-tickets] #428: Move ubuntu buildslaves In-Reply-To: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> References: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> Message-ID: <042.18352e6cc296bc9dc5033365e95caa41@pyamf.org> #428: Move ubuntu buildslaves ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: task | Status: assigned Priority: critical | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by thijs): * owner: thijs => nick * priority: major => critical * status: new => assigned -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 15:49:42 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 15:51:23 2009 Subject: [pyamf-tickets] #426: ElementTree serialized to ObjectProxy, not XML In-Reply-To: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> References: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> Message-ID: <045.47df5c5e069f111456f9a2df1ec8d9c8@pyamf.org> #426: ElementTree serialized to ObjectProxy, not XML ---------------------------------------------------+------------------------ Reporter: jhaislip | Owner: thijs Type: defect | Status: assigned Priority: critical | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: ElementTree, ObjectProxy, XML, review | ---------------------------------------------------+------------------------ Changes (by nick): * keywords: ElementTree ObjectProxy XML => ElementTree, ObjectProxy, XML, review * owner: nick => thijs * status: accepted => assigned Comment: I amended the xml lib initialisation code to check in order for all libraries available and to check for each type when encoding xml elements. When decoding PyAMF will use the first implementation is comes across. This is the order: 1. xml.etree.cElementTree 2. cElementTree 3. xml.etree.ElementTree 4. elementtree.ElementTree Tests have been added to ensure that all libs are compatible. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 16:36:44 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 16:37:03 2009 Subject: [pyamf-tickets] #426: ElementTree serialized to ObjectProxy, not XML In-Reply-To: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> References: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> Message-ID: <045.d1da8caf132e71b04262dfef62cd2848@pyamf.org> #426: ElementTree serialized to ObjectProxy, not XML ---------------------------------------------------+------------------------ Reporter: jhaislip | Owner: nick Type: defect | Status: assigned Priority: critical | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: ElementTree, ObjectProxy, XML, review | ---------------------------------------------------+------------------------ Changes (by thijs): * owner: thijs => nick Comment: The new method needs @since: 0.4 markup. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 17:48:14 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 17:50:14 2009 Subject: [pyamf-tickets] #429: Grab version nr for setuptools from pyamf.__version__ Message-ID: <033.2494d02167f54b117ea00871f6dcefee@pyamf.org> #429: Grab version nr for setuptools from pyamf.__version__ -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: new Priority: minor | Milestone: 0.5 Component: Installer | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- We're currently defining the PyAMF version nr in 2 places: 1. [source:pyamf/trunk/setup.py] 1. [source:pyamf/trunk/pyamf/__init__.py] - {{{__version__}}} Let's import the version nr from option 2 into option 1. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 17:50:07 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 17:51:02 2009 Subject: [pyamf-tickets] #426: ElementTree serialized to ObjectProxy, not XML In-Reply-To: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> References: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> Message-ID: <045.8415a1e0a9c58649076eb01eedbdf69d@pyamf.org> #426: ElementTree serialized to ObjectProxy, not XML ---------------------------------------------------+------------------------ Reporter: jhaislip | Owner: thijs Type: defect | Status: assigned Priority: critical | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: ElementTree, ObjectProxy, XML, review | ---------------------------------------------------+------------------------ Changes (by nick): * owner: nick => thijs Comment: Done. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 18:22:56 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 18:23:13 2009 Subject: [pyamf-tickets] #426: ElementTree serialized to ObjectProxy, not XML In-Reply-To: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> References: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> Message-ID: <045.6321a68d3ce1a3a0da074895f7ed8646@pyamf.org> #426: ElementTree serialized to ObjectProxy, not XML -------------------------------------------+-------------------------------- Reporter: jhaislip | Owner: nick Type: defect | Status: assigned Priority: critical | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: ElementTree, ObjectProxy, XML | -------------------------------------------+-------------------------------- Changes (by thijs): * keywords: ElementTree, ObjectProxy, XML, review => ElementTree, ObjectProxy, XML * owner: thijs => nick Comment: If it works with the latest EchoTest, and passes the tests on feisley's buildslaves, then it can be merged. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 18:24:28 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 18:24:45 2009 Subject: [pyamf-tickets] #356: Remove fpconst dependency for Windows with Python 2.6 In-Reply-To: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> References: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> Message-ID: <042.ee57750c683040d210db08778272a980@pyamf.org> #356: Remove fpconst dependency for Windows with Python 2.6 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: accepted Priority: major | Milestone: 0.5 Component: Installer | Version: 0.3.1 Keywords: | -------------------------+-------------------------------------------------- Changes (by nick): * status: new => accepted * component: Decoder => Installer Comment: I suggest instead of adding lots of `if` statements for edge cases such as this we should only require the fpconst lib if we detect that floats are broken on the platform from within `setup.py` -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 18:44:40 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 18:45:00 2009 Subject: [pyamf-tickets] #356: Remove fpconst dependency for Windows with Python 2.6 In-Reply-To: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> References: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> Message-ID: <042.d9c2f1ceb268193916ed44f951956b78@pyamf.org> #356: Remove fpconst dependency for Windows with Python 2.6 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: accepted Priority: major | Milestone: 0.5 Component: Installer | Version: 0.3.1 Keywords: | -------------------------+-------------------------------------------------- Comment(by nick): Branching to source:pyamf/branches/broken-floats-356 -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 18:46:15 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 18:46:34 2009 Subject: [pyamf-tickets] #356: Remove fpconst dependency for Windows with Python 2.6 In-Reply-To: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> References: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> Message-ID: <042.87dcd541a61a337a924d1ae535138b25@pyamf.org> #356: Remove fpconst dependency for Windows with Python 2.6 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: thijs Type: enhancement | Status: assigned Priority: major | Milestone: 0.5 Component: Installer | Version: 0.3.1 Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * keywords: => review * status: accepted => assigned * owner: nick => thijs Comment: Ready for review in r1991. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 19:37:39 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 19:37:59 2009 Subject: [pyamf-tickets] #426: ElementTree serialized to ObjectProxy, not XML In-Reply-To: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> References: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> Message-ID: <045.e0bf2d02872b5237e298ea7feee09d35@pyamf.org> #426: ElementTree serialized to ObjectProxy, not XML -----------------------+---------------------------------------------------- Reporter: jhaislip | Owner: nick Type: defect | Status: closed Priority: critical | Milestone: 0.4 Component: Remoting | Version: 0.4 Resolution: fixed | Keywords: ElementTree, ObjectProxy, XML -----------------------+---------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Checked EchoTest and slaves - all good. I have merged to trunk in r1992 and to source:pyamf/branches/release-0.4 in r1993. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 20:32:22 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 20:32:40 2009 Subject: [pyamf-tickets] #390: encoding/decoding dates prior to 1970 with Windows In-Reply-To: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> References: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> Message-ID: <043.591bb7bd1883ec35157566c6b0a61b63@pyamf.org> #390: encoding/decoding dates prior to 1970 with Windows ---------------------+------------------------------------------------------ Reporter: arman0 | Owner: thijs Type: defect | Status: assigned Priority: major | Milestone: 0.5 Component: Decoder | Version: 0.3.1 Keywords: review | ---------------------+------------------------------------------------------ Changes (by nick): * keywords: => review * owner: nick => thijs Comment: echo test and slaves look good. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 21:11:05 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 21:11:29 2009 Subject: [pyamf-tickets] #430: Release 0.4rc3 Message-ID: <033.c022fd46085140a368c91facf2af7613@pyamf.org> #430: Release 0.4rc3 ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: new Priority: blocker | Milestone: 0.4 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ We're going to have another Release Candidate, hopefully the last one. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 21:12:33 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 21:12:52 2009 Subject: [pyamf-tickets] #356: Remove fpconst dependency for Windows with Python 2.6 In-Reply-To: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> References: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> Message-ID: <042.415b00248990afef518014b4e60ced3b@pyamf.org> #356: Remove fpconst dependency for Windows with Python 2.6 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: thijs Type: enhancement | Status: accepted Priority: major | Milestone: 0.4 Component: Installer | Version: 0.3.1 Keywords: review | -------------------------+-------------------------------------------------- Changes (by thijs): * status: assigned => accepted * milestone: 0.5 => 0.4 -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 21:13:10 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 21:13:28 2009 Subject: [pyamf-tickets] #390: encoding/decoding dates prior to 1970 with Windows In-Reply-To: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> References: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> Message-ID: <043.b46a10182e8f4b9e7235474624d437eb@pyamf.org> #390: encoding/decoding dates prior to 1970 with Windows ---------------------+------------------------------------------------------ Reporter: arman0 | Owner: thijs Type: defect | Status: accepted Priority: major | Milestone: 0.4 Component: Decoder | Version: 0.3.1 Keywords: review | ---------------------+------------------------------------------------------ Changes (by thijs): * status: assigned => accepted * milestone: 0.5 => 0.4 -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 21:17:30 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 21:18:00 2009 Subject: [pyamf-tickets] #392: exceptions.AssertionError: != In-Reply-To: <033.91fa92ea990e28461d1611c72a5e4318@pyamf.org> References: <033.91fa92ea990e28461d1611c72a5e4318@pyamf.org> Message-ID: <042.a0c1274a30fc8eb819b0479068561a6b@pyamf.org> #392: exceptions.AssertionError: != ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: reopened Priority: major | Milestone: 0.5 Component: Testing | Version: 0.4 Resolution: | Keywords: ----------------------+----------------------------------------------------- Changes (by thijs): * status: closed => reopened * resolution: fixed => * milestone: 0.4 => 0.5 Comment: Looks like it's [http://buildbot.pyamf.org/builders/x86-winxp- py26/builds/9/steps/python2.6-test_4/logs/stdio back] :-/ -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 21:18:57 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 21:19:16 2009 Subject: [pyamf-tickets] #402: fpconst should be installed on all win32 buildslaves by default In-Reply-To: <032.acab1dbf9774ae292106736d363e870d@pyamf.org> References: <032.acab1dbf9774ae292106736d363e870d@pyamf.org> Message-ID: <041.68da6380555221c23fc9488262b7146b@pyamf.org> #402: fpconst should be installed on all win32 buildslaves by default ----------------------+----------------------------------------------------- Reporter: nick | Owner: feisley Type: defect | Status: reopened Priority: major | Milestone: 0.4 Component: Testing | Version: 0.3.1 Resolution: | Keywords: ----------------------+----------------------------------------------------- Changes (by thijs): * status: closed => reopened * resolution: fixed => * component: Remoting => Testing Comment: It's [http://buildbot.pyamf.org/builders/x86-winxp- py26/builds/9/steps/python2.6-test_4/logs/stdio back]. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 21:41:34 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 21:49:20 2009 Subject: [pyamf-tickets] #356: Remove fpconst dependency for Windows with Python 2.6 In-Reply-To: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> References: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> Message-ID: <042.0a2ee26d7b89bd8dbd771179f5fbc7d4@pyamf.org> #356: Remove fpconst dependency for Windows with Python 2.6 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: assigned Priority: major | Milestone: 0.4 Component: Installer | Version: 0.3.1 Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * keywords: review => * owner: thijs => nick * status: accepted => assigned Comment: Looks like it's [http://buildbot.pyamf.org/builders/x86-winxp- py26/builds/11/steps/python2.6-test/logs/stdio working], please merge. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 21:47:27 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 21:49:44 2009 Subject: [pyamf-tickets] #402: fpconst should be installed on the win32 buildslaves by default (was: fpconst should be installed on all win32 buildslaves by default) In-Reply-To: <032.acab1dbf9774ae292106736d363e870d@pyamf.org> References: <032.acab1dbf9774ae292106736d363e870d@pyamf.org> Message-ID: <041.5e9a85d27d5680849a4b959891f44cbd@pyamf.org> #402: fpconst should be installed on the win32 buildslaves by default ----------------------+----------------------------------------------------- Reporter: nick | Owner: feisley Type: defect | Status: closed Priority: major | Milestone: 0.4 Component: Testing | Version: 0.3.1 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by thijs): * status: reopened => closed * resolution: => fixed Old description: > Otherwise we get failed builds like > [http://buildbot.pyamf.org/builders/x86-win2003-py25/builds/100/steps/python2.5-test/logs/stdio > this] New description: Otherwise we get failed builds like [http://buildbot.pyamf.org/builders/x86-win2003-py25/builds/100/steps/python2.5-test/logs/stdio this]. It shouldn't be installed on the Python 2.6 slave because that one doesn't have any problems with floats. -- Comment: #356 fixed this one. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 22:01:59 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 22:14:36 2009 Subject: [pyamf-tickets] #356: Remove fpconst dependency for Windows with Python 2.6 In-Reply-To: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> References: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> Message-ID: <042.d36c1c21a2baf60158f659cd522f843d@pyamf.org> #356: Remove fpconst dependency for Windows with Python 2.6 --------------------------+------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: closed Priority: major | Milestone: 0.4 Component: Installer | Version: 0.3.1 Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Merged to source:pyamf/branches/release-0.4 and source:pyamf/trunk -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 22:52:08 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 22:58:52 2009 Subject: [pyamf-tickets] #356: Remove fpconst dependency for Windows with Python 2.6 In-Reply-To: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> References: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> Message-ID: <042.9149fa344e0e17691ff3b814188de34a@pyamf.org> #356: Remove fpconst dependency for Windows with Python 2.6 --------------------------+------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: reopened Priority: major | Milestone: 0.4 Component: Installer | Version: 0.3.1 Resolution: | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: closed => reopened * resolution: fixed => Comment: win32-python2.4 slave is failing .. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 23:11:31 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 7 23:28:25 2009 Subject: [pyamf-tickets] #356: Remove fpconst dependency for Windows with Python 2.6 In-Reply-To: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> References: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> Message-ID: <042.377984d50f4cc0676e3fc47b58bd8316@pyamf.org> #356: Remove fpconst dependency for Windows with Python 2.6 --------------------------+------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: closed Priority: major | Milestone: 0.4 Component: Installer | Version: 0.3.1 Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: reopened => closed * resolution: => fixed Comment: Fixed in r2005 -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 8 10:53:29 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 8 10:53:46 2009 Subject: [pyamf-tickets] #377: Porting C-Extension Module to Python 3.0 In-Reply-To: <033.89ff9943ac068869772f5a3137a306d4@pyamf.org> References: <033.89ff9943ac068869772f5a3137a306d4@pyamf.org> Message-ID: <042.e70dbd15b8f24c003b8dd2d0494e4bf8@pyamf.org> #377: Porting C-Extension Module to Python 3.0 --------------------------+------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: closed Priority: minor | Milestone: Python 3000 Component: C-Extension | Version: 0.4 Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Cython is now in operation - Py3k taken care of. -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 8 11:01:04 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 8 11:01:25 2009 Subject: [pyamf-tickets] #252: Add egg export feature to package script In-Reply-To: <033.71bde58a1920b3944fc7c735254710e3@pyamf.org> References: <033.71bde58a1920b3944fc7c735254710e3@pyamf.org> Message-ID: <042.d8e08c1ce8798cdcbeabcff6e042e1e2@pyamf.org> #252: Add egg export feature to package script -----------------------+---------------------------------------------------- Reporter: thijs | Owner: nick Type: task | Status: new Priority: minor | Milestone: At some point Component: Installer | Version: 0.3 Keywords: | -----------------------+---------------------------------------------------- Comment(by nick): The eggs are now platform dependant (since the introduction of cpyamf) so using the package script is a not an option. I recommend integrating the egg building into the buildslaves which would upload the result to the master (roughly 220K for each egg). -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 8 17:23:31 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 8 17:23:49 2009 Subject: [pyamf-tickets] #343: Refactor the test suite to be python implementation independent In-Reply-To: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> References: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> Message-ID: <041.20b6ce2c91e390bb6c87283478210a48@pyamf.org> #343: Refactor the test suite to be python implementation independent -------------------------+-------------------------------------------------- Reporter: nick | Owner: thijs Type: enhancement | Status: assigned Priority: minor | Milestone: 0.4 Component: Testing | Version: 0.3.1 Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * keywords: => review * milestone: 0.5 => 0.4 -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 8 18:47:51 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 8 18:48:20 2009 Subject: [pyamf-tickets] #428: Move ubuntu buildslaves In-Reply-To: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> References: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> Message-ID: <042.35be6c1681f67962e2325715f5fbc58f@pyamf.org> #428: Move ubuntu buildslaves ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: task | Status: assigned Priority: critical | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Comment(by nick): Ubuntu build slaves have now been moved to callisto (thanks to Dark Horse Networks for providing hardware/support) - however i am getting this issue: http://buildbot.pyamf.org/builders/ubuntu-py24/builds/6/steps/svn- update/logs/stdio I can create the build dir and then the next build will run fine but then the dir is deleted and the error will appear in the next build. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 10 21:14:59 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 10 21:15:17 2009 Subject: [pyamf-tickets] #428: Move ubuntu buildslaves In-Reply-To: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> References: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> Message-ID: <042.c68496e8672843d5ffaa8d097ed8c5ee@pyamf.org> #428: Move ubuntu buildslaves ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: assigned Priority: critical | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: review | ----------------------+----------------------------------------------------- Changes (by nick): * keywords: => review * owner: nick => thijs Comment: The error has now been sorted - see http://buildbot.net/trac/ticket/284 Django & Twisted installed on all slaves. I have also created 4 debian64 python23-6 slaves to cover that distribution also. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 10 21:32:51 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 10 21:33:42 2009 Subject: [pyamf-tickets] #431: Don't fire a build on every commit to branches Message-ID: <032.932689b90dc0786c1d0e18318d92c1e0@pyamf.org> #431: Don't fire a build on every commit to branches -------------------------+-------------------------------------------------- Reporter: nick | Owner: thijs Type: enhancement | Status: new Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Lots of commits are thrown into the branches - including debug stuff. When a ticket is ready for merging a manual build should be fired by the reviewer and an auto build should be fired when merging to trunk. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 10 21:38:12 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 10 21:38:51 2009 Subject: [pyamf-tickets] #390: encoding/decoding dates prior to 1970 with Windows In-Reply-To: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> References: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> Message-ID: <043.0ec27cea93b0cc80a61e03c19d368491@pyamf.org> #390: encoding/decoding dates prior to 1970 with Windows ---------------------+------------------------------------------------------ Reporter: arman0 | Owner: thijs Type: defect | Status: accepted Priority: major | Milestone: 0.4 Component: Decoder | Version: 0.3.1 Keywords: review | ---------------------+------------------------------------------------------ Comment(by nick): For reference: source:pyamf/branches/negative-timestamp-390 -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 10 21:42:27 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 10 21:43:13 2009 Subject: [pyamf-tickets] #432: Only run PyFlakes on the pyamf tree Message-ID: <032.1ff1eecc791e299b7f6eec5aa9d728f7@pyamf.org> #432: Only run PyFlakes on the pyamf tree ---------------------+------------------------------------------------------ Reporter: nick | Owner: thijs Type: task | Status: new Priority: minor | Milestone: Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Otherwise we get false positives such as: http://buildbot.pyamf.org/builders/ubuntu- py24/builds/10/steps/pyflakes/logs/stdio -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 10 21:44:46 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 10 21:45:02 2009 Subject: [pyamf-tickets] #433: Only run PyFlakes on the pyamf tree Message-ID: <032.8d444565c76d4961e1bbbd9edec8ef74@pyamf.org> #433: Only run PyFlakes on the pyamf tree ---------------------+------------------------------------------------------ Reporter: nick | Owner: thijs Type: task | Status: new Priority: minor | Milestone: Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Otherwise we get false positives such as: http://buildbot.pyamf.org/builders/ubuntu- py24/builds/10/steps/pyflakes/logs/stdio -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 10 21:46:24 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 10 21:46:40 2009 Subject: [pyamf-tickets] #433: Only run PyFlakes on the pyamf tree In-Reply-To: <032.8d444565c76d4961e1bbbd9edec8ef74@pyamf.org> References: <032.8d444565c76d4961e1bbbd9edec8ef74@pyamf.org> Message-ID: <041.b575424a43f6e4443e9e33b27fb179d9@pyamf.org> #433: Only run PyFlakes on the pyamf tree ------------------------+--------------------------------------------------- Reporter: nick | Owner: thijs Type: task | Status: closed Priority: minor | Milestone: Component: Testing | Version: 0.4 Resolution: duplicate | Keywords: ------------------------+--------------------------------------------------- Changes (by nick): * status: new => closed * resolution: => duplicate Comment: Duplicate of #432. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 10 21:49:36 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 10 21:49:53 2009 Subject: [pyamf-tickets] #390: encoding/decoding dates prior to 1970 with Windows In-Reply-To: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> References: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> Message-ID: <043.a1899bfbe3015337d3ef8034f9fdb0ad@pyamf.org> #390: encoding/decoding dates prior to 1970 with Windows ---------------------+------------------------------------------------------ Reporter: arman0 | Owner: nick Type: defect | Status: assigned Priority: major | Milestone: 0.4 Component: Decoder | Version: 0.3.1 Keywords: | ---------------------+------------------------------------------------------ Changes (by thijs): * keywords: review => * status: accepted => assigned * owner: thijs => nick Comment: Replying to [comment:7 nick]: > echo test and slaves look good. In that case merge. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 10 22:31:34 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 10 22:33:02 2009 Subject: [pyamf-tickets] #390: encoding/decoding dates prior to 1970 with Windows In-Reply-To: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> References: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> Message-ID: <043.10f41771263ab39ffde071fccbe31e8a@pyamf.org> #390: encoding/decoding dates prior to 1970 with Windows ----------------------+----------------------------------------------------- Reporter: arman0 | Owner: nick Type: defect | Status: closed Priority: major | Milestone: 0.4 Component: Decoder | Version: 0.3.1 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 11 05:06:20 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 11 05:06:42 2009 Subject: [pyamf-tickets] #392: exceptions.AssertionError: != In-Reply-To: <033.91fa92ea990e28461d1611c72a5e4318@pyamf.org> References: <033.91fa92ea990e28461d1611c72a5e4318@pyamf.org> Message-ID: <042.6dbcc9ab3d9dac586666c512ab569839@pyamf.org> #392: exceptions.AssertionError: != ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: closed Priority: major | Milestone: 0.5 Component: Testing | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by nick): * status: reopened => closed * resolution: => fixed Comment: Fixed. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 11 05:07:57 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 11 05:08:16 2009 Subject: [pyamf-tickets] #428: Move ubuntu buildslaves In-Reply-To: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> References: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> Message-ID: <042.908b8fb93390494abce65e3dc735c7ef@pyamf.org> #428: Move ubuntu buildslaves ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: assigned Priority: critical | Milestone: 0.4 Component: Website | Version: 0.4 Keywords: review | ----------------------+----------------------------------------------------- Changes (by nick): * milestone: 0.5 => 0.4 -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 11 17:06:45 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 11 17:07:02 2009 Subject: [pyamf-tickets] #343: Refactor the test suite to be python implementation independent In-Reply-To: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> References: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> Message-ID: <041.c857f880b4d703d9d728cc0ba09b76c3@pyamf.org> #343: Refactor the test suite to be python implementation independent -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: assigned Priority: minor | Milestone: 0.4 Component: Testing | Version: 0.3.1 Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * keywords: review => * owner: thijs => nick Comment: Tested with ParseDump and EchoTest and looks good now, please merge. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 11 17:09:19 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 11 17:09:39 2009 Subject: [pyamf-tickets] #428: Move ubuntu buildslaves In-Reply-To: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> References: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> Message-ID: <042.b7ec31b700382f993558314f8c24ea9a@pyamf.org> #428: Move ubuntu buildslaves -----------------------+---------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: closed Priority: critical | Milestone: 0.4 Component: Website | Version: 0.4 Resolution: fixed | Keywords: -----------------------+---------------------------------------------------- Changes (by thijs): * keywords: review => * status: assigned => closed * resolution: => fixed Comment: Awesome, good stuff! -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 11 17:29:29 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 11 17:31:08 2009 Subject: [pyamf-tickets] #343: Refactor the test suite to be python implementation independent In-Reply-To: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> References: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> Message-ID: <041.605f3c2a4aac3ad62511fb6deec55cd6@pyamf.org> #343: Refactor the test suite to be python implementation independent --------------------------+------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: closed Priority: minor | Milestone: 0.4 Component: Testing | Version: 0.3.1 Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 11 17:34:22 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 11 17:35:14 2009 Subject: [pyamf-tickets] #434: need twisted client API using defer Message-ID: <035.985b1d3065feb21a2b37015ef0e62ae8@pyamf.org> #434: need twisted client API using defer -------------------------+-------------------------------------------------- Reporter: cassidy | Owner: nick Type: enhancement | Status: new Priority: major | Milestone: 0.5 Component: Client | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- I need a client side API using twisted's defer (for async method calls) but didn't find one in existing API. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 11 19:36:36 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 11 19:36:51 2009 Subject: [pyamf-tickets] #435: Return XML instead of XMLDocument Message-ID: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> #435: Return XML instead of XMLDocument ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- When I create a server that returns elementtree data, and request it with a AMF3 Flex client, it's being returned as flash.xml.XMLDocument data instead of an toplevel XML instance. See attached test files that demonstrate the problem. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 11 19:55:24 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 11 19:55:42 2009 Subject: [pyamf-tickets] #269: Issues with PyAMF and Jython In-Reply-To: <033.e52e403024bdb47ab854aeb6669eb8cc@pyamf.org> References: <033.e52e403024bdb47ab854aeb6669eb8cc@pyamf.org> Message-ID: <042.02a6330da434563d73cc6c6c45ef8723@pyamf.org> #269: Issues with PyAMF and Jython -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: accepted Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.3 Keywords: | -------------------------+-------------------------------------------------- Comment(by thijs): Blocked by #353 and http://bugs.jython.org/issue1227 -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 11 19:59:37 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 11 19:59:53 2009 Subject: [pyamf-tickets] #420: Create example that uses the SQLAlchemy Adapter In-Reply-To: <033.50980369e7f89a7c2776b18e6efa6bcf@pyamf.org> References: <033.50980369e7f89a7c2776b18e6efa6bcf@pyamf.org> Message-ID: <042.67549848ecabd94cff18d17de9862b47@pyamf.org> #420: Create example that uses the SQLAlchemy Adapter ----------------------+----------------------------------------------------- Reporter: thijs | Owner: dthompso Type: task | Status: assigned Priority: major | Milestone: 0.5 Component: Examples | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by thijs): * owner: thijs => dthompso * status: new => assigned Comment: See [source:examples/branches/sqlalchemy_examples_420] -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 12 23:57:35 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 12 23:57:58 2009 Subject: [pyamf-tickets] #422: Add read/write_24bit_uint to util.DataTypeMixIn. In-Reply-To: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> References: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> Message-ID: <041.44fe8f46722ed1981742e7d5c681071c@pyamf.org> #422: Add read/write_24bit_uint to util.DataTypeMixIn. -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: accepted Priority: minor | Milestone: 0.4 Component: Utility | Version: Keywords: | -------------------------+-------------------------------------------------- Changes (by nick): * status: new => accepted * type: defect => enhancement * milestone: 0.5 => 0.4 -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 00:00:16 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 00:01:56 2009 Subject: [pyamf-tickets] #422: Add read/write_24bit_uint to util.DataTypeMixIn. In-Reply-To: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> References: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> Message-ID: <041.4356e386cc13f945b62c2170de752667@pyamf.org> #422: Add read/write_24bit_uint to util.DataTypeMixIn. -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: accepted Priority: minor | Milestone: 0.4 Component: Utility | Version: Keywords: | -------------------------+-------------------------------------------------- Comment(by nick): Branching to source:pyamf/branches/24int-422 -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 00:03:50 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 00:08:34 2009 Subject: [pyamf-tickets] #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. Message-ID: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- I'm working on it. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 00:23:19 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 00:23:35 2009 Subject: [pyamf-tickets] #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. In-Reply-To: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> References: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> Message-ID: <045.dda40049ad696a1b21b99e98abbd4270@pyamf.org> #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: dthompso Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by nick): * owner: nick => dthompso * priority: major => blocker * status: new => assigned -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 02:44:30 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 02:44:50 2009 Subject: [pyamf-tickets] #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. In-Reply-To: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> References: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> Message-ID: <045.590a59d74fbba76380b1ed8a6006a92e@pyamf.org> #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: dthompso Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Comment(by dthompso): My fix in 'branches/sa_0.5.0-436' is ready for review. I had some pending improvements I threw in there too. The change to the 'is_class_sa_mapped' function fixed the problem with SA 0.5.0, all the other changes are improvements. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 03:07:22 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 03:07:39 2009 Subject: [pyamf-tickets] #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. In-Reply-To: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> References: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> Message-ID: <045.c6b991921742b63e5a96ee1b40f54f86@pyamf.org> #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: dthompso Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Comment(by nick): Generally looking good. Some comments: {{{ #!python ['_sa_class_manager', '_sa_adapter', '_sa_appender', '_sa_instrumented', '_sa_iterator', '_sa_remover', '_sa_initiator'] }}} are all extra excluded attributes. Are these necessary - especially the last 5? Shouldn't {{{ #!python pyamf.add_type(collections.InstrumentedList, util.to_list) pyamf.add_type(collections.InstrumentedDict, util.to_dict) pyamf.add_type(collections.InstrumentedSet, util.to_set) }}} cover these most of these cases? I haven't delved too deep into SA's behaviour so I could be/probably am missing something .. Tests are required for the `applyAttributes` behaviour. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 06:07:10 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 06:07:30 2009 Subject: [pyamf-tickets] #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. In-Reply-To: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> References: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> Message-ID: <045.f9b5a3a642deac1c0b017dba8212596c@pyamf.org> #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: dthompso Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Comment(by dthompso): I'm not sure if we need '_sa_class_manager' or not, I just saw that one sitting around. The other extra attributes are used by SA for custom collections. They hold the information needed by SA to use a custom class that does not inherit from one of the 3 Instrumented... classes as if it were a collection class. See here for more info: [http://www.sqlalchemy.org/docs/05/mappers.html#custom-collection- implementations] We have one important custom collection in our code base, but I'm not sure how commonly other people use them. I changed the existing test 'test_lazy_load_attributes' to test for the new behavior (lazy-loaded attributes should not be in __dict__ even if they were set in __init__). -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 18:59:42 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 18:59:59 2009 Subject: [pyamf-tickets] #437: Move Jython buildslave to different server Message-ID: <033.f16137b48b0e77b18c75dc4812cf1203@pyamf.org> #437: Move Jython buildslave to different server ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: task | Status: new Priority: major | Milestone: 0.5 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ The Jython buildslave on the main PyAMF webserver is slowing down the site severely, so it should moved to a different machine. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 19:14:38 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 19:14:58 2009 Subject: [pyamf-tickets] #422: Add read/write_24bit_uint to util.DataTypeMixIn. In-Reply-To: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> References: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> Message-ID: <041.9cd8fdad8a4b7ca924a280b85474a403@pyamf.org> #422: Add read/write_24bit_uint to util.DataTypeMixIn. -------------------------+-------------------------------------------------- Reporter: nick | Owner: thijs Type: enhancement | Status: assigned Priority: minor | Milestone: 0.4 Component: Utility | Version: Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * keywords: => review * status: accepted => assigned * owner: nick => thijs -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 19:16:46 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 19:17:03 2009 Subject: [pyamf-tickets] #438: Setup PyAMF rsync backup Message-ID: <033.4bccdfb705c5fd749ecc83f062fdf762@pyamf.org> #438: Setup PyAMF rsync backup ----------------------+----------------------------------------------------- Reporter: thijs | Owner: feisley Type: task | Status: new Priority: critical | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- We need to backup the PyAMF site and resources every night and setup mirrors. We have several volunteers for this, but feisley is the main man to get this going. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 19:21:09 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 19:21:30 2009 Subject: [pyamf-tickets] #423: Add a consume method that will chop the head off the data stream at the current stream position. In-Reply-To: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> References: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> Message-ID: <041.bb5d32727da575608c4fbbf0ca93bc63@pyamf.org> #423: Add a consume method that will chop the head off the data stream at the current stream position. -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: accepted Priority: minor | Milestone: 0.5 Component: Utility | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by nick): * status: new => accepted * type: defect => enhancement Comment: Branching to source:pyamf/branches/util-consume-423 -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 19:21:50 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 19:22:13 2009 Subject: [pyamf-tickets] #439: Get rid of draft background image in source browser Message-ID: <033.83aa80941e9aaad9b930755c2e94973f@pyamf.org> #439: Get rid of draft background image in source browser ---------------------+------------------------------------------------------ Reporter: thijs | Owner: thijs Type: defect | Status: new Priority: minor | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ The source browser in Trac uses a 'draft' background image for some files like [source:pyamf/trunk/cpyamf/amf3.pyx]. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 19:38:21 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 19:38:58 2009 Subject: [pyamf-tickets] #423: Add a consume method that will chop the head off the data stream at the current stream position. In-Reply-To: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> References: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> Message-ID: <041.0e9bdefa8b62734531ffcd0303be03ee@pyamf.org> #423: Add a consume method that will chop the head off the data stream at the current stream position. -------------------------+-------------------------------------------------- Reporter: nick | Owner: thijs Type: enhancement | Status: assigned Priority: minor | Milestone: 0.5 Component: Utility | Version: 0.4 Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * keywords: => review * owner: nick => thijs * status: accepted => assigned -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 20:16:30 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 20:16:47 2009 Subject: [pyamf-tickets] #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. In-Reply-To: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> References: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> Message-ID: <045.905b02b28be08e43b65b0e552a44ca54@pyamf.org> #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: dthompso Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Comment(by dthompso): I made another modification to ensure that decoded objects can be merged correctly. All tests pass with SA 0.5.0 and SA 0.4.8. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 20:56:35 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 20:56:51 2009 Subject: [pyamf-tickets] #423: Add a consume method that will chop the head off the data stream at the current stream position. In-Reply-To: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> References: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> Message-ID: <041.6fac308da64c2f9f2c458953eeac7288@pyamf.org> #423: Add a consume method that will chop the head off the data stream at the current stream position. -------------------------+-------------------------------------------------- Reporter: nick | Owner: thijs Type: enhancement | Status: assigned Priority: minor | Milestone: 0.4 Component: Utility | Version: 0.4 Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * milestone: 0.5 => 0.4 -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 21:05:46 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 21:06:07 2009 Subject: [pyamf-tickets] #422: Add read/write_24bit_uint to util.DataTypeMixIn. In-Reply-To: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> References: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> Message-ID: <041.38b6b71cb04c60aaff7c2219c8e46e10@pyamf.org> #422: Add read/write_24bit_uint to util.DataTypeMixIn. -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: assigned Priority: minor | Milestone: 0.4 Component: Utility | Version: Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * keywords: review => * owner: thijs => nick Comment: Unit tests, EchoTest and ParseDump succeed. Please merge after adding {{{@rtype}}} and {{{@return}}} markup for the new methods, and adding a changelog entry. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 21:15:29 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 21:15:52 2009 Subject: [pyamf-tickets] #440: epydoc signatures should be added to all util.StringIOProxy, util.DataTypeMixIn and util.BufferedByteStream classes Message-ID: <032.f9b631ce7a6fb9fe1c72c9ea2d6738a7@pyamf.org> #440: epydoc signatures should be added to all util.StringIOProxy, util.DataTypeMixIn and util.BufferedByteStream classes ---------------------------+------------------------------------------------ Reporter: nick | Owner: thijs Type: defect | Status: new Priority: minor | Milestone: 0.5 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 21:17:40 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 21:18:01 2009 Subject: [pyamf-tickets] #423: Add a consume method that will chop the head off the data stream at the current stream position. In-Reply-To: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> References: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> Message-ID: <041.9d868d003d7a6c6550f81839034f3da3@pyamf.org> #423: Add a consume method that will chop the head off the data stream at the current stream position. -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: assigned Priority: minor | Milestone: 0.4 Component: Utility | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * keywords: review => * owner: thijs => nick Comment: Unit tests, EchoTest and ParseDump succeed. After replacing {{{`tell()`}}} with {{{C{tell()}}}}, duplicating the {{{consume}}} docs into util.pyx, and adding a changelog entry it can be merged. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 21:25:22 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 21:25:41 2009 Subject: [pyamf-tickets] #422: Add read/write_24bit_uint to util.DataTypeMixIn. In-Reply-To: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> References: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> Message-ID: <041.906bcf1bb12e66c6b6893c5c54c0afd9@pyamf.org> #422: Add read/write_24bit_uint to util.DataTypeMixIn. --------------------------+------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: closed Priority: minor | Milestone: 0.4 Component: Utility | Version: Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: `rtype` and `return` signatures have been given their own ticket #440. Merged to source:pyamf/branches/release-0.4 in r2041 -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 21:28:46 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 21:29:03 2009 Subject: [pyamf-tickets] #435: Return XML instead of XMLDocument In-Reply-To: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> References: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> Message-ID: <042.32ac72c35579c6a92cbfbbff0908ab00@pyamf.org> #435: Return XML instead of XMLDocument ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.5 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by thijs): * milestone: 0.4 => 0.5 -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 21:36:04 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 21:36:22 2009 Subject: [pyamf-tickets] #423: Add a consume method that will chop the head off the data stream at the current stream position. In-Reply-To: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> References: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> Message-ID: <041.73ee26f72bd1d6bd97f1e59c4dd14177@pyamf.org> #423: Add a consume method that will chop the head off the data stream at the current stream position. --------------------------+------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: closed Priority: minor | Milestone: 0.4 Component: Utility | Version: 0.4 Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Merged to source:pyamf/branches/release-0.4 in r2043. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 21:39:42 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 21:39:59 2009 Subject: [pyamf-tickets] #432: Only run PyFlakes on the pyamf tree In-Reply-To: <032.1ff1eecc791e299b7f6eec5aa9d728f7@pyamf.org> References: <032.1ff1eecc791e299b7f6eec5aa9d728f7@pyamf.org> Message-ID: <041.0a51fe55f1b052500e75326994ed0297@pyamf.org> #432: Only run PyFlakes on the pyamf tree ---------------------+------------------------------------------------------ Reporter: nick | Owner: thijs Type: task | Status: accepted Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Changes (by thijs): * status: new => accepted * milestone: => 0.5 -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 22:12:11 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 22:12:27 2009 Subject: [pyamf-tickets] #432: Only run PyFlakes on the pyamf tree In-Reply-To: <032.1ff1eecc791e299b7f6eec5aa9d728f7@pyamf.org> References: <032.1ff1eecc791e299b7f6eec5aa9d728f7@pyamf.org> Message-ID: <041.cdb96f026a7db6640e61a0595c63c964@pyamf.org> #432: Only run PyFlakes on the pyamf tree ----------------------+----------------------------------------------------- Reporter: nick | Owner: thijs Type: task | Status: closed Priority: minor | Milestone: 0.4 Component: Testing | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by thijs): * status: accepted => closed * resolution: => fixed * milestone: 0.5 => 0.4 Comment: Fixed with r2045 -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 22:24:56 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 22:25:17 2009 Subject: [pyamf-tickets] #440: epydoc signatures should be added to all util.StringIOProxy, util.DataTypeMixIn and util.BufferedByteStream classes In-Reply-To: <032.f9b631ce7a6fb9fe1c72c9ea2d6738a7@pyamf.org> References: <032.f9b631ce7a6fb9fe1c72c9ea2d6738a7@pyamf.org> Message-ID: <041.7487abed9bcae48fe0c74a098d1b2c38@pyamf.org> #440: epydoc signatures should be added to all util.StringIOProxy, util.DataTypeMixIn and util.BufferedByteStream classes ---------------------------+------------------------------------------------ Reporter: nick | Owner: thijs Type: defect | Status: new Priority: minor | Milestone: 0.5 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Comment(by thijs): I ran the epydoc check command on the trunk, results below: {{{ $ epydoc --check pyamf/util/ Warning: Undocumented: - pyamf.util.BufferedByteStream.__add__() - pyamf.util.DataTypeMixIn.ENDIAN_BIG - pyamf.util.DataTypeMixIn.ENDIAN_LITTLE - pyamf.util.DataTypeMixIn.ENDIAN_NATIVE - pyamf.util.DataTypeMixIn.ENDIAN_NETWORK - pyamf.util.DataTypeMixIn.endian - pyamf.util.IndexedCollection.__contains__() - pyamf.util.IndexedCollection.__eq__() - pyamf.util.IndexedCollection.__getitem__() - pyamf.util.IndexedCollection.__init__() - pyamf.util.IndexedCollection.__iter__() - pyamf.util.IndexedCollection.__len__() - pyamf.util.IndexedCollection.append() - pyamf.util.IndexedCollection.clear() - pyamf.util.IndexedCollection.getByReference() - pyamf.util.IndexedCollection.getReferenceTo() - pyamf.util.IndexedCollection.remove() - pyamf.util.IndexedMap.__init__() - pyamf.util.IndexedMap.append() - pyamf.util.IndexedMap.clear() - pyamf.util.IndexedMap.getMappedByReference() - pyamf.util.IndexedMap.map() - pyamf.util.IndexedMap.remove() - pyamf.util.StringIOProxy.__len__() - pyamf.util.StringIOProxy.close() - pyamf.util.StringIOProxy.flush() - pyamf.util.StringIOProxy.getvalue() - pyamf.util.StringIOProxy.next() - pyamf.util.StringIOProxy.read() - pyamf.util.StringIOProxy.readline() - pyamf.util.StringIOProxy.seek() - pyamf.util.StringIOProxy.tell() - pyamf.util.StringIOProxy.truncate() - pyamf.util.StringIOProxy.write() - pyamf.util.StringIOProxy.writelines() - pyamf.util.get_class_alias() - pyamf.util.imports.PY_EXT - pyamf.util.imports.loadedModules - pyamf.util.imports.postLoadHooks - pyamf.util.negative_timestamp_broken - pyamf.util.read_double_workaround() - pyamf.util.write_double_workaround() - pyamf.util.xml_types Warning: No description: - object.__new__() - pyamf.util.IndexedCollection - pyamf.util.StringIOProxy.readlines() }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 22:28:01 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 13 22:28:21 2009 Subject: [pyamf-tickets] #419: Put the changelog in the API docs In-Reply-To: <033.209be78cfaf0e68649600fc3e938e6ea@pyamf.org> References: <033.209be78cfaf0e68649600fc3e938e6ea@pyamf.org> Message-ID: <042.4b783c6471dfca07d8e73fdeaadf3459@pyamf.org> #419: Put the changelog in the API docs ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: enhancement | Status: accepted Priority: minor | Milestone: 0.5 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Changes (by thijs): * priority: major => minor * status: new => accepted Comment: This can be done by adding the following option to [source:pyamf/trunk/setup.cfg]: {{{ # An alternative help file. The named file should contain the # body of an HTML file; navigation bars will be added to it. help: my_helpfile.html }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 14 01:02:49 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 14 01:03:05 2009 Subject: [pyamf-tickets] #419: Put the changelog in the API docs In-Reply-To: <033.209be78cfaf0e68649600fc3e938e6ea@pyamf.org> References: <033.209be78cfaf0e68649600fc3e938e6ea@pyamf.org> Message-ID: <042.068728ad160879803170c24f67b73b06@pyamf.org> #419: Put the changelog in the API docs ----------------------------+----------------------------------------------- Reporter: thijs | Owner: thijs Type: enhancement | Status: closed Priority: minor | Milestone: 0.4 Component: Documentation | Version: 0.4 Resolution: fixed | Keywords: ----------------------------+----------------------------------------------- Changes (by thijs): * status: accepted => closed * resolution: => fixed * milestone: 0.5 => 0.4 Comment: Fixed with r2051 -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 14 02:19:30 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 14 02:19:50 2009 Subject: [pyamf-tickets] #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. In-Reply-To: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> References: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> Message-ID: <045.8e4f41b8989fe6284685f3e9468c992e@pyamf.org> #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: dthompso Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Comment(by nick): I found an obscure bug in AMF3 that didn't handle anonymous classes and class definition references correctly, which I committed to the branch - the build slaves were showing test failures. Code & tests & EchoTest look good. Please merge. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 14 19:53:54 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 14 19:54:12 2009 Subject: [pyamf-tickets] #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. In-Reply-To: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> References: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> Message-ID: <045.83cb7b25773f2086f45ebf323a79c2b0@pyamf.org> #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. -----------------------+---------------------------------------------------- Reporter: dthompso | Owner: dthompso Type: defect | Status: closed Priority: blocker | Milestone: 0.4 Component: Adapters | Version: 0.4 Resolution: fixed | Keywords: -----------------------+---------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Merged this to source:pyamf/branches/release-0.4 as we're pushing 0.4rc3. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 14 22:43:09 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 14 22:43:32 2009 Subject: [pyamf-tickets] #430: Release 0.4rc3 In-Reply-To: <033.c022fd46085140a368c91facf2af7613@pyamf.org> References: <033.c022fd46085140a368c91facf2af7613@pyamf.org> Message-ID: <042.9899fd93cc7595c27bf66b804e7c77f5@pyamf.org> #430: Release 0.4rc3 ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: closed Priority: blocker | Milestone: 0.4 Component: Website | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by thijs): * status: new => closed * component: Testing => Website * resolution: => fixed Comment: Fixed with r2063 -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 15 05:39:27 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 15 05:39:50 2009 Subject: [pyamf-tickets] #441: 2052 Breaks _sqlalchemy adapter Message-ID: <036.ba16b2d06cb56da2bf08e32d0894e88f@pyamf.org> #441: 2052 Breaks _sqlalchemy adapter ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- The getLazyAttrs method does not work correctly. You can't determine which attributes are lazy on a class wide basis. Which attributes are lazy is specific to an individual object, and is determined by how the object was originally queried, and if the lazy-loaded attributes have been accessed (at which time SA automatically loads them). You also can't use the mapper to determine which attributes are lazy, because prop.lazy is an attribute that tells SA how to perform a query, not whether an individual object has loaded that attribute yet. Similarly, in the ApplyAttributes method, you must use the lazy attribute list that came from the client, because the client may have loaded some of those attributes after the persistent object was originally queried and encoded. -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 15 13:18:40 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 15 13:18:58 2009 Subject: [pyamf-tickets] #441: 2052 Breaks _sqlalchemy adapter In-Reply-To: <036.ba16b2d06cb56da2bf08e32d0894e88f@pyamf.org> References: <036.ba16b2d06cb56da2bf08e32d0894e88f@pyamf.org> Message-ID: <045.9d2e35fedbece960cabc17a560975c53@pyamf.org> #441: 2052 Breaks _sqlalchemy adapter ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: dthompso Type: defect | Status: assigned Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: review | ----------------------+----------------------------------------------------- Changes (by nick): * keywords: => review * status: new => assigned * owner: nick => dthompso Comment: Yep, using class lazy attrs is not the right thing to do here .. I have attached a diff which corrects this behaviour -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 15 20:26:01 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 15 20:26:24 2009 Subject: [pyamf-tickets] #441: 2052 Breaks _sqlalchemy adapter In-Reply-To: <036.ba16b2d06cb56da2bf08e32d0894e88f@pyamf.org> References: <036.ba16b2d06cb56da2bf08e32d0894e88f@pyamf.org> Message-ID: <045.b01e82c47e0ba1cd85e6a845023eb2b9@pyamf.org> #441: 2052 Breaks _sqlalchemy adapter ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: dthompso Type: defect | Status: assigned Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: review | ----------------------+----------------------------------------------------- Comment(by dthompso): Patch looks good and works with our system. Thanks! -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 15 21:10:10 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 15 21:10:34 2009 Subject: [pyamf-tickets] #252: Integrate egg building into the buildslave (was: Add egg export feature to package script) In-Reply-To: <033.71bde58a1920b3944fc7c735254710e3@pyamf.org> References: <033.71bde58a1920b3944fc7c735254710e3@pyamf.org> Message-ID: <042.986cae6a055da8c4708f2591b6826cd7@pyamf.org> #252: Integrate egg building into the buildslave -----------------------+---------------------------------------------------- Reporter: thijs | Owner: nick Type: task | Status: new Priority: minor | Milestone: At some point Component: Installer | Version: 0.3 Keywords: | -----------------------+---------------------------------------------------- Old description: > The [source:pyamf/sandbox/release/package.py package script] currently > doesn't create any .egg files. It should be able to do this for multiple > versions of Python. New description: The platform-specific eggs should be build by the buildslaves and uploaded to the master. -- Comment(by thijs): Sounds good, updated the ticket summary and description. -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 15 21:23:01 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 15 21:23:20 2009 Subject: [pyamf-tickets] #442: Fix custom Test buildstep that marks failed tests as successful Message-ID: <033.a0b0a49c3dea17d19a1228735a4d031d@pyamf.org> #442: Fix custom Test buildstep that marks failed tests as successful ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.4 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ The buildslave marks test runs as successful when they're failing, which can be seen [http://buildbot.pyamf.org/builders/x86-macosx- py25/builds/64/steps/python2.5-test_2/logs/stdio here] for example. This is a bug in our custom [source:/pyamf/sandbox/buildbot/pyamf.py test buildstep] and can be fixed by following the [http://buildbot.net/trac/ticket/275 instructions] from the buildbot developers. -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 15 21:27:16 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 15 21:27:34 2009 Subject: [pyamf-tickets] #442: Fix custom Test buildstep that marks failed tests as successful In-Reply-To: <033.a0b0a49c3dea17d19a1228735a4d031d@pyamf.org> References: <033.a0b0a49c3dea17d19a1228735a4d031d@pyamf.org> Message-ID: <042.5c29a132d22161aac3e1ce982625c9c9@pyamf.org> #442: Fix custom Test buildstep that marks failed tests as successful ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.4 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Comment(by thijs): Made an update in r2065 based on the perl test buildstep, but probably still needs some work (regexp) and testing. -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 15 23:34:17 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 15 23:35:30 2009 Subject: [pyamf-tickets] #441: 2052 Breaks _sqlalchemy adapter In-Reply-To: <036.ba16b2d06cb56da2bf08e32d0894e88f@pyamf.org> References: <036.ba16b2d06cb56da2bf08e32d0894e88f@pyamf.org> Message-ID: <045.eb07a173e07bad96459ca24e1a73e0a4@pyamf.org> #441: 2052 Breaks _sqlalchemy adapter ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: nick Type: defect | Status: accepted Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by nick): * keywords: review => * status: assigned => accepted * owner: dthompso => nick Comment: Branching to source:pyamf/branches/sa-lazy-attrs-441 -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 15 23:43:33 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 15 23:43:52 2009 Subject: [pyamf-tickets] #441: 2052 Breaks _sqlalchemy adapter In-Reply-To: <036.ba16b2d06cb56da2bf08e32d0894e88f@pyamf.org> References: <036.ba16b2d06cb56da2bf08e32d0894e88f@pyamf.org> Message-ID: <045.e20452075fffbe64bea05cd35d434b2a@pyamf.org> #441: 2052 Breaks _sqlalchemy adapter -----------------------+---------------------------------------------------- Reporter: dthompso | Owner: nick Type: defect | Status: closed Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Resolution: fixed | Keywords: -----------------------+---------------------------------------------------- Changes (by nick): * status: accepted => closed * resolution: => fixed -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 16 00:22:00 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 16 00:22:21 2009 Subject: [pyamf-tickets] #442: Fix custom Test buildstep that marks failed tests as successful In-Reply-To: <033.a0b0a49c3dea17d19a1228735a4d031d@pyamf.org> References: <033.a0b0a49c3dea17d19a1228735a4d031d@pyamf.org> Message-ID: <042.ff62dc465f86c0499ad4ec0e9904acb5@pyamf.org> #442: Fix custom Test buildstep that marks failed tests as successful ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: closed Priority: major | Milestone: 0.4 Component: Testing | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by nick): * status: new => closed * resolution: => fixed Comment: This has now been sorted check the [http://buildbot.pyamf/waterfall waterfall] -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 16 10:53:06 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 16 10:53:25 2009 Subject: [pyamf-tickets] #443: Implement auto aliasing Message-ID: <032.5797f786ec9d31c4d52d60730a5be07a@pyamf.org> #443: Implement auto aliasing -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: new Priority: major | Milestone: Component: Encoder | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- I was reading up on some [http://marxsoftware.blogspot.com/2009/01/bare- bones-blazeds-object-remoting.html BlazeDS magikery] and it appears that it supports auto aliasing .. that is when an instance is fed into the encoder its full package/module name + class name is automatically registered (server side at least), presumably if not already registered. This is something that PyAMF ought to support - it would get us out of a lot of jams regarding decoding untyped objects - especially with SQLAlchemy. The feature should be optional as not to break backward compatibility (we may set this as the default for 0.5). From the linked blog post: {{{ #!python # file-name: dustin.py class Person(object): __slots__ = ('firstName', 'lastName') def __str__(self): return '%s %s' % (self.firstName, self.lastName) }}} {{{ #!python # file-name: gateway.py from dustin import Person class HelloWorldRemotingServer(object): def processHello(self, name): return "Hello, %s!" % (name,) def processName(self, p): assert isinstance(p, Person) return "Your name is %s, %s %s!" % (p.lastName, p.firstName, p.lastName) services = { 'HelloWorld': HelloWorldRemotingServer() } if __name__ == '__main__': from pyamf.remoting.gateway.wsgi import WSGIGateway from wsgiref import simple_server gw = WSGIGateway(services) httpd = simple_server.WSGIServer( ('localhost', 8000), simple_server.WSGIRequestHandler, ) httpd.set_app(gw) try: httpd.serve_forever() except (KeyboardInterrupt, SystemExit): pass }}} Look mum - no XML! -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 16 11:37:17 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 16 11:37:33 2009 Subject: [pyamf-tickets] #444: BufferedByteStream.truncate(100) doesn't work as expected Message-ID: <032.16909237061b20c2515a9811661a6570@pyamf.org> #444: BufferedByteStream.truncate(100) doesn't work as expected ---------------------+------------------------------------------------------ Reporter: nick | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.4 Component: Utility | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ {{{ #!python from pyamf.util import BufferedByteStream x = BufferedByteStream('hello') x.truncate(3) assert x.getvalue() == 'hel' }}} The actual value is `''`. -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 16 12:03:40 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 16 12:03:56 2009 Subject: [pyamf-tickets] #444: BufferedByteStream.truncate(100) doesn't work as expected In-Reply-To: <032.16909237061b20c2515a9811661a6570@pyamf.org> References: <032.16909237061b20c2515a9811661a6570@pyamf.org> Message-ID: <041.48201977fd21966afd37a63c35a1b09f@pyamf.org> #444: BufferedByteStream.truncate(100) doesn't work as expected ---------------------+------------------------------------------------------ Reporter: nick | Owner: nick Type: defect | Status: accepted Priority: major | Milestone: 0.4 Component: Utility | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Changes (by nick): * status: new => accepted Comment: Branching to source:pyamf/branches/truncate-444 -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 16 12:04:16 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 16 12:04:33 2009 Subject: [pyamf-tickets] #444: BufferedByteStream.truncate(100) doesn't work as expected In-Reply-To: <032.16909237061b20c2515a9811661a6570@pyamf.org> References: <032.16909237061b20c2515a9811661a6570@pyamf.org> Message-ID: <041.adfda6f725c6c533a48128864c2da473@pyamf.org> #444: BufferedByteStream.truncate(100) doesn't work as expected ---------------------+------------------------------------------------------ Reporter: nick | Owner: feisley Type: defect | Status: assigned Priority: major | Milestone: 0.4 Component: Utility | Version: 0.4 Keywords: review | ---------------------+------------------------------------------------------ Changes (by nick): * keywords: => review * status: accepted => assigned * owner: nick => feisley Comment: Buildslaves look good. -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 16 20:01:55 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 16 20:02:15 2009 Subject: [pyamf-tickets] #420: Create example that uses the SQLAlchemy Adapter In-Reply-To: <033.50980369e7f89a7c2776b18e6efa6bcf@pyamf.org> References: <033.50980369e7f89a7c2776b18e6efa6bcf@pyamf.org> Message-ID: <042.c81b7553f177ac0ea40fe07fd396ef94@pyamf.org> #420: Create example that uses the SQLAlchemy Adapter ----------------------+----------------------------------------------------- Reporter: thijs | Owner: dthompso Type: task | Status: assigned Priority: major | Milestone: 0.5 Component: Examples | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Comment(by dthompso): I committed some example code that needs to be reviewed. [http://pyamf.org/browser/examples/branches/sqlalchemy_examples_420 example] -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 12:19:52 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 12:20:11 2009 Subject: [pyamf-tickets] #429: Grab version nr for setuptools from pyamf.__version__ In-Reply-To: <033.2494d02167f54b117ea00871f6dcefee@pyamf.org> References: <033.2494d02167f54b117ea00871f6dcefee@pyamf.org> Message-ID: <042.0f2ed0b0db577b455946d9f569884ecc@pyamf.org> #429: Grab version nr for setuptools from pyamf.__version__ -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: accepted Priority: minor | Milestone: 0.5 Component: Installer | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by nick): * status: new => accepted Comment: Branching to source:pyamf/branches/setup-version-429 -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 12:57:51 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 12:58:07 2009 Subject: [pyamf-tickets] #429: Grab version nr for setuptools from pyamf.__version__ In-Reply-To: <033.2494d02167f54b117ea00871f6dcefee@pyamf.org> References: <033.2494d02167f54b117ea00871f6dcefee@pyamf.org> Message-ID: <042.4d17d4d8c33c0081c24478acc7d944bc@pyamf.org> #429: Grab version nr for setuptools from pyamf.__version__ -------------------------+-------------------------------------------------- Reporter: thijs | Owner: thijs Type: enhancement | Status: assigned Priority: minor | Milestone: 0.5 Component: Installer | Version: 0.4 Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * keywords: => review * status: accepted => assigned * owner: nick => thijs -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 20:14:31 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 20:14:51 2009 Subject: [pyamf-tickets] #269: Issues with PyAMF and Jython In-Reply-To: <033.e52e403024bdb47ab854aeb6669eb8cc@pyamf.org> References: <033.e52e403024bdb47ab854aeb6669eb8cc@pyamf.org> Message-ID: <042.efdcaf0fbbbd95573edece3486d07e5e@pyamf.org> #269: Issues with PyAMF and Jython -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: accepted Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.3 Keywords: | -------------------------+-------------------------------------------------- Old description: > I tested PyAMF on [http://www.jython.org Jython] with different versions > and quite a few tests failed: > > - PyAMF r1441 and Jython - trunk > [http://fisheye3.atlassian.com/changelog/jython/?cs=4725 r4725] > ([attachment:jython-r4725.log log]) > - PyAMF r1458 and Jython - trunk > [http://fisheye3.atlassian.com/changelog/jython/?cs=4758 r4758] > ([attachment:jython-r4758.log log]) > - PyAMF r1531 and Jython - trunk > [http://fisheye3.atlassian.com/changelog/jython/?cs=4927 r4927] > (tests=427, failures=19, errors=125) > - PyAMF r1586 and Jython - asm branch > [http://fisheye3.atlassian.com/changelog/jython/?cs=5026 r5026] > ([http://buildbot.pyamf.org/builders/amd64-ubuntu-jython/builds/6/steps > /jython-test/logs/stdio/text failures=15, errors=14)] > - PyAMF r1597 and Jython - trunk > [http://fisheye3.atlassian.com/changelog/jython/?cs=5215 r5215] > ([http://buildbot.pyamf.org/builders/amd64-ubuntu-jython/builds/18/steps > /jython-test/logs/stdio/text failures=18, errors=1]) > - PyAMF r1699 and Jython - trunk > [http://fisheye3.atlassian.com/changelog/jython/?cs=5372 r5372] > ([http://buildbot.pyamf.org/builders/amd64-ubuntu-jython/builds/103/steps > /jython-test/logs/stdio/text failures=15, errors=1]) > - PyAMF r1848 and Jython - trunk > [http://fisheye3.atlassian.com/changelog/jython/?cs=5770 r5770] > ([http://buildbot.pyamf.org/builders/amd64-ubuntu-jython/builds/108/steps > /jython-test/logs/stdio/text failures=18, errors=1]) > > == How to reproduce == > > 1. Grab the Jython trunk: > {{{ > #!sh > svn co https://jython.svn.sourceforge.net/svnroot/jython/trunk jython- > trunk > }}} > > 2. Compile Jython and set {{{JYTHON_HOME}}}: > {{{ > #!sh > cd jython-trunk > ant > export JYTHON_HOME=/path/to/jython-trunk/dist > chmod 777 $JYTHON_HOME/bin/jython > }}} > > 3. Grab the PyAMF trunk, install setuptools with: > {{{ > #!sh > $JYTHON_HOME/bin/jython ez_setup.py > }}} > > 4. Run the tests from the PyAMF trunk: > {{{ > #!sh > $JYTHON_HOME/bin/jython setup.py test > }}} New description: I tested PyAMF on [http://www.jython.org Jython] with different versions and quite a few tests failed: - PyAMF r1441 and Jython - trunk [http://fisheye3.atlassian.com/changelog/jython/?cs=4725 r4725] ([attachment:jython-r4725.log log]) - PyAMF r1458 and Jython - trunk [http://fisheye3.atlassian.com/changelog/jython/?cs=4758 r4758] ([attachment:jython-r4758.log log]) - PyAMF r1531 and Jython - trunk [http://fisheye3.atlassian.com/changelog/jython/?cs=4927 r4927] (tests=427, failures=19, errors=125) - PyAMF r1586 and Jython - asm branch [http://fisheye3.atlassian.com/changelog/jython/?cs=5026 r5026] ([http://buildbot.pyamf.org/builders/amd64-ubuntu-jython/builds/6/steps /jython-test/logs/stdio/text failures=15, errors=14)] - PyAMF r1597 and Jython - trunk [http://fisheye3.atlassian.com/changelog/jython/?cs=5215 r5215] ([http://buildbot.pyamf.org/builders/amd64-ubuntu-jython/builds/18/steps /jython-test/logs/stdio/text failures=18, errors=1]) - PyAMF r1699 and Jython - trunk [http://fisheye3.atlassian.com/changelog/jython/?cs=5372 r5372] ([http://buildbot.pyamf.org/builders/amd64-ubuntu-jython/builds/103/steps /jython-test/logs/stdio/text failures=15, errors=1]) - PyAMF r1848 and Jython - trunk [http://fisheye3.atlassian.com/changelog/jython/?cs=5770 r5770] ([http://buildbot.pyamf.org/builders/amd64-ubuntu-jython/builds/108/steps /jython-test/logs/stdio/text failures=18, errors=1]) - PyAMF r2078 and Jython trunk [http://fisheye3.atlassian.com/changelog/jython/?cs=5939 r5939] [http://buildbot.pyamf.org/builders/jython25/builds/25/steps/python2.5-test_2/logs/stdio/text failures=4]) == How to reproduce == 1. Grab the Jython trunk: {{{ #!sh svn co https://jython.svn.sourceforge.net/svnroot/jython/trunk jython- trunk }}} 2. Compile Jython and set {{{JYTHON_HOME}}}: {{{ #!sh cd jython-trunk ant export JYTHON_HOME=/path/to/jython-trunk/dist chmod 777 $JYTHON_HOME/bin/jython }}} 3. Grab the PyAMF trunk, install setuptools with: {{{ #!sh $JYTHON_HOME/bin/jython ez_setup.py }}} 4. Run the tests from the PyAMF trunk: {{{ #!sh $JYTHON_HOME/bin/jython setup.py test }}} -- Comment(by thijs): Replying to [comment:15 thijs]: > Blocked by #353 and http://bugs.jython.org/issue1227 Both issues have been fixed in the Jython trunk now. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 20:16:08 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 20:16:26 2009 Subject: [pyamf-tickets] #353: Bytearray test hack showing in Jython In-Reply-To: <033.7ab88d6b724bc380e58306e1cbfc2367@pyamf.org> References: <033.7ab88d6b724bc380e58306e1cbfc2367@pyamf.org> Message-ID: <042.07c271e711bc8714c333f749a3973549@pyamf.org> #353: Bytearray test hack showing in Jython ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: task | Status: closed Priority: minor | Milestone: 0.4 Component: Testing | Version: 0.3.1 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by thijs): * status: accepted => closed * resolution: => fixed * milestone: 0.5 => 0.4 Comment: Fixed in Jython's trunk (r5938) and the test is now passing. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 20:24:34 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 20:24:52 2009 Subject: [pyamf-tickets] #445: Setup weekly bug report mail Message-ID: <033.2d3411dddfc9117ee0eb6b5e7df761e8@pyamf.org> #445: Setup weekly bug report mail ---------------------+------------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: new Priority: major | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Twisted has a weekly bug report email that is send to their main mailinglist. Would be cool to have something similar for PyAMF. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 20:24:44 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 20:25:02 2009 Subject: [pyamf-tickets] #437: Move Jython buildslave to different server In-Reply-To: <033.f16137b48b0e77b18c75dc4812cf1203@pyamf.org> References: <033.f16137b48b0e77b18c75dc4812cf1203@pyamf.org> Message-ID: <042.327a20a25c4c2838bcdd0ae752503815@pyamf.org> #437: Move Jython buildslave to different server ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: task | Status: closed Priority: major | Milestone: 0.5 Component: Testing | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by nick): * status: new => closed * resolution: => fixed Comment: The Jython buildslave has now been moved to callisto. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 20:40:28 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 20:41:06 2009 Subject: [pyamf-tickets] #429: Grab version nr for setuptools from pyamf.__version__ In-Reply-To: <033.2494d02167f54b117ea00871f6dcefee@pyamf.org> References: <033.2494d02167f54b117ea00871f6dcefee@pyamf.org> Message-ID: <042.b09289bb982ca0291e4f94ab44bd9985@pyamf.org> #429: Grab version nr for setuptools from pyamf.__version__ -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: assigned Priority: minor | Milestone: 0.4 Component: Installer | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * keywords: review => * owner: thijs => nick * milestone: 0.5 => 0.4 Comment: I guess an entry in the changelog would be useful when you merge it. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 20:51:23 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 20:51:44 2009 Subject: [pyamf-tickets] #429: Grab version nr for setuptools from pyamf.__version__ In-Reply-To: <033.2494d02167f54b117ea00871f6dcefee@pyamf.org> References: <033.2494d02167f54b117ea00871f6dcefee@pyamf.org> Message-ID: <042.6d58786a8a999a7dbeaa7b21783996b8@pyamf.org> #429: Grab version nr for setuptools from pyamf.__version__ --------------------------+------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: closed Priority: minor | Milestone: 0.4 Component: Installer | Version: 0.4 Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Fixed in r2080. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 20:52:14 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 20:52:37 2009 Subject: [pyamf-tickets] #438: Setup PyAMF rsync backup In-Reply-To: <033.4bccdfb705c5fd749ecc83f062fdf762@pyamf.org> References: <033.4bccdfb705c5fd749ecc83f062fdf762@pyamf.org> Message-ID: <042.3243eca7621463a35066db56b3b58e00@pyamf.org> #438: Setup PyAMF rsync backup ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: assigned Priority: critical | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by nick): * status: new => assigned * owner: feisley => thijs Comment: We need some permissions setup on saturn to achieve this. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 20:55:58 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 20:56:14 2009 Subject: [pyamf-tickets] #85: Twisted WSGI adaptor In-Reply-To: <033.9fa0e1dc855ed88894db0168560e2f25@pyamf.org> References: <033.9fa0e1dc855ed88894db0168560e2f25@pyamf.org> Message-ID: <042.1db94ff01a2dd1cf412937efd166c9c4@pyamf.org> #85: Twisted WSGI adaptor --------------------------+------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: closed Priority: minor | Milestone: At some point Component: Gateway | Version: 0.1a Resolution: wontfix | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: new => closed * resolution: => wontfix Comment: web2 is now deprecated so this is no longer required. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 21:02:55 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 21:03:11 2009 Subject: [pyamf-tickets] #85: Twisted WSGI adaptor In-Reply-To: <033.9fa0e1dc855ed88894db0168560e2f25@pyamf.org> References: <033.9fa0e1dc855ed88894db0168560e2f25@pyamf.org> Message-ID: <042.b8f54c5afef8cb0eb25c93dbbedd3174@pyamf.org> #85: Twisted WSGI adaptor --------------------------+------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: reopened Priority: minor | Milestone: At some point Component: Gateway | Version: Resolution: | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: closed => reopened * version: 0.1a => * resolution: wontfix => Comment: Re-opening this because wsgi is supported in `twisted.web`. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 21:17:18 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 21:17:35 2009 Subject: [pyamf-tickets] #446: Jython example Message-ID: <033.e8def5e28b3a79fb81472dbe806c7287@pyamf.org> #446: Jython example ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: new Priority: major | Milestone: 0.5 Component: Examples | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Now that the test suite passes on Jython 2.5 it would be cool to have a Jython example showing how to use PyAMF with Java. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 21:28:26 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 21:28:44 2009 Subject: [pyamf-tickets] #420: Create example that uses the SQLAlchemy Adapter In-Reply-To: <033.50980369e7f89a7c2776b18e6efa6bcf@pyamf.org> References: <033.50980369e7f89a7c2776b18e6efa6bcf@pyamf.org> Message-ID: <042.2ff50201f5db57715d1b3532af57a8ad@pyamf.org> #420: Create example that uses the SQLAlchemy Adapter ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: task | Status: accepted Priority: major | Milestone: 0.5 Component: Examples | Version: 0.4 Keywords: review | ----------------------+----------------------------------------------------- Changes (by nick): * keywords: => review * status: assigned => accepted * owner: dthompso => nick -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 21:33:27 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 21:33:46 2009 Subject: [pyamf-tickets] #444: BufferedByteStream.truncate(100) doesn't work as expected In-Reply-To: <032.16909237061b20c2515a9811661a6570@pyamf.org> References: <032.16909237061b20c2515a9811661a6570@pyamf.org> Message-ID: <041.50a1b98f56326ab7929eae26acd9a079@pyamf.org> #444: BufferedByteStream.truncate(100) doesn't work as expected ---------------------+------------------------------------------------------ Reporter: nick | Owner: nick Type: defect | Status: assigned Priority: major | Milestone: 0.4 Component: Utility | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Changes (by thijs): * keywords: review => * owner: feisley => nick Comment: Merge with a changelog entry, thx. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 21:37:08 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 21:37:29 2009 Subject: [pyamf-tickets] #447: test_amf3.ComplexEncodingTestCase failing for Jyton Message-ID: <033.d86c3b90679015b09a4c1f3b8a903bc9@pyamf.org> #447: test_amf3.ComplexEncodingTestCase failing for Jyton ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.5 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ From the buildslave [http://buildbot.pyamf.org/builders/jython25/builds/30/steps/python2.5-test_2/logs/stdio log]: {{{ FAIL: test_complex_dict (pyamf.tests.test_amf3.ComplexEncodingTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/buildbot/slaves/pyamf/jython25/build/pyamf/tests/test_amf3.py", line 1624, in test_complex_dict self.complex_test() File "/home/buildbot/slaves/pyamf/jython25/build/pyamf/tests/test_amf3.py", line 1613, in complex_test self.assertEquals(self.TestSubObject, class_defs[2].klass) AssertionError: != ====================================================================== FAIL: test_complex_encode_decode_dict (pyamf.tests.test_amf3.ComplexEncodingTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/buildbot/slaves/pyamf/jython25/build/pyamf/tests/test_amf3.py", line 1632, in test_complex_encode_decode_dict self.complex_encode_decode_test(decoded['objects']) File "/home/buildbot/slaves/pyamf/jython25/build/pyamf/tests/test_amf3.py", line 1618, in complex_encode_decode_test self.assertEquals(self.TestSubObject, obj.sub_obj.__class__) AssertionError: != ---------------------------------------------------------------------- }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 21:40:55 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 21:41:16 2009 Subject: [pyamf-tickets] #444: BufferedByteStream.truncate(100) doesn't work as expected In-Reply-To: <032.16909237061b20c2515a9811661a6570@pyamf.org> References: <032.16909237061b20c2515a9811661a6570@pyamf.org> Message-ID: <041.996567c657f9c058a126550b2bac8946@pyamf.org> #444: BufferedByteStream.truncate(100) doesn't work as expected ----------------------+----------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: closed Priority: major | Milestone: 0.4 Component: Utility | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Merged in r2082. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 21:51:14 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 21:51:34 2009 Subject: [pyamf-tickets] #447: test_amf3.ComplexEncodingTestCase failing for Jython (was: test_amf3.ComplexEncodingTestCase failing for Jyton) In-Reply-To: <033.d86c3b90679015b09a4c1f3b8a903bc9@pyamf.org> References: <033.d86c3b90679015b09a4c1f3b8a903bc9@pyamf.org> Message-ID: <042.cdaeeb3c2540d0f8bfed0d29738926f5@pyamf.org> #447: test_amf3.ComplexEncodingTestCase failing for Jython ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.5 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Comment(by thijs): Fix typo -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 22:02:36 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 22:02:54 2009 Subject: [pyamf-tickets] #443: Implement auto aliasing In-Reply-To: <032.5797f786ec9d31c4d52d60730a5be07a@pyamf.org> References: <032.5797f786ec9d31c4d52d60730a5be07a@pyamf.org> Message-ID: <041.91936abf5d6641638432488bf7d19ac6@pyamf.org> #443: Implement auto aliasing -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: new Priority: major | Milestone: At some point Component: Encoder | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * milestone: => At some point Comment: Assigning ticket to a milestone so it isnt singled out on the ticket overview page. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 22:11:18 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 17 22:11:34 2009 Subject: [pyamf-tickets] #421: Add note about optional adapter/gateway dependencies in the installation instructions In-Reply-To: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> References: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> Message-ID: <042.b1aa041275eb047fcd026a8a30e3cf9e@pyamf.org> #421: Add note about optional adapter/gateway dependencies in the installation instructions ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: enhancement | Status: accepted Priority: major | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Changes (by thijs): * status: new => accepted * milestone: 0.5 => 0.4 -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 02:48:02 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 02:48:24 2009 Subject: [pyamf-tickets] #448: test_infinites failing for Python 2.5 on win32 Message-ID: <033.16d8657be2ad2194fa3d68da8884078d@pyamf.org> #448: test_infinites failing for Python 2.5 on win32 ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: new Priority: blocker | Milestone: 0.4 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ See the buildslave [http://buildbot.pyamf.org/builders/winxp32-py25/builds/64/steps/python2.5-test_4/logs/stdio/text log]: {{{ =============================================================================== [FAIL]: pyamf.tests.test_amf0.DecoderTestCase.test_infinites Traceback (most recent call last): File "C:\Python25\lib\unittest.py", line 260, in run testMethod() File "c:\buildbot\pyamf\winxp32-py25\build\pyamf\tests\test_amf0.py", line 576, in test_infinites self.assertTrue(isNaN(x)) exceptions.AssertionError: =============================================================================== [FAIL]: pyamf.tests.test_amf3.DecoderTestCase.test_infinites Traceback (most recent call last): File "C:\Python25\lib\unittest.py", line 260, in run testMethod() File "c:\buildbot\pyamf\winxp32-py25\build\pyamf\tests\test_amf3.py", line 771, in test_infinites self.assertTrue(_util.isNaN(x)) exceptions.AssertionError: =============================================================================== [FAIL]: pyamf.tests.test_util.DataTypeMixInTestCase.test_nan Traceback (most recent call last): File "C:\Python25\lib\unittest.py", line 260, in run testMethod() File "c:\buildbot\pyamf\winxp32-py25\build\pyamf\tests\test_util.py", line 500, in test_nan self.assertTrue(_util.isNaN(x.read_double())) exceptions.AssertionError: ------------------------------------------------------------------------------- }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 03:09:44 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 03:10:04 2009 Subject: [pyamf-tickets] #449: Support for SQLAlchemy 0.5.1 Message-ID: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> #449: Support for SQLAlchemy 0.5.1 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: new Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- [http://sqlalchemy.org SQLAlchemy 0.5.1] was released on Jan 17 and the test results now show {{{SADeprecationWarning}}}s: {{{ /home/thijs/pyamf/pyamf/tests/adapters/test_sqlalchemy.py:115: sqlalchemy.exc.SADeprecationWarning: Use session.add() [OK] pyamf.tests.adapters.test_sqlalchemy.SATestCase.test_encode_decode_persistent ... /home/thijs/pyamf/pyamf/tests/adapters/test_sqlalchemy.py:99: sqlalchemy.exc.SADeprecationWarning: Use session.add() [OK] pyamf.tests.adapters.test_sqlalchemy.SATestCase.test_encode_decode_transient ... [OK] pyamf.tests.adapters.test_sqlalchemy.SATestCase.test_encode_decode_with_references ... /home/thijs/pyamf/pyamf/tests/adapters/test_sqlalchemy.py:194: sqlalchemy.exc.SADeprecationWarning: Use session.add() [OK] pyamf.tests.adapters.test_sqlalchemy.SATestCase.test_lazy_load_attributes ... /home/thijs/pyamf/pyamf/tests/adapters/test_sqlalchemy.py:155: sqlalchemy.exc.SADeprecationWarning: Use session.add() /home/thijs/pyamf/pyamf/tests/adapters/test_sqlalchemy.py:157: sqlalchemy.exc.SADeprecationWarning: Use session.expunge_all() [OK] pyamf.tests.adapters.test_sqlalchemy.SATestCase.test_merge_with_lazy_loaded_attrs ... /home/thijs/pyamf/pyamf/tests/adapters/test_sqlalchemy.py:175: sqlalchemy.exc.SADeprecationWarning: Use session.add() /home/thijs/pyamf/pyamf/tests/adapters/test_sqlalchemy.py:177: sqlalchemy.exc.SADeprecationWarning: Use session.expunge_all() [OK] pyamf.tests.adapters.test_sqlalchemy.SATestCase.test_sa_merge ... /home/thijs/pyamf/pyamf/tests/adapters/test_sqlalchemy.py:137: sqlalchemy.exc.SADeprecationWarning: Use session.add() [OK] }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 03:36:44 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 03:37:01 2009 Subject: [pyamf-tickets] #449: Support for SQLAlchemy 0.5.1 In-Reply-To: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> References: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> Message-ID: <042.4dd3579d5af85565aac5a5376637e560@pyamf.org> #449: Support for SQLAlchemy 0.5.1 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: new Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Comment(by thijs): I updated the tarball for the buildslaves to use 0.5.1. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 03:51:54 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 03:52:11 2009 Subject: [pyamf-tickets] #450: Add cython to extras_require Message-ID: <033.59bd837b2638ba854cb8bb31954394b1@pyamf.org> #450: Add cython to extras_require -----------------------+---------------------------------------------------- Reporter: thijs | Owner: nick Type: task | Status: new Priority: major | Milestone: 0.4 Component: Installer | Version: 0.4 Keywords: | -----------------------+---------------------------------------------------- [http://cython.org Cython] is an optional extra required to build the C-extension, and should be added in setup.py. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 04:22:11 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 04:22:26 2009 Subject: [pyamf-tickets] #421: Add note about optional adapter/gateway dependencies in the installation instructions In-Reply-To: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> References: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> Message-ID: <042.5337061b77f965001e046ca6a3525fbb@pyamf.org> #421: Add note about optional adapter/gateway dependencies in the installation instructions ---------------------------+------------------------------------------------ Reporter: thijs | Owner: nick Type: enhancement | Status: assigned Priority: major | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: review | ---------------------------+------------------------------------------------ Changes (by thijs): * keywords: => review * status: accepted => assigned * owner: thijs => nick Comment: See attached patch and updated [wiki:Install] page. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 04:27:23 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 04:27:38 2009 Subject: [pyamf-tickets] #450: Add cython to extras_require In-Reply-To: <033.59bd837b2638ba854cb8bb31954394b1@pyamf.org> References: <033.59bd837b2638ba854cb8bb31954394b1@pyamf.org> Message-ID: <042.23c4b3f80eb67cc5008e3443d7859cd7@pyamf.org> #450: Add cython to extras_require -----------------------+---------------------------------------------------- Reporter: thijs | Owner: nick Type: task | Status: assigned Priority: major | Milestone: 0.4 Component: Installer | Version: 0.4 Keywords: review | -----------------------+---------------------------------------------------- Changes (by thijs): * keywords: => review * status: new => assigned Comment: See attached patch. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 09:38:02 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 09:38:45 2009 Subject: [pyamf-tickets] #421: Add note about optional adapter/gateway dependencies in the installation instructions In-Reply-To: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> References: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> Message-ID: <042.6ab478326e5c51258f63437991876961@pyamf.org> #421: Add note about optional adapter/gateway dependencies in the installation instructions ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: enhancement | Status: assigned Priority: major | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Changes (by nick): * keywords: review => * owner: nick => thijs Comment: I wouldn't include Cython as part of the optional modules. We use Cython to build the cpyamf/*.c from cpyamf/*.pyx files and is purely a developers tool. But apart from that, good to go. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 10:24:43 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 10:24:59 2009 Subject: [pyamf-tickets] #435: Return XML instead of XMLDocument In-Reply-To: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> References: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> Message-ID: <042.7fe42f397f6b7186c64029621683b13c@pyamf.org> #435: Return XML instead of XMLDocument ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: accepted Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by nick): * status: new => accepted * milestone: 0.5 => 0.4 -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 10:43:23 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 10:43:40 2009 Subject: [pyamf-tickets] #435: Return XML instead of XMLDocument In-Reply-To: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> References: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> Message-ID: <042.239c85e70f38cf931eecbe59f81c0661@pyamf.org> #435: Return XML instead of XMLDocument ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: accepted Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Comment(by nick): Branching to source:pyamf/branches/xmldoc-xml-435 -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 10:47:27 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 10:47:43 2009 Subject: [pyamf-tickets] #435: Return XML instead of XMLDocument In-Reply-To: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> References: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> Message-ID: <042.a25ba02bb65ebd751dc4d27da018620d@pyamf.org> #435: Return XML instead of XMLDocument ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: defect | Status: assigned Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: review | ----------------------+----------------------------------------------------- Changes (by nick): * keywords: => review * status: accepted => assigned * owner: nick => thijs Comment: I have added a `use_amf3` flag to `amf0.Encoder`. If client type is set to `pyamf.ClientTypes.Flash9` then this flag is set to `True`. At the moment, only `writeXML` takes any notice of this flag but the attached swf now does as expected (XML = True, XMLDocument = False). -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 12:10:13 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 12:10:29 2009 Subject: [pyamf-tickets] #448: test_infinites failing for Python 2.5 on win32 In-Reply-To: <033.16d8657be2ad2194fa3d68da8884078d@pyamf.org> References: <033.16d8657be2ad2194fa3d68da8884078d@pyamf.org> Message-ID: <042.9390ec1613bc31fa8c4b05a14f88c876@pyamf.org> #448: test_infinites failing for Python 2.5 on win32 ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: accepted Priority: blocker | Milestone: 0.4 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Changes (by nick): * status: new => accepted Comment: Branching to source:pyamf/branches/infinites-win32-448 -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 15:03:23 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 15:03:39 2009 Subject: [pyamf-tickets] #448: test_infinites failing for Python 2.5 on win32 In-Reply-To: <033.16d8657be2ad2194fa3d68da8884078d@pyamf.org> References: <033.16d8657be2ad2194fa3d68da8884078d@pyamf.org> Message-ID: <042.94096334b3330db7637c76c7b2690f98@pyamf.org> #448: test_infinites failing for Python 2.5 on win32 ---------------------+------------------------------------------------------ Reporter: thijs | Owner: thijs Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Testing | Version: 0.4 Keywords: review | ---------------------+------------------------------------------------------ Changes (by nick): * keywords: => review * status: accepted => assigned * owner: nick => thijs Comment: Clean bill of health from the buildslaves .. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 15:21:35 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 15:21:53 2009 Subject: [pyamf-tickets] #449: Support for SQLAlchemy 0.5.1 In-Reply-To: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> References: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> Message-ID: <042.3b3dd844f4605c3b92d788fbba0f442c@pyamf.org> #449: Support for SQLAlchemy 0.5.1 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: accepted Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by nick): * status: new => accepted Comment: Branching to source:pyamf/branches/sa-0.5.1-compat-449 -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 15:22:47 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 15:23:04 2009 Subject: [pyamf-tickets] #449: Support for SQLAlchemy 0.5.1 In-Reply-To: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> References: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> Message-ID: <042.326ffc701794b9fe65ae84b79afe1204@pyamf.org> #449: Support for SQLAlchemy 0.5.1 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: thijs Type: enhancement | Status: assigned Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * keywords: => review * status: accepted => assigned * owner: nick => thijs Comment: I have provided compatibility functions in the BaseTestCase. This removes the deprecation warnings when running with SQLAlchemy==0.5.1 -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 17:28:17 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 17:28:36 2009 Subject: [pyamf-tickets] #450: Add cython to extras_require In-Reply-To: <033.59bd837b2638ba854cb8bb31954394b1@pyamf.org> References: <033.59bd837b2638ba854cb8bb31954394b1@pyamf.org> Message-ID: <042.6d08d9632590cb167883c8cb9370fa10@pyamf.org> #450: Add cython to extras_require -----------------------+---------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: assigned Priority: major | Milestone: 0.4 Component: Installer | Version: 0.4 Keywords: | -----------------------+---------------------------------------------------- Changes (by nick): * keywords: review => * owner: nick => thijs Comment: Looks good. Please apply/merge -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 17:35:56 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 17:36:14 2009 Subject: [pyamf-tickets] #122: Setup documentation tools In-Reply-To: <033.4f5b96b2c71b6165196fe40774b0a8b3@pyamf.org> References: <033.4f5b96b2c71b6165196fe40774b0a8b3@pyamf.org> Message-ID: <042.ab7cfb59d9092779f7ffcc48d96bfe27@pyamf.org> #122: Setup documentation tools ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: accepted Priority: critical | Milestone: 0.5 Component: Documentation | Version: Keywords: | ---------------------------+------------------------------------------------ Changes (by thijs): * keywords: review => * owner: nick => thijs * status: assigned => accepted -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 17:45:41 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 17:45:57 2009 Subject: [pyamf-tickets] #450: Add cython to extras_require In-Reply-To: <033.59bd837b2638ba854cb8bb31954394b1@pyamf.org> References: <033.59bd837b2638ba854cb8bb31954394b1@pyamf.org> Message-ID: <042.4f252aca61ae9a32770f1b6a437e29a3@pyamf.org> #450: Add cython to extras_require ------------------------+--------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: closed Priority: major | Milestone: 0.4 Component: Installer | Version: 0.4 Resolution: fixed | Keywords: ------------------------+--------------------------------------------------- Changes (by thijs): * status: assigned => closed * resolution: => fixed Comment: Applied in r2093. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 17:55:33 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 17:55:49 2009 Subject: [pyamf-tickets] #421: Add note about optional adapter/gateway dependencies in the installation instructions In-Reply-To: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> References: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> Message-ID: <042.0f9e94d2ce90e5a7624c6fc088747882@pyamf.org> #421: Add note about optional adapter/gateway dependencies in the installation instructions ---------------------------+------------------------------------------------ Reporter: thijs | Owner: nick Type: enhancement | Status: assigned Priority: major | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: review | ---------------------------+------------------------------------------------ Changes (by thijs): * keywords: => review * owner: thijs => nick Comment: I updated the patch and added a section for the C-extension. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 17:59:10 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 17:59:26 2009 Subject: [pyamf-tickets] #421: Add note about optional adapter/gateway dependencies in the installation instructions In-Reply-To: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> References: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> Message-ID: <042.d6bc63452cff82b85d9c2952f1620f95@pyamf.org> #421: Add note about optional adapter/gateway dependencies in the installation instructions ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: enhancement | Status: assigned Priority: major | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Changes (by nick): * keywords: review => * owner: nick => thijs Comment: Looks good. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 17:59:10 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 17:59:27 2009 Subject: [pyamf-tickets] #449: Support for SQLAlchemy 0.5.1 In-Reply-To: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> References: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> Message-ID: <042.c9da07828c83d6eba1f11b0aba4392cf@pyamf.org> #449: Support for SQLAlchemy 0.5.1 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: assigned Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * keywords: review => * owner: thijs => nick Comment: Looks good, please merge with a changelog entry. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 18:01:39 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 18:01:56 2009 Subject: [pyamf-tickets] #448: test_infinites failing for Python 2.5 on win32 In-Reply-To: <033.16d8657be2ad2194fa3d68da8884078d@pyamf.org> References: <033.16d8657be2ad2194fa3d68da8884078d@pyamf.org> Message-ID: <042.3b3bfd9fa88a8368ab36084aae38e162@pyamf.org> #448: test_infinites failing for Python 2.5 on win32 ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Changes (by thijs): * keywords: review => * owner: thijs => nick Comment: I don't have access to a win32 machine so if the slaves are happy then I'm happy. Please merge with a changelog entry. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 18:07:45 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 18:08:39 2009 Subject: [pyamf-tickets] #449: Support for SQLAlchemy 0.5.1 In-Reply-To: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> References: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> Message-ID: <042.c2d6f45335c10145c0179d31fe4d5760@pyamf.org> #449: Support for SQLAlchemy 0.5.1 --------------------------+------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: closed Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Merged in r2094. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 18:08:31 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 18:08:55 2009 Subject: [pyamf-tickets] #435: Return XML instead of XMLDocument In-Reply-To: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> References: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> Message-ID: <042.816112ccfa445fcd1b9188353ed5187d@pyamf.org> #435: Return XML instead of XMLDocument ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: assigned Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by thijs): * keywords: review => * owner: thijs => nick Comment: Tested with ParseDump, EchoTest and the test.swf, all look good, please merge with a changelog entry. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 18:11:40 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 18:11:57 2009 Subject: [pyamf-tickets] #421: Add note about optional adapter/gateway dependencies in the installation instructions In-Reply-To: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> References: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> Message-ID: <042.2ff9a638546cbf3156b4c4acfd94acb2@pyamf.org> #421: Add note about optional adapter/gateway dependencies in the installation instructions ----------------------------+----------------------------------------------- Reporter: thijs | Owner: thijs Type: enhancement | Status: closed Priority: major | Milestone: 0.4 Component: Documentation | Version: 0.4 Resolution: fixed | Keywords: ----------------------------+----------------------------------------------- Changes (by thijs): * status: assigned => closed * resolution: => fixed Comment: Applied in r2095. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 18:14:07 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 18:14:37 2009 Subject: [pyamf-tickets] #448: test_infinites failing for Python 2.5 on win32 In-Reply-To: <033.16d8657be2ad2194fa3d68da8884078d@pyamf.org> References: <033.16d8657be2ad2194fa3d68da8884078d@pyamf.org> Message-ID: <042.f51175cf5b66ee7aad04790644d754ae@pyamf.org> #448: test_infinites failing for Python 2.5 on win32 ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: closed Priority: blocker | Milestone: 0.4 Component: Testing | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Merged in r2096. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 18:22:30 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 18:22:48 2009 Subject: [pyamf-tickets] #435: Return XML instead of XMLDocument In-Reply-To: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> References: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> Message-ID: <042.38639eda7e5186020daf48d38fda93ad@pyamf.org> #435: Return XML instead of XMLDocument -----------------------+---------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: closed Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Resolution: fixed | Keywords: -----------------------+---------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Merged in r2097. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 19:41:01 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sun Jan 18 19:41:26 2009 Subject: [pyamf-tickets] #417: Release 0.4 final In-Reply-To: <033.a073f642c43fd4a9856ebdd72d5e1b46@pyamf.org> References: <033.a073f642c43fd4a9856ebdd72d5e1b46@pyamf.org> Message-ID: <042.56177b80de52ccf4beba53ae106485e1@pyamf.org> #417: Release 0.4 final ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: closed Priority: blocker | Milestone: 0.4 Component: Website | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by thijs): * status: new => closed * resolution: => fixed Comment: Updated wiki pages, added tarballs, uploaded to pypi. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 19 07:09:52 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 19 07:10:10 2009 Subject: [pyamf-tickets] #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer Message-ID: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer -------------------------+-------------------------------------------------- Reporter: sparkle | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- using PyAMF 0.4 released at January 18th test = pyamf.util.BufferedByteStream('abcdef') print test.read() print len(test) test.consume() print len(test) test.truncate() print len(test) print out this in cpyamf abcdef 6 6 0 but this in pyamf abcdef 6 0 0 which is the right behavior? -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 19 10:05:15 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 19 10:05:30 2009 Subject: [pyamf-tickets] #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer In-Reply-To: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> References: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> Message-ID: <044.31a04087cd16cd0b534efa6037209e68@pyamf.org> #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer -------------------------+-------------------------------------------------- Reporter: sparkle | Owner: nick Type: defect | Status: accepted Priority: minor | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by nick): * priority: major => minor * status: new => accepted Comment: The correct behaviour is the pure python version. I will attach a patch which corrects cpyamf. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 19 10:06:52 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 19 10:07:09 2009 Subject: [pyamf-tickets] #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer In-Reply-To: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> References: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> Message-ID: <044.8b9e8bdf29a79a038ebad4b56b4b5980@pyamf.org> #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer -------------------------+-------------------------------------------------- Reporter: sparkle | Owner: nick Type: defect | Status: accepted Priority: minor | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Comment(by nick): The patch is rather lengthy but that is mainly due to the regeneration of the C code using cython. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 19 10:15:28 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 19 10:15:45 2009 Subject: [pyamf-tickets] #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer In-Reply-To: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> References: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> Message-ID: <044.44e8726d53624d3dd5139d072644bc8b@pyamf.org> #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer -------------------------+-------------------------------------------------- Reporter: sparkle | Owner: nick Type: defect | Status: accepted Priority: minor | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Comment(by nick): Branching to source:pyamf/branches/cpyamf-consume-451 -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 19 10:20:53 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 19 10:21:09 2009 Subject: [pyamf-tickets] #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer In-Reply-To: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> References: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> Message-ID: <044.d76b1f2ae3ffd1a458a2c1355675a640@pyamf.org> #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer -------------------------+-------------------------------------------------- Reporter: sparkle | Owner: sparkle Type: defect | Status: assigned Priority: minor | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * keywords: => review * status: accepted => assigned * owner: nick => sparkle Comment: The attached patch has been applied to the branch and the buildbots all report okay. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 19 11:40:08 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 19 11:40:24 2009 Subject: [pyamf-tickets] #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer In-Reply-To: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> References: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> Message-ID: <044.bb75c3177f8f6f2a6bb487688ac50a85@pyamf.org> #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer -------------------------+-------------------------------------------------- Reporter: sparkle | Owner: sparkle Type: defect | Status: assigned Priority: minor | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: review | -------------------------+-------------------------------------------------- Old description: > using PyAMF 0.4 released at January 18th > > test = pyamf.util.BufferedByteStream('abcdef') > print test.read() > print len(test) > test.consume() > print len(test) > test.truncate() > print len(test) > > print out this in cpyamf > abcdef > 6 > 6 > 0 > > but this in pyamf > abcdef > 6 > 0 > 0 > > which is the right behavior? New description: using PyAMF 0.4 released at January 18th {{{ #!python test = pyamf.util.BufferedByteStream('abcdef') print test.read() print len(test) test.consume() print len(test) test.truncate() print len(test) }}} print out this in cpyamf: {{{ abcdef 6 6 0 }}} but this in pyamf: {{{ abcdef 6 0 0 }}} which is the right behavior? -- Comment(by thijs): Fixing markup. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 19 11:43:29 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 19 11:43:47 2009 Subject: [pyamf-tickets] #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer In-Reply-To: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> References: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> Message-ID: <044.f125aabdbbf7b94b993d4f720efc2c89@pyamf.org> #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer -------------------------+-------------------------------------------------- Reporter: sparkle | Owner: sparkle Type: defect | Status: assigned Priority: minor | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: review | -------------------------+-------------------------------------------------- Comment(by thijs): Haven't tested it yet and will continue the review later on but there's a typo in the comment of the test: {{{ #!python # move the strem pos to the end }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 19 16:39:15 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Mon Jan 19 16:39:31 2009 Subject: [pyamf-tickets] #438: Setup PyAMF rsync backup In-Reply-To: <033.4bccdfb705c5fd749ecc83f062fdf762@pyamf.org> References: <033.4bccdfb705c5fd749ecc83f062fdf762@pyamf.org> Message-ID: <042.21b65a28e872942ad881f472d18336c7@pyamf.org> #438: Setup PyAMF rsync backup ----------------------+----------------------------------------------------- Reporter: thijs | Owner: feisley Type: task | Status: assigned Priority: critical | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by thijs): * owner: thijs => feisley Comment: What kind of permissions? -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 20 12:49:47 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Tue Jan 20 12:50:05 2009 Subject: [pyamf-tickets] #434: need twisted client API using defer In-Reply-To: <035.985b1d3065feb21a2b37015ef0e62ae8@pyamf.org> References: <035.985b1d3065feb21a2b37015ef0e62ae8@pyamf.org> Message-ID: <044.b3806abfcb0112176c549dacce3ed964@pyamf.org> #434: need twisted client API using defer -------------------------+-------------------------------------------------- Reporter: cassidy | Owner: nick Type: enhancement | Status: accepted Priority: major | Milestone: 0.5 Component: Client | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by nick): * status: new => accepted Comment: Branching to source:pyamf/branches/twisted-client-434 -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 21 20:31:23 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Wed Jan 21 20:31:40 2009 Subject: [pyamf-tickets] #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer In-Reply-To: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> References: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> Message-ID: <044.6e99799e8b39ba1f104a078cc5786f63@pyamf.org> #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer -------------------------+-------------------------------------------------- Reporter: sparkle | Owner: thijs Type: defect | Status: assigned Priority: minor | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * owner: sparkle => thijs -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 22 18:13:00 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 22 18:13:19 2009 Subject: [pyamf-tickets] #452: Add more info to the README file Message-ID: <033.888e3e44b43d983069632b9b76a54e3a@pyamf.org> #452: Add more info to the README file ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: defect | Status: new Priority: minor | Milestone: 0.5 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ The [source:pyamf/trunk/README.txt] file currently mirrors the WikiStart page's content, but is missing the statements about the supported frameworks and cpyamf. -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 23 21:52:14 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 23 21:52:39 2009 Subject: [pyamf-tickets] #234: Expose the AMF request envelope In-Reply-To: <032.c69de8c132bf6695025a02b2f9d3dbc2@pyamf.org> References: <032.c69de8c132bf6695025a02b2f9d3dbc2@pyamf.org> Message-ID: <041.e4c565a78c6fefd4985e0981582fee85@pyamf.org> #234: Expose the AMF request envelope -------------------------+-------------------------------------------------- Reporter: nick | Owner: Type: enhancement | Status: assigned Priority: major | Milestone: 0.5 Component: Remoting | Version: 0.3 Keywords: hack | -------------------------+-------------------------------------------------- Comment(by thijs): See http://lists.pyamf.org/archives/users/2009-January/000883.html -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 29 23:32:57 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 29 23:33:10 2009 Subject: [pyamf-tickets] #453: am0.Encoder has a use_amf3 option that isn't used well Message-ID: <032.521b92f157bee9cd98bc05f38734f4a8@pyamf.org> #453: am0.Encoder has a use_amf3 option that isn't used well -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: new Priority: minor | Milestone: 0.4.1 Component: AMF0 | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Change it. -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 29 23:34:53 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 29 23:35:02 2009 Subject: [pyamf-tickets] #454: GAE adapter breaks if trying to encode non saved objects Message-ID: <032.968f5d1388c063b6e526f9d7766cffd4@pyamf.org> #454: GAE adapter breaks if trying to encode non saved objects ----------------------+----------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: new Priority: critical | Milestone: 0.4.1 Component: Adapter | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- because the `_key` attribute is ignored. -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 29 23:36:41 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 29 23:36:50 2009 Subject: [pyamf-tickets] #455: Check unicode __repr__ functions Message-ID: <032.ef23b661198cddb0194cde024560282d@pyamf.org> #455: Check unicode __repr__ functions ----------------------+----------------------------------------------------- Reporter: nick | Owner: nick Type: task | Status: new Priority: major | Milestone: 0.4.1 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- As the logger will fall over if this isn't handled carefully. -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 29 23:38:37 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 29 23:38:46 2009 Subject: [pyamf-tickets] #456: Remove _*_cache attributes from django objects Message-ID: <032.2306f4914cb69670f4b25abffe9a8217@pyamf.org> #456: Remove _*_cache attributes from django objects ----------------------+----------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.4.1 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Also the foreignkey attributes aren't being followed correctly. -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 29 23:40:38 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Thu Jan 29 23:40:46 2009 Subject: [pyamf-tickets] #457: Check django.db.models.TimeField encoding Message-ID: <032.59c54f0f959e95dad270e7764380f46f@pyamf.org> #457: Check django.db.models.TimeField encoding ----------------------+----------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.4.1 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Needs to be encoded as a `datetime.datetime`. -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 30 13:28:38 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 30 13:29:14 2009 Subject: [pyamf-tickets] #454: GAE adapter breaks if trying to encode non saved objects In-Reply-To: <032.968f5d1388c063b6e526f9d7766cffd4@pyamf.org> References: <032.968f5d1388c063b6e526f9d7766cffd4@pyamf.org> Message-ID: <041.36a7e5a3e331dc5d378443ca7159f7bc@pyamf.org> #454: GAE adapter breaks if trying to encode non saved objects ----------------------+----------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: accepted Priority: critical | Milestone: 0.4.1 Component: Adapter | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by nick): * status: new => accepted Comment: Branching to source:pyamf/branches/gae-non-saved-454 -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 30 13:57:24 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 30 13:57:31 2009 Subject: [pyamf-tickets] #458: generate exception when encoding duplicate keys Message-ID: <034.eb6e97af34aa1d35563ecaf250a42db8@pyamf.org> #458: generate exception when encoding duplicate keys -------------------------+-------------------------------------------------- Reporter: arman0 | Owner: nick Type: enhancement | Status: new Priority: blocker | Milestone: 0.4.1 Component: Encoder | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- {{{ >>> pyamf.decode(pyamf.encode({0:0, '0':1})).next() {u'0': 1} }}} My guess is that the user almost always has a bug when encoding a python dict which will result in duplicate AS object keys. Therefore, it would be help for pyamf to raise an exception in such cases. -arman -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 30 17:34:27 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Fri Jan 30 17:34:35 2009 Subject: [pyamf-tickets] #458: generate exception when encoding duplicate keys In-Reply-To: <034.eb6e97af34aa1d35563ecaf250a42db8@pyamf.org> References: <034.eb6e97af34aa1d35563ecaf250a42db8@pyamf.org> Message-ID: <043.5ff5fe7d91896a8f066d1715914193cf@pyamf.org> #458: generate exception when encoding duplicate keys -------------------------+-------------------------------------------------- Reporter: arman0 | Owner: nick Type: enhancement | Status: new Priority: blocker | Milestone: 0.4.1 Component: Encoder | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Description changed by thijs: Old description: > {{{ > >>> pyamf.decode(pyamf.encode({0:0, '0':1})).next() > {u'0': 1} > }}} > My guess is that the user almost always has a bug when encoding a python > dict which will result in duplicate AS object keys. Therefore, it would > be help for pyamf to raise an exception in such cases. > > -arman New description: {{{ #!python >>> pyamf.decode(pyamf.encode({0:0, '0':1})).next() {u'0': 1} }}} My guess is that the user almost always has a bug when encoding a python dict which will result in duplicate AS object keys. Therefore, it would be help for pyamf to raise an exception in such cases. -arman -- -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 31 14:13:12 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 31 14:13:19 2009 Subject: [pyamf-tickets] #434: need twisted client API using defer In-Reply-To: <035.985b1d3065feb21a2b37015ef0e62ae8@pyamf.org> References: <035.985b1d3065feb21a2b37015ef0e62ae8@pyamf.org> Message-ID: <044.22ba69a6a145667d664a64bee8202838@pyamf.org> #434: need twisted client API using defer -------------------------+-------------------------------------------------- Reporter: cassidy | Owner: nick Type: enhancement | Status: accepted Priority: major | Milestone: 0.5 Component: Client | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Comment(by cassidy): Thanks. I integrated your twisted client in my application [1] and it seems to work great! [1] https://launchpad.net/elisa-plugin-rtbf -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 31 20:39:16 2009 From: tickets at pyamf.org (tickets@pyamf.org) Date: Sat Jan 31 20:39:24 2009 Subject: [pyamf-tickets] #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer In-Reply-To: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> References: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> Message-ID: <044.6107264c418c7a930538ccde5a3a51f1@pyamf.org> #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer -------------------------+-------------------------------------------------- Reporter: sparkle | Owner: thijs Type: defect | Status: assigned Priority: minor | Milestone: 0.4.1 Component: C-Extension | Version: 0.4 Keywords: review | -------------------------+-------------------------------------------------- Changes (by thijs): * milestone: 0.5 => 0.4.1 -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 1 22:50:24 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 01 Jan 2009 21:50:24 -0000 Subject: [pyamf-tickets] #343: Refactor the test suite to be python implementation independent In-Reply-To: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> References: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> Message-ID: <041.449e177701411c9fbc239d32308554b9@pyamf.org> #343: Refactor the test suite to be python implementation independent -------------------------+-------------------------------------------------- Reporter: nick | Owner: thijs Type: enhancement | Status: assigned Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.3.1 Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * keywords: => review * status: new => assigned * owner: nick => thijs Comment: All tests have now been refactored to be python implementation independent. There are still Jython tests failing but these are unrelated. -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 16:13:51 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 02 Jan 2009 15:13:51 -0000 Subject: [pyamf-tickets] #398: Add SQLAlchemy buildstep In-Reply-To: <033.5541fbd65b967b59eb46f6c8811a5633@pyamf.org> References: <033.5541fbd65b967b59eb46f6c8811a5633@pyamf.org> Message-ID: <042.cb068bb82f27f91063061f028625e4da@pyamf.org> #398: Add SQLAlchemy buildstep ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: closed Priority: major | Milestone: 0.4 Component: Testing | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by thijs): * status: accepted => closed * resolution: => fixed Old description: > The upcoming SQLAlchemyAdapter should be tested on both SQLAlchemy 0.4.x > and the latest 0.5.x New description: The upcoming SQLAlchemyAdapter should be tested on both SQLAlchemy 0.4.x and the latest 0.5.x release. -- Comment: Fixed with r1945 -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 16:37:15 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 02 Jan 2009 15:37:15 -0000 Subject: [pyamf-tickets] #409: Update copyright headers In-Reply-To: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> References: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> Message-ID: <042.43283f6d1a7e10bfca2480a40e747893@pyamf.org> #409: Update copyright headers ---------------------------+------------------------------------------------ Reporter: thijs | Owner: feisley Type: defect | Status: accepted Priority: blocker | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Changes (by feisley): * status: new => accepted * owner: thijs => feisley -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 16:47:20 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 02 Jan 2009 15:47:20 -0000 Subject: [pyamf-tickets] #410: Support for SQLAlchemy 0.4.0 Message-ID: <032.1f628095e45e344a1a6d84bb2b92080f@pyamf.org> #410: Support for SQLAlchemy 0.4.0 ----------------------+----------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- When using SQLAlchemy 0.4.0 the following traceback occurs when running the test suite. {{{ #!python Traceback (most recent call last): File "./setup.py", line 139, in "Topic :: Software Development :: Libraries :: Python Modules", File "C:\Python25\lib\distutils\core.py", line 151, in setup dist.run_commands() File "C:\Python25\lib\distutils\dist.py", line 974, in run_commands self.run_command(cmd) File "C:\Python25\lib\distutils\dist.py", line 994, in run_command cmd_obj.run() File "build\bdist.win32\egg\setuptools\command\test.py", line 121, in run File "build\bdist.win32\egg\setuptools\command\test.py", line 101, in with_project_on_sys_path File "./setup.py", line 35, in run_tests self.run_twisted() File "./setup.py", line 25, in run_twisted r.run(suite()) File "c:\buildbot\pyamf\x86-win2003-py25\build\pyamf\tests\__init__.py", line 35, in suite suite.addTest(mod.suite()) File "c:\buildbot\pyamf\x86-win2003-py25\build\pyamf\tests\test_adapters.py", line 78, in suite mod = __import__('.'.join(base_mod)) File "c:\buildbot\pyamf\x86-win2003-py25\build\pyamf\tests\adapters\test_sqlalchemy.py", line 17, in import pyamf.flex File "c:\buildbot\pyamf\x86-win2003-py25\build\pyamf\flex\__init__.py", line 203, in metadata=['external', 'amf3']) File "c:\buildbot\pyamf\x86-win2003-py25\build\pyamf\__init__.py", line 816, in register_class alias_klass = util.get_class_alias(klass) File "c:\buildbot\pyamf\x86-win2003-py25\build\pyamf\util\__init__.py", line 584, in get_class_alias if kl(klass) is True: File "c:\buildbot\pyamf\x86-win2003-py25\build\pyamf\adapters\_sqlalchemy.py", line 125, in is_class_sa_mapped class_mapper(klass) File "c:\buildbot\pyamf\x86-win2003-py25\build\sqlalchemy\orm\util.py", line 386, in class_mapper raise exceptions.InvalidRequestError("Class '%s' entity name '%s' has no mapper associated with it" % (class_.__name__, entity_name)) sqlalchemy.exceptions.InvalidRequestError: Class 'ArrayCollection' entity name 'None' has no mapper associated with it }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 16:53:04 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 02 Jan 2009 15:53:04 -0000 Subject: [pyamf-tickets] #411: GAE buildslave - ValueError: No JSON object could be decoded Message-ID: <033.983707531c8c10d93bfb23317d9c9bff@pyamf.org> #411: GAE buildslave - ValueError: No JSON object could be decoded ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.5 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Sometimes the GoogleAppEngine buildslave fails with the following error: {{{ #!python Traceback (most recent call last): File "client.py", line 216, in x = GAETestRunner(options.url) File "client.py", line 71, in __init__ self.get_all_tests() File "client.py", line 87, in get_all_tests ret = simplejson.loads(self._get_url('tests')) File "build/bdist.linux-x86_64/egg/simplejson/__init__.py", line 262, in loads File "build/bdist.linux-x86_64/egg/simplejson/decoder.py", line 251, in decode File "build/bdist.linux-x86_64/egg/simplejson/decoder.py", line 270, in raw_decode ValueError: No JSON object could be decoded }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 17:00:46 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 02 Jan 2009 16:00:46 -0000 Subject: [pyamf-tickets] #410: Support for SQLAlchemy 0.4.0 In-Reply-To: <032.1f628095e45e344a1a6d84bb2b92080f@pyamf.org> References: <032.1f628095e45e344a1a6d84bb2b92080f@pyamf.org> Message-ID: <041.8f123244aed365b3e5547ac2fdcc6475@pyamf.org> #410: Support for SQLAlchemy 0.4.0 ----------------------+----------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: accepted Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by nick): * status: new => accepted Comment: Branching to source:pyamf/branches/sqlalchemy-four-point-oh-410. -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 17:07:54 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 02 Jan 2009 16:07:54 -0000 Subject: [pyamf-tickets] #409: Update copyright headers In-Reply-To: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> References: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> Message-ID: <042.93cccee05c66a04d37f7c0bc65cf9f1a@pyamf.org> #409: Update copyright headers ---------------------------+------------------------------------------------ Reporter: thijs | Owner: feisley Type: defect | Status: accepted Priority: blocker | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Comment(by feisley): Branching to source:pyamf/branches/2009-copyright-409 -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 17:11:40 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 02 Jan 2009 16:11:40 -0000 Subject: [pyamf-tickets] #412: Cosmetic updates for GAE buildslave Message-ID: <033.bec95add736ebd98febc2855279b9457@pyamf.org> #412: Cosmetic updates for GAE buildslave -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: new Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Some cosmetic changes to make the output more readable: 1. The app starts with a checkout like this: {{{ A . A app A app/manage.py A app/app.yaml A app/assets }}} Would be better if it first prints a start message with the full repository path like: {{{ Google App Engine buildslave (v0.x) ====================== 1. Google App Engine - SVN Checkout: http://svn.pyamf.org/pyamf/trunk A . A app A app/manage.py A app/app.yaml A app/assets }}} 2. When it finishes the first checkout it goes on with the next checkout like: {{{ A client.py Exported revision 1947. A app/pyamf A app/pyamf/tests }}} This would read better (like the first checkout): {{{ A client.py Exported revision 1947. 2. PyAMF - SVN Checkout: http://svn.etc A app/pyamf A app/pyamf/tests }}} 3. Add a break after the checkout: {{{ A app/pyamf/flex/__init__.py Exported revision 1947. Scanning files on local disk. }}} 4. Add these statements on their own line and separate them with a break: {{{ Password for gae-buildslave at pyamf.org: Traceback (most recent call last): }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 17:27:27 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 02 Jan 2009 16:27:27 -0000 Subject: [pyamf-tickets] #409: Update copyright headers In-Reply-To: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> References: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> Message-ID: <042.e20317d3f285112d91b0f56b0d4d760e@pyamf.org> #409: Update copyright headers ---------------------------+------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: review | ---------------------------+------------------------------------------------ Changes (by feisley): * keywords: => review * status: accepted => assigned * owner: feisley => nick Comment: Changes complete, please review. -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 17:30:37 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 02 Jan 2009 16:30:37 -0000 Subject: [pyamf-tickets] #413: Cosmetic updates for GAE buildslave In-Reply-To: <033.ae8cde3cf18b67a5def408e3debaa669@pyamf.org> References: <033.ae8cde3cf18b67a5def408e3debaa669@pyamf.org> Message-ID: <042.acb32a4e4ad558e678b6ce5118605a4a@pyamf.org> #413: Cosmetic updates for GAE buildslave --------------------------+------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: closed Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.4 Resolution: duplicate | Keywords: --------------------------+------------------------------------------------- Changes (by thijs): * status: new => closed * resolution: => duplicate Comment: #412 -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 17:32:18 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 02 Jan 2009 16:32:18 -0000 Subject: [pyamf-tickets] #410: Support for SQLAlchemy 0.4.0 In-Reply-To: <032.1f628095e45e344a1a6d84bb2b92080f@pyamf.org> References: <032.1f628095e45e344a1a6d84bb2b92080f@pyamf.org> Message-ID: <041.26bdad544ba0e9e9c8db4a049bc4846b@pyamf.org> #410: Support for SQLAlchemy 0.4.0 ----------------------+----------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: accepted Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Comment(by thijs): Fixed with r1951 -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 17:32:36 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 02 Jan 2009 16:32:36 -0000 Subject: [pyamf-tickets] #410: Support for SQLAlchemy 0.4.0 In-Reply-To: <032.1f628095e45e344a1a6d84bb2b92080f@pyamf.org> References: <032.1f628095e45e344a1a6d84bb2b92080f@pyamf.org> Message-ID: <041.c863995d3bd84214d36f30425e14e88a@pyamf.org> #410: Support for SQLAlchemy 0.4.0 -----------------------+---------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: closed Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Resolution: fixed | Keywords: -----------------------+---------------------------------------------------- Changes (by thijs): * status: accepted => closed * resolution: => fixed -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 17:38:52 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 02 Jan 2009 16:38:52 -0000 Subject: [pyamf-tickets] #409: Update copyright headers In-Reply-To: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> References: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> Message-ID: <042.c4312f188d832588f576a3a0c202df36@pyamf.org> #409: Update copyright headers ---------------------------+------------------------------------------------ Reporter: thijs | Owner: feisley Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Changes (by nick): * keywords: review => * owner: nick => feisley Comment: Updates look good, please merge. -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 18:08:50 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 02 Jan 2009 17:08:50 -0000 Subject: [pyamf-tickets] #409: Update copyright headers In-Reply-To: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> References: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> Message-ID: <042.e9e45c2d1f286a63a02ab94c8c01e51c@pyamf.org> #409: Update copyright headers ---------------------------+------------------------------------------------ Reporter: thijs | Owner: feisley Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Comment(by feisley): We forgot to do the examples so... Branching to source:examples/branches/2009-copyright-409 -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 18:09:43 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 02 Jan 2009 17:09:43 -0000 Subject: [pyamf-tickets] #409: Update copyright headers In-Reply-To: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> References: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> Message-ID: <042.837b7d05e8f9e19a1b3268da33d003c0@pyamf.org> #409: Update copyright headers ---------------------------+------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: review | ---------------------------+------------------------------------------------ Changes (by feisley): * keywords: => review * owner: feisley => nick -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 18:17:35 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 02 Jan 2009 17:17:35 -0000 Subject: [pyamf-tickets] #409: Update copyright headers In-Reply-To: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> References: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> Message-ID: <042.66b312314ac22344941bfab36a01b164@pyamf.org> #409: Update copyright headers ---------------------------+------------------------------------------------ Reporter: thijs | Owner: darkhorse Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Changes (by nick): * keywords: review => * owner: nick => darkhorse Comment: Examples look good too :) -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 19:49:12 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 02 Jan 2009 18:49:12 -0000 Subject: [pyamf-tickets] #409: Update copyright headers In-Reply-To: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> References: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> Message-ID: <042.4845e7a1b423ea3dc60700b18a2a6ada@pyamf.org> #409: Update copyright headers ---------------------------+------------------------------------------------ Reporter: thijs | Owner: feisley Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Changes (by nick): * owner: darkhorse => feisley -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 19:50:50 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 02 Jan 2009 18:50:50 -0000 Subject: [pyamf-tickets] #409: Update copyright headers In-Reply-To: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> References: <033.d17772f73f90c8ab35a59676060dffb1@pyamf.org> Message-ID: <042.558f9bb2910b0397c911c147e8ad34e6@pyamf.org> #409: Update copyright headers ----------------------------+----------------------------------------------- Reporter: thijs | Owner: feisley Type: defect | Status: closed Priority: blocker | Milestone: 0.4 Component: Documentation | Version: 0.4 Resolution: fixed | Keywords: ----------------------------+----------------------------------------------- Changes (by feisley): * status: assigned => closed * resolution: => fixed Comment: Fixed in r1957 and r1959 -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 2 19:58:20 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 02 Jan 2009 18:58:20 -0000 Subject: [pyamf-tickets] #320: UnknownClassAlias: NetDebugConfig In-Reply-To: <033.e56ef1fb78caf978d51f8969004d5db1@pyamf.org> References: <033.e56ef1fb78caf978d51f8969004d5db1@pyamf.org> Message-ID: <042.571e232e8a005792b5df8062ca1db942@pyamf.org> #320: UnknownClassAlias: NetDebugConfig ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: defect | Status: assigned Priority: minor | Milestone: 0.5 Component: Remoting | Version: 0.3.1 Keywords: | ----------------------+----------------------------------------------------- Changes (by nick): * owner: nick => thijs * status: new => assigned Comment: Using 0.4rc2 this now gives: {{{ #!python }}} So this is now invalid? -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 3 14:05:59 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 03 Jan 2009 13:05:59 -0000 Subject: [pyamf-tickets] #353: Bytearray test hack showing in Jython In-Reply-To: <033.7ab88d6b724bc380e58306e1cbfc2367@pyamf.org> References: <033.7ab88d6b724bc380e58306e1cbfc2367@pyamf.org> Message-ID: <042.aad050a3b93f48a2c7b3138ce047c6dc@pyamf.org> #353: Bytearray test hack showing in Jython ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: task | Status: accepted Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.3.1 Keywords: | ---------------------+------------------------------------------------------ Changes (by nick): * priority: major => minor * status: new => accepted * type: defect => task Comment: This turns out to be a compatibility issue with Jython. It raises `java.util.zip.DataFormatException` instead of zlib.error. I have raised this issue in Jython's [http://bugs.jython.org/issue1217 bug tracker]. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 4 00:36:31 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 03 Jan 2009 23:36:31 -0000 Subject: [pyamf-tickets] #343: Refactor the test suite to be python implementation independent In-Reply-To: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> References: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> Message-ID: <041.06c268b9c818c3a82b06f11185e2004d@pyamf.org> #343: Refactor the test suite to be python implementation independent -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: assigned Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.3.1 Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * keywords: review => * owner: thijs => nick Comment: EchoTest dies for me with: {{{ AMF error received (after 0.02 sec): description: error code: Channel.Call.Failed details: NetConnection.Call.Failed: HTTP: Failed Error: ReferenceError: Error #1069: Property 0 not found on String and there is no default value. at org.red5.samples.echo::EchoTest/onRemotingError() at echotest/__echoService_fault() at flash.events::EventDispatcher/dispatchEventFunction() at flash.events::EventDispatcher/dispatchEvent() at mx.rpc::AbstractService/dispatchEvent() at mx.rpc.remoting.mxml::RemoteObject/dispatchEvent() at mx.rpc::AbstractOperation/http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent() at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faultHandler() at mx.rpc::Responder/fault() at mx.rpc::AsyncRequest/fault() at NetConnectionMessageResponder/channelFaultHandler() at flash.events::EventDispatcher/dispatchEventFunction() at flash.events::EventDispatcher/dispatchEvent() at mx.messaging.channels::AMFChannel/statusHandler() }}} Might be related to an old version of the EchoTest swf. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 4 04:33:21 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 04 Jan 2009 03:33:21 -0000 Subject: [pyamf-tickets] #388: Exclude third-party class(es) in our API documentation (was: Exclude Twisted class(es) in our API documentation) In-Reply-To: <033.f71ccf163a21187c1cf6d3618880074f@pyamf.org> References: <033.f71ccf163a21187c1cf6d3618880074f@pyamf.org> Message-ID: <042.3b00c3a09d96c36eea970ce052c09221@pyamf.org> #388: Exclude third-party class(es) in our API documentation ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: defect | Status: accepted Priority: major | Milestone: 0.5 Component: Documentation | Version: 0.3.1 Keywords: | ---------------------------+------------------------------------------------ -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 4 04:37:08 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 04 Jan 2009 03:37:08 -0000 Subject: [pyamf-tickets] #414: Support for the NetConnection Debugger panel Message-ID: <033.fb87f58ac69af005f99f0918b90cd93f@pyamf.org> #414: Support for the NetConnection Debugger panel ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: new Priority: minor | Milestone: At some point Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- The NetDebug object is the ActionScript 2.0 object that powers the NetConnection Debugger panel, allowing a developer to view and trace output to and from the application server. Would be nice to have this standard Remoting class available in PyAMF (like AMFPHP and others). -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 4 04:39:16 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 04 Jan 2009 03:39:16 -0000 Subject: [pyamf-tickets] #320: UnknownClassAlias issue with .sol files (was: UnknownClassAlias: NetDebugConfig) In-Reply-To: <033.e56ef1fb78caf978d51f8969004d5db1@pyamf.org> References: <033.e56ef1fb78caf978d51f8969004d5db1@pyamf.org> Message-ID: <042.df5c76447bc7ce26ca0aeeb4814f67ab@pyamf.org> #320: UnknownClassAlias issue with .sol files ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: defect | Status: assigned Priority: minor | Milestone: 0.5 Component: Shared Object | Version: 0.3.1 Keywords: | ---------------------------+------------------------------------------------ Changes (by thijs): * component: Remoting => Shared Object Old description: > The > [http://etutorials.org/Macromedia/Fash+remoting.+the+definitive+guide/Part+III+Advanced+Flash+Remoting/Chapter+15.+Flash+Remoting+API/NetDebug+Object/ > NetDebug] object is the !ActionScript 2.0 object that powers the > !NetConnection Debugger panel, allowing a developer to view and trace > output to and from the application server. Would be nice to have this > standard Remoting class available in PyAMF (like AMFPHP and others). > While testing the attached .sol [attachment:TestMovie_Config_Info.sol > file] like this: > > {{{ > #!python > from pyamf import sol > > path = 'TestMovie_Config_Info.sol' > lso = sol.load(path) > > print lso > }}} > > I'm getting this error: > {{{ > Traceback (most recent call last):', ' > File "/pyamf/trunk/pyamf/remoting/amf0.py", line 100, in __call__ > response.body = self._getBody(request, response, service_request, *args, > **kwargs)', ' > File "/pyamf/trunk/pyamf/remoting/amf0.py", line 56, in _getBody > return self.gateway.callServiceRequest(service_request, *request.body, > **kwargs)', ' > File "/pyamf/trunk/pyamf/remoting/gateway/__init__.py", line 471, in > callServiceRequest return service_request(*args)', ' > File "/pyamf/trunk/pyamf/remoting/gateway/__init__.py", line 208, in > __call__ return self.service(self.method, args)', ' > File "/pyamf/trunk/pyamf/remoting/gateway/__init__.py", line 110, in > __call__ return func(*params)', ' > File "/workspace/pyamf-temp2/sol/python/service.py", line 90, in > getDetails lso = sol.load(path)', ' > File "/pyamf/trunk/pyamf/sol.py", line 163, in load name, values = > decode(f.read())', ' > File "/pyamf/trunk/pyamf/sol.py", line 83, in decode value = > decoder.readElement()', ' > File "/pyamf/trunk/pyamf/__init__.py", line 486, in readElement return > func()', ' > File "/pyamf/trunk/pyamf/amf0.py", line 296, in readTypedObject alias > = pyamf.load_class(classname)', ' > File "/pyamf/trunk/pyamf/__init__.py", line 777, in load_class raise > UnknownClassAlias, "Unknown alias %s" % alias', > 'UnknownClassAlias: Unknown alias NetDebugConfig' > }}} New description: While testing the attached .sol [attachment:TestMovie_Config_Info.sol file] like this: {{{ #!python from pyamf import sol path = 'TestMovie_Config_Info.sol' lso = sol.load(path) print lso }}} I'm getting this error: {{{ Traceback (most recent call last):', ' File "/pyamf/trunk/pyamf/remoting/amf0.py", line 100, in __call__ response.body = self._getBody(request, response, service_request, *args, **kwargs)', ' File "/pyamf/trunk/pyamf/remoting/amf0.py", line 56, in _getBody return self.gateway.callServiceRequest(service_request, *request.body, **kwargs)', ' File "/pyamf/trunk/pyamf/remoting/gateway/__init__.py", line 471, in callServiceRequest return service_request(*args)', ' File "/pyamf/trunk/pyamf/remoting/gateway/__init__.py", line 208, in __call__ return self.service(self.method, args)', ' File "/pyamf/trunk/pyamf/remoting/gateway/__init__.py", line 110, in __call__ return func(*params)', ' File "/workspace/pyamf-temp2/sol/python/service.py", line 90, in getDetails lso = sol.load(path)', ' File "/pyamf/trunk/pyamf/sol.py", line 163, in load name, values = decode(f.read())', ' File "/pyamf/trunk/pyamf/sol.py", line 83, in decode value = decoder.readElement()', ' File "/pyamf/trunk/pyamf/__init__.py", line 486, in readElement return func()', ' File "/pyamf/trunk/pyamf/amf0.py", line 296, in readTypedObject alias = pyamf.load_class(classname)', ' File "/pyamf/trunk/pyamf/__init__.py", line 777, in load_class raise UnknownClassAlias, "Unknown alias %s" % alias', 'UnknownClassAlias: Unknown alias NetDebugConfig' }}} -- Comment: Updating ticket description and moving most of it to a second ticket (#414). -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 4 04:42:14 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 04 Jan 2009 03:42:14 -0000 Subject: [pyamf-tickets] #320: UnknownClassAlias issue with .sol files In-Reply-To: <033.e56ef1fb78caf978d51f8969004d5db1@pyamf.org> References: <033.e56ef1fb78caf978d51f8969004d5db1@pyamf.org> Message-ID: <042.0217e074eb516616f630fa3040f8b711@pyamf.org> #320: UnknownClassAlias issue with .sol files ----------------------------+----------------------------------------------- Reporter: thijs | Owner: thijs Type: defect | Status: closed Priority: minor | Milestone: 0.4 Component: Shared Object | Version: 0.3.1 Resolution: fixed | Keywords: ----------------------------+----------------------------------------------- Changes (by thijs): * status: assigned => closed * resolution: => fixed * milestone: 0.5 => 0.4 Comment: I'm getting a similar output for the 2nd attached file. Replying to [comment:2 nick]: > So this is now invalid? I'm marking it as fixed cause it was broken before..... ;) -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 4 04:44:11 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 04 Jan 2009 03:44:11 -0000 Subject: [pyamf-tickets] #377: Porting C-Extension Module to Python 3.0 In-Reply-To: <033.89ff9943ac068869772f5a3137a306d4@pyamf.org> References: <033.89ff9943ac068869772f5a3137a306d4@pyamf.org> Message-ID: <042.521230a220f9e97e4ed7581b52edfcba@pyamf.org> #377: Porting C-Extension Module to Python 3.0 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: assigned Priority: minor | Milestone: Python 3000 Component: C-Extension | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * priority: major => minor * type: task => enhancement -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 4 04:47:08 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 04 Jan 2009 03:47:08 -0000 Subject: [pyamf-tickets] #123: Create benchmark sub-project In-Reply-To: <033.6c9ac6cdf6866be5fdb85665218e2d22@pyamf.org> References: <033.6c9ac6cdf6866be5fdb85665218e2d22@pyamf.org> Message-ID: <042.8233697eceb8dcc60792ba07dc268a89@pyamf.org> #123: Create benchmark sub-project ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: task | Status: new Priority: major | Milestone: 0.5 Component: Testing | Version: 0.1a Keywords: | ---------------------+------------------------------------------------------ Changes (by thijs): * milestone: At some point => 0.5 Comment: Good to have this now that there's a C-extension. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 01:04:25 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 05 Jan 2009 00:04:25 -0000 Subject: [pyamf-tickets] #415: Jython C-extension warning Message-ID: <033.73320f1720c8c11616fd38b85c4e88fe@pyamf.org> #415: Jython C-extension warning -------------------------+-------------------------------------------------- Reporter: thijs | Owner: gerard Type: enhancement | Status: new Priority: major | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Zope 3.5 or newer has a C-extension warning for Jython, might be a good idea to have something similar, instead of silently skipping the build_ext. {{{ ******************************************************************************** WARNING: An optional code optimization (C extension) could not be compiled. Optimizations for this package will not be available! Compiling extensions is not supported on Jython ******************************************************************************** }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 01:07:22 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 05 Jan 2009 00:07:22 -0000 Subject: [pyamf-tickets] #415: Jython C-extension warning In-Reply-To: <033.73320f1720c8c11616fd38b85c4e88fe@pyamf.org> References: <033.73320f1720c8c11616fd38b85c4e88fe@pyamf.org> Message-ID: <042.e9d9faca6434a30137efae96e3dd7a00@pyamf.org> #415: Jython C-extension warning -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: assigned Priority: minor | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * owner: gerard => nick * priority: major => minor * status: new => assigned -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 02:12:24 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 05 Jan 2009 01:12:24 -0000 Subject: [pyamf-tickets] #415: Jython C-extension warning In-Reply-To: <033.73320f1720c8c11616fd38b85c4e88fe@pyamf.org> References: <033.73320f1720c8c11616fd38b85c4e88fe@pyamf.org> Message-ID: <042.5cf063b8bfd0ac89374cab368c60bedc@pyamf.org> #415: Jython C-extension warning -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: assigned Priority: minor | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Description changed by thijs: Old description: > Zope 3.5 or newer has a C-extension warning for Jython, might be a good > idea to have something similar, instead of silently skipping the > build_ext. > > {{{ > ******************************************************************************** > WARNING: > > An optional code optimization (C extension) could not be > compiled. > > Optimizations for this package will not be available! > > Compiling extensions is not supported on Jython > ******************************************************************************** > }}} New description: Zope Interface 3.5 or newer has a C-extension warning for Jython, might be a good idea to have something similar, instead of silently skipping the build_ext. {{{ ******************************************************************************** WARNING: An optional code optimization (C extension) could not be compiled. Optimizations for this package will not be available! Compiling extensions is not supported on Jython ******************************************************************************** }}} -- -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 12:04:45 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 05 Jan 2009 11:04:45 -0000 Subject: [pyamf-tickets] #416: Release 0.4rc2 Message-ID: <033.fb458379f13bcedeea8fdf3c6d9ac259@pyamf.org> #416: Release 0.4rc2 ---------------------+------------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: new Priority: blocker | Milestone: 0.4 Component: Website | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Release PyAMF 0.4rc2 to the world. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 12:06:03 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 05 Jan 2009 11:06:03 -0000 Subject: [pyamf-tickets] #417: Release 0.4 final Message-ID: <033.a073f642c43fd4a9856ebdd72d5e1b46@pyamf.org> #417: Release 0.4 final ---------------------+------------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: new Priority: blocker | Milestone: 0.4 Component: Website | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Release 0.4 final to the world and maintain the [source:pyamf/branches/release-0.4 0.4] branch. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 12:59:21 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 05 Jan 2009 11:59:21 -0000 Subject: [pyamf-tickets] #418: Setup nightly builds page Message-ID: <033.c4ed5a69d76333c7af3ec68f3aefd46c@pyamf.org> #418: Setup nightly builds page ---------------------+------------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: new Priority: major | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Would be nice to have something similar to [http://nightly.webkit.org webkit]'s nightly builds page. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 18:22:24 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 05 Jan 2009 17:22:24 -0000 Subject: [pyamf-tickets] #407: Update SQLAlchemy Adapter docs In-Reply-To: <033.29e29526964e0174ddcd46cae5cc0be1@pyamf.org> References: <033.29e29526964e0174ddcd46cae5cc0be1@pyamf.org> Message-ID: <042.d47fb0aa40cc91a0228ae18d1d1dd4f2@pyamf.org> #407: Update SQLAlchemy Adapter docs ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: assigned Priority: major | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: review | ---------------------------+------------------------------------------------ Comment(by dthompso): I just copy and pasted from my code that uses a custom class that extends AbstractOperation. I'll change the example to Operation. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 19:18:59 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 05 Jan 2009 18:18:59 -0000 Subject: [pyamf-tickets] #407: Update SQLAlchemy Adapter docs In-Reply-To: <033.29e29526964e0174ddcd46cae5cc0be1@pyamf.org> References: <033.29e29526964e0174ddcd46cae5cc0be1@pyamf.org> Message-ID: <042.0ca9655703e3b14fe064525b497b7a3f@pyamf.org> #407: Update SQLAlchemy Adapter docs ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: assigned Priority: major | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: review | ---------------------------+------------------------------------------------ Comment(by dthompso): I changed the example to use RemoteObject in the methods. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 20:57:43 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 05 Jan 2009 19:57:43 -0000 Subject: [pyamf-tickets] #419: Put the changelog in the API docs Message-ID: <033.209be78cfaf0e68649600fc3e938e6ea@pyamf.org> #419: Put the changelog in the API docs ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: enhancement | Status: new Priority: major | Milestone: 0.5 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Would be nice to have the [source:pyamf/trunk/CHANGES.txt changelog] (and perhaps more files) generated to html and included in the API docs. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 21:00:33 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 05 Jan 2009 20:00:33 -0000 Subject: [pyamf-tickets] #420: Create example that uses the SQLAlchemy Adapter Message-ID: <033.50980369e7f89a7c2776b18e6efa6bcf@pyamf.org> #420: Create example that uses the SQLAlchemy Adapter ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: new Priority: major | Milestone: 0.5 Component: Examples | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Now that there's a [wiki:SQLAlchemyAdapter] it would be nice to have a python/flex|flash|air example that shows the use of the adapter. Could be anything really, perhaps some fictional address book thing, allowing you to delete/update/remove contacts? -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 21:03:50 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 05 Jan 2009 20:03:50 -0000 Subject: [pyamf-tickets] #420: Create example that uses the SQLAlchemy Adapter In-Reply-To: <033.50980369e7f89a7c2776b18e6efa6bcf@pyamf.org> References: <033.50980369e7f89a7c2776b18e6efa6bcf@pyamf.org> Message-ID: <042.3e665f5210ff47f36ffa8dbca054df2d@pyamf.org> #420: Create example that uses the SQLAlchemy Adapter ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: new Priority: major | Milestone: 0.5 Component: Examples | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by thijs): * cc: dthompso (added) Comment: Also see #407, which means the [wiki:SQLAlchemyAdapter] page needs to be updated when this ticket closes. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 21:05:22 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 05 Jan 2009 20:05:22 -0000 Subject: [pyamf-tickets] #416: Release 0.4rc2 In-Reply-To: <033.fb458379f13bcedeea8fdf3c6d9ac259@pyamf.org> References: <033.fb458379f13bcedeea8fdf3c6d9ac259@pyamf.org> Message-ID: <042.f195e15d0d76a578851e6b2cec8b57e8@pyamf.org> #416: Release 0.4rc2 ---------------------+------------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: accepted Priority: blocker | Milestone: 0.4 Component: Website | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Changes (by thijs): * status: new => accepted Comment: I updated the release date (today) in r1979, and uploaded new tarballs to the server. Will now update the [wiki:Download] page. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 21:11:45 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 05 Jan 2009 20:11:45 -0000 Subject: [pyamf-tickets] #421: Add note about optional adapter/gateway dependencies in the installation instructions Message-ID: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> #421: Add note about optional adapter/gateway dependencies in the installation instructions ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: enhancement | Status: new Priority: major | Milestone: 0.5 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Would be good to point out the various dependencies in the [source:pyamf/trunk/INSTALL.txt INSTALL.txt] and also including url's on the [wiki:Install] page. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 21:16:09 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 05 Jan 2009 20:16:09 -0000 Subject: [pyamf-tickets] #407: Update SQLAlchemy Adapter docs In-Reply-To: <033.29e29526964e0174ddcd46cae5cc0be1@pyamf.org> References: <033.29e29526964e0174ddcd46cae5cc0be1@pyamf.org> Message-ID: <042.088629d4d26f6f440562cefa0c5b6da3@pyamf.org> #407: Update SQLAlchemy Adapter docs ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: accepted Priority: major | Milestone: 0.5 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Changes (by thijs): * keywords: review => * status: assigned => accepted * milestone: 0.4 => 0.5 Comment: Replying to [comment:4 dthompso]: > I changed the example to use RemoteObject in the methods. Thanks. I opened #420 for a complete example in [source:examples/trunk] and will close this ticket when we finished that one. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 5 21:19:30 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 05 Jan 2009 20:19:30 -0000 Subject: [pyamf-tickets] #416: Release 0.4rc2 In-Reply-To: <033.fb458379f13bcedeea8fdf3c6d9ac259@pyamf.org> References: <033.fb458379f13bcedeea8fdf3c6d9ac259@pyamf.org> Message-ID: <042.fe626168bcc215a0a068797fd353148d@pyamf.org> #416: Release 0.4rc2 ---------------------+------------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: accepted Priority: blocker | Milestone: 0.4 Component: Website | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Comment(by thijs): Download page is fixed, the blog post is also ready, which will be used for the announce mails to lists.pyamf.org. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 6 04:11:56 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 06 Jan 2009 03:11:56 -0000 Subject: [pyamf-tickets] #422: Add read/write_24bit_uint to util.DataTypeMixIn. Message-ID: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> #422: Add read/write_24bit_uint to util.DataTypeMixIn. ---------------------+------------------------------------------------------ Reporter: nick | Owner: nick Type: defect | Status: new Priority: minor | Milestone: 0.5 Component: Utility | Version: Keywords: | ---------------------+------------------------------------------------------ Not used so much in PyAMF but useful as an all-rounder and to be part of cpyamf -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 6 04:16:18 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 06 Jan 2009 03:16:18 -0000 Subject: [pyamf-tickets] #423: Add a consume method that will chop the head off the data stream at the current stream position. Message-ID: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> #423: Add a consume method that will chop the head off the data stream at the current stream position. ---------------------+------------------------------------------------------ Reporter: nick | Owner: nick Type: defect | Status: new Priority: minor | Milestone: 0.5 Component: Utility | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ The areas that will be affected: `pyamf.util.StringIOProxy` `cpyamf.util.BufferedByteStream` -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 6 04:17:42 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 06 Jan 2009 03:17:42 -0000 Subject: [pyamf-tickets] #424: Move IndexedCollection to cpyamf Message-ID: <032.a2f076997e96a30e1e40a8a864c5d2e0@pyamf.org> #424: Move IndexedCollection to cpyamf -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: new Priority: major | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- `pyamf.util.IndexedCollection` is the class used in all reference lookups so should be as fast as possible. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 6 04:49:22 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 06 Jan 2009 03:49:22 -0000 Subject: [pyamf-tickets] #343: Refactor the test suite to be python implementation independent In-Reply-To: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> References: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> Message-ID: <041.f1ff72c133b822d3cead30a02ba55ba9@pyamf.org> #343: Refactor the test suite to be python implementation independent -------------------------+-------------------------------------------------- Reporter: nick | Owner: thijs Type: enhancement | Status: assigned Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.3.1 Keywords: | -------------------------+-------------------------------------------------- Changes (by nick): * owner: nick => thijs Comment: I downloaded the [http://red5.googlecode.com/svn/flash/trunk/deploy/echo_test.swf latest echo_test] and i could not reproduce this? `HTTP AMF0` `HTTP AMF3` and `mx:RemoteObject` all worked without a hitch using this branch .. Can you double check? -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 6 15:38:45 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 06 Jan 2009 14:38:45 -0000 Subject: [pyamf-tickets] #425: Policy for Adobe Flash references Message-ID: <033.21b4efa73ec49f726ebe964b76f38d8c@pyamf.org> #425: Policy for Adobe Flash references ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: new Priority: critical | Milestone: 0.5 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Check the [http://www.adobe.com/misc/pdfs/flash_3rd_party_trademark_guidelines_020708.pdf Adobe Flash trademark guidelines] that describe how to refer to the Adobe Flash Player in our documentation and announcements. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 6 17:12:12 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 06 Jan 2009 16:12:12 -0000 Subject: [pyamf-tickets] #416: Release 0.4rc2 In-Reply-To: <033.fb458379f13bcedeea8fdf3c6d9ac259@pyamf.org> References: <033.fb458379f13bcedeea8fdf3c6d9ac259@pyamf.org> Message-ID: <042.16c8bf5fbed1ab5130e4c1908d063f0f@pyamf.org> #416: Release 0.4rc2 ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: closed Priority: blocker | Milestone: 0.4 Component: Website | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by thijs): * status: accepted => closed * resolution: => fixed Comment: Fixed with r1984 -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 00:07:37 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 06 Jan 2009 23:07:37 -0000 Subject: [pyamf-tickets] #426: ElementTree serialized to ObjectProxy, not XML Message-ID: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> #426: ElementTree serialized to ObjectProxy, not XML -----------------------------------------+---------------------------------- Reporter: jhaislip | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.5 Component: Remoting | Version: 0.4 Keywords: ElementTree ObjectProxy XML | -----------------------------------------+---------------------------------- I recently setup pyAMF with mod_python. I wrote test services that return the various datatypes of interest (DateTime, List, Bool, etc). I then accessed those services from a Flex application and saw that the serialization into Flex data types was working (Date, Array, Bool, etc). All of the data types I tested worked as they are supposed to except for one: ElementTree. In my service, I have: {{{ from pyamf.remoting.gateway.wsgi import WSGIGateway import elementtree.ElementTree as ET def getXML(): root = Element("root") SubElement(root, "one") SubElement(root, "two") SubElement(root, "three") SubElement(root, "four") return root # Expose our services: services = { 'service.getXML': getXML } GatewayController = WSGIGateway(services) }}} Here is the Flex: {{{ }}} When I access the service from Flex, it returns an ObjectProxy and not an XML. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 00:13:57 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 06 Jan 2009 23:13:57 -0000 Subject: [pyamf-tickets] #426: ElementTree serialized to ObjectProxy, not XML In-Reply-To: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> References: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> Message-ID: <045.33a60ca12c641fb96f58c460b3ed989e@pyamf.org> #426: ElementTree serialized to ObjectProxy, not XML -----------------------------------------+---------------------------------- Reporter: jhaislip | Owner: nick Type: defect | Status: new Priority: critical | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: ElementTree ObjectProxy XML | -----------------------------------------+---------------------------------- Changes (by thijs): * priority: major => critical * milestone: 0.5 => 0.4 Old description: > I recently setup pyAMF with mod_python. I wrote test services that return > the various datatypes of interest (DateTime, List, Bool, etc). I then > accessed those services from a Flex application and saw that the > serialization into Flex data types was working (Date, Array, Bool, etc). > All of the data types I tested worked as > they are supposed to except for one: ElementTree. > > In my service, I have: > > {{{ > from pyamf.remoting.gateway.wsgi import WSGIGateway > import elementtree.ElementTree as ET > > def getXML(): > root = Element("root") > > SubElement(root, "one") > SubElement(root, "two") > SubElement(root, "three") > SubElement(root, "four") > return root > > # Expose our services: > services = { > 'service.getXML': getXML > } > > GatewayController = WSGIGateway(services) > }}} > > Here is the Flex: > > {{{ > horizontalAlign="center" > verticalAlign="middle"> > > endpoint="http://localhost:80/services" destination="service" > result="displayResult(event)" fault="remoteFault(event)"> > > > > > > > > import mx.utils.ObjectUtil; > import mx.rpc.events.ResultEvent; > import mx.rpc.events.FaultEvent; > > private function displayResult(re:ResultEvent): void { > result.text = ObjectUtil.toString(re.result) + "\n"; > } > private function remoteFault(fault:FaultEvent): void { > result.text = ObjectUtil.toString(fault); > } > private function handleGetXML(evt:MouseEvent):void { > remoteObj.getXML() > } > ]]> > > > > }}} > > > When I access the service from Flex, it returns an ObjectProxy and not an > XML. New description: I recently setup pyAMF with mod_python. I wrote test services that return the various datatypes of interest (!DateTime, List, Bool, etc). I then accessed those services from a Flex application and saw that the serialization into Flex data types was working (Date, Array, Bool, etc). All of the data types I tested worked as they are supposed to except for one: !ElementTree. In my service, I have: {{{ #!python from pyamf.remoting.gateway.wsgi import WSGIGateway import elementtree.ElementTree as ET def getXML(): root = Element("root") SubElement(root, "one") SubElement(root, "two") SubElement(root, "three") SubElement(root, "four") return root # Expose our services: services = { 'service.getXML': getXML } GatewayController = WSGIGateway(services) }}} Here is the Flex: {{{ #!xml }}} When I access the service from Flex, it returns an ObjectProxy and not an XML. -- Comment: Moving to [milestone:0.4 milestone 0.4]. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 00:43:29 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 06 Jan 2009 23:43:29 -0000 Subject: [pyamf-tickets] #426: ElementTree serialized to ObjectProxy, not XML In-Reply-To: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> References: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> Message-ID: <045.307c9f263a6da4214054b39bd3e438ed@pyamf.org> #426: ElementTree serialized to ObjectProxy, not XML -----------------------------------------+---------------------------------- Reporter: jhaislip | Owner: nick Type: defect | Status: new Priority: critical | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: ElementTree ObjectProxy XML | -----------------------------------------+---------------------------------- Comment(by thijs): It was confirmed (on IRC) that this is working with 0.3.1 and a 0.4/trunk issue only. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 10:08:56 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 09:08:56 -0000 Subject: [pyamf-tickets] #427: elementree is not a supported XML lib Message-ID: <032.b36b78413346ea1a06c8aa9cdf9bbdf9@pyamf.org> #427: elementree is not a supported XML lib ---------------------+------------------------------------------------------ Reporter: nick | Owner: nick Type: defect | Status: new Priority: minor | Milestone: 0.4 Component: Utility | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ {{{ !#python >>> import pyamf >>> import xml.etree.ElementTree as ET >>> pyamf.encode(ET.Element('a', foo='bar'), encoding=pyamf.AMF3).getvalue() '\x0b\x1f' }}} Which is correct, however: {{{ >>> import pyamf >>> import elementtree.ElementTree as ET >>> pyamf.encode(ET.Element('a', foo='bar'), encoding=pyamf.AMF3).getvalue() '\n\x0b\x01\rattrib\n\x0b\x01\x07foo\x06\x07bar\x01\x07tag\x06\x03a\x13_children\t\x01\x01\x01' }}} Isn't. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 10:10:15 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 09:10:15 -0000 Subject: [pyamf-tickets] #427: elementree is not a supported XML lib In-Reply-To: <032.b36b78413346ea1a06c8aa9cdf9bbdf9@pyamf.org> References: <032.b36b78413346ea1a06c8aa9cdf9bbdf9@pyamf.org> Message-ID: <041.32547d816fab4780fdce03f207337b73@pyamf.org> #427: elementree is not a supported XML lib ---------------------+------------------------------------------------------ Reporter: nick | Owner: nick Type: defect | Status: accepted Priority: minor | Milestone: 0.4 Component: Utility | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Changes (by nick): * status: new => accepted Old description: > {{{ > !#python > >>> import pyamf > >>> import xml.etree.ElementTree as ET > >>> pyamf.encode(ET.Element('a', foo='bar'), > encoding=pyamf.AMF3).getvalue() > '\x0b\x1f' > }}} > > Which is correct, however: > > {{{ > >>> import pyamf > >>> import elementtree.ElementTree as ET > >>> pyamf.encode(ET.Element('a', foo='bar'), > encoding=pyamf.AMF3).getvalue() > '\n\x0b\x01\rattrib\n\x0b\x01\x07foo\x06\x07bar\x01\x07tag\x06\x03a\x13_children\t\x01\x01\x01' > }}} > > Isn't. New description: {{{ #!python >>> import pyamf >>> import xml.etree.ElementTree as ET >>> pyamf.encode(ET.Element('a', foo='bar'), encoding=pyamf.AMF3).getvalue() '\x0b\x1f' }}} Which is correct, however: {{{ #!python >>> import pyamf >>> import elementtree.ElementTree as ET >>> pyamf.encode(ET.Element('a', foo='bar'), encoding=pyamf.AMF3).getvalue() '\n\x0b\x01\rattrib\n\x0b\x01\x07foo\x06\x07bar\x01\x07tag\x06\x03a\x13_children\t\x01\x01\x01' }}} Isn't. -- -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 11:06:04 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 10:06:04 -0000 Subject: [pyamf-tickets] #427: elementree is not a supported XML lib In-Reply-To: <032.b36b78413346ea1a06c8aa9cdf9bbdf9@pyamf.org> References: <032.b36b78413346ea1a06c8aa9cdf9bbdf9@pyamf.org> Message-ID: <041.cd4dd29961077ef55760320311ba2479@pyamf.org> #427: elementree is not a supported XML lib ------------------------+--------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: closed Priority: minor | Milestone: 0.4 Component: Utility | Version: 0.4 Resolution: duplicate | Keywords: ------------------------+--------------------------------------------------- Changes (by nick): * status: accepted => closed * resolution: => duplicate Comment: Duplicate of #426. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 11:23:49 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 10:23:49 -0000 Subject: [pyamf-tickets] #426: ElementTree serialized to ObjectProxy, not XML In-Reply-To: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> References: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> Message-ID: <045.78a074efe0b927b51bf1e22d85d0e12d@pyamf.org> #426: ElementTree serialized to ObjectProxy, not XML -----------------------------------------+---------------------------------- Reporter: jhaislip | Owner: nick Type: defect | Status: accepted Priority: critical | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: ElementTree ObjectProxy XML | -----------------------------------------+---------------------------------- Changes (by nick): * status: new => accepted Comment: Branching to source:pyamf/branches/etree-checking-426 -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 11:30:59 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 10:30:59 -0000 Subject: [pyamf-tickets] #428: Move ubuntu buildslaves Message-ID: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> #428: Move ubuntu buildslaves ---------------------+------------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: new Priority: major | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Currently the BuildBot farm is running buildslaves as well as the buildmaster, but also the website/svn/mailinglist etc. This is causing too much load on the server so it would be a good idea to move those amd64-ubuntu-* slaves to a different server. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 11:53:02 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 10:53:02 -0000 Subject: [pyamf-tickets] #428: Move ubuntu buildslaves In-Reply-To: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> References: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> Message-ID: <042.18352e6cc296bc9dc5033365e95caa41@pyamf.org> #428: Move ubuntu buildslaves ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: task | Status: assigned Priority: critical | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by thijs): * owner: thijs => nick * priority: major => critical * status: new => assigned -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 15:49:42 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 14:49:42 -0000 Subject: [pyamf-tickets] #426: ElementTree serialized to ObjectProxy, not XML In-Reply-To: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> References: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> Message-ID: <045.47df5c5e069f111456f9a2df1ec8d9c8@pyamf.org> #426: ElementTree serialized to ObjectProxy, not XML ---------------------------------------------------+------------------------ Reporter: jhaislip | Owner: thijs Type: defect | Status: assigned Priority: critical | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: ElementTree, ObjectProxy, XML, review | ---------------------------------------------------+------------------------ Changes (by nick): * keywords: ElementTree ObjectProxy XML => ElementTree, ObjectProxy, XML, review * owner: nick => thijs * status: accepted => assigned Comment: I amended the xml lib initialisation code to check in order for all libraries available and to check for each type when encoding xml elements. When decoding PyAMF will use the first implementation is comes across. This is the order: 1. xml.etree.cElementTree 2. cElementTree 3. xml.etree.ElementTree 4. elementtree.ElementTree Tests have been added to ensure that all libs are compatible. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 16:36:44 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 15:36:44 -0000 Subject: [pyamf-tickets] #426: ElementTree serialized to ObjectProxy, not XML In-Reply-To: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> References: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> Message-ID: <045.d1da8caf132e71b04262dfef62cd2848@pyamf.org> #426: ElementTree serialized to ObjectProxy, not XML ---------------------------------------------------+------------------------ Reporter: jhaislip | Owner: nick Type: defect | Status: assigned Priority: critical | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: ElementTree, ObjectProxy, XML, review | ---------------------------------------------------+------------------------ Changes (by thijs): * owner: thijs => nick Comment: The new method needs @since: 0.4 markup. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 17:48:14 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 16:48:14 -0000 Subject: [pyamf-tickets] #429: Grab version nr for setuptools from pyamf.__version__ Message-ID: <033.2494d02167f54b117ea00871f6dcefee@pyamf.org> #429: Grab version nr for setuptools from pyamf.__version__ -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: new Priority: minor | Milestone: 0.5 Component: Installer | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- We're currently defining the PyAMF version nr in 2 places: 1. [source:pyamf/trunk/setup.py] 1. [source:pyamf/trunk/pyamf/__init__.py] - {{{__version__}}} Let's import the version nr from option 2 into option 1. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 17:50:07 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 16:50:07 -0000 Subject: [pyamf-tickets] #426: ElementTree serialized to ObjectProxy, not XML In-Reply-To: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> References: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> Message-ID: <045.8415a1e0a9c58649076eb01eedbdf69d@pyamf.org> #426: ElementTree serialized to ObjectProxy, not XML ---------------------------------------------------+------------------------ Reporter: jhaislip | Owner: thijs Type: defect | Status: assigned Priority: critical | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: ElementTree, ObjectProxy, XML, review | ---------------------------------------------------+------------------------ Changes (by nick): * owner: nick => thijs Comment: Done. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 18:22:56 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 17:22:56 -0000 Subject: [pyamf-tickets] #426: ElementTree serialized to ObjectProxy, not XML In-Reply-To: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> References: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> Message-ID: <045.6321a68d3ce1a3a0da074895f7ed8646@pyamf.org> #426: ElementTree serialized to ObjectProxy, not XML -------------------------------------------+-------------------------------- Reporter: jhaislip | Owner: nick Type: defect | Status: assigned Priority: critical | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: ElementTree, ObjectProxy, XML | -------------------------------------------+-------------------------------- Changes (by thijs): * keywords: ElementTree, ObjectProxy, XML, review => ElementTree, ObjectProxy, XML * owner: thijs => nick Comment: If it works with the latest EchoTest, and passes the tests on feisley's buildslaves, then it can be merged. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 18:24:28 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 17:24:28 -0000 Subject: [pyamf-tickets] #356: Remove fpconst dependency for Windows with Python 2.6 In-Reply-To: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> References: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> Message-ID: <042.ee57750c683040d210db08778272a980@pyamf.org> #356: Remove fpconst dependency for Windows with Python 2.6 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: accepted Priority: major | Milestone: 0.5 Component: Installer | Version: 0.3.1 Keywords: | -------------------------+-------------------------------------------------- Changes (by nick): * status: new => accepted * component: Decoder => Installer Comment: I suggest instead of adding lots of `if` statements for edge cases such as this we should only require the fpconst lib if we detect that floats are broken on the platform from within `setup.py` -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 18:44:40 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 17:44:40 -0000 Subject: [pyamf-tickets] #356: Remove fpconst dependency for Windows with Python 2.6 In-Reply-To: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> References: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> Message-ID: <042.d9c2f1ceb268193916ed44f951956b78@pyamf.org> #356: Remove fpconst dependency for Windows with Python 2.6 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: accepted Priority: major | Milestone: 0.5 Component: Installer | Version: 0.3.1 Keywords: | -------------------------+-------------------------------------------------- Comment(by nick): Branching to source:pyamf/branches/broken-floats-356 -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 18:46:15 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 17:46:15 -0000 Subject: [pyamf-tickets] #356: Remove fpconst dependency for Windows with Python 2.6 In-Reply-To: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> References: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> Message-ID: <042.87dcd541a61a337a924d1ae535138b25@pyamf.org> #356: Remove fpconst dependency for Windows with Python 2.6 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: thijs Type: enhancement | Status: assigned Priority: major | Milestone: 0.5 Component: Installer | Version: 0.3.1 Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * keywords: => review * status: accepted => assigned * owner: nick => thijs Comment: Ready for review in r1991. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 19:37:39 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 18:37:39 -0000 Subject: [pyamf-tickets] #426: ElementTree serialized to ObjectProxy, not XML In-Reply-To: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> References: <036.893e98586d92c45cfb41dee78c7ed83f@pyamf.org> Message-ID: <045.e0bf2d02872b5237e298ea7feee09d35@pyamf.org> #426: ElementTree serialized to ObjectProxy, not XML -----------------------+---------------------------------------------------- Reporter: jhaislip | Owner: nick Type: defect | Status: closed Priority: critical | Milestone: 0.4 Component: Remoting | Version: 0.4 Resolution: fixed | Keywords: ElementTree, ObjectProxy, XML -----------------------+---------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Checked EchoTest and slaves - all good. I have merged to trunk in r1992 and to source:pyamf/branches/release-0.4 in r1993. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 20:32:22 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 19:32:22 -0000 Subject: [pyamf-tickets] #390: encoding/decoding dates prior to 1970 with Windows In-Reply-To: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> References: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> Message-ID: <043.591bb7bd1883ec35157566c6b0a61b63@pyamf.org> #390: encoding/decoding dates prior to 1970 with Windows ---------------------+------------------------------------------------------ Reporter: arman0 | Owner: thijs Type: defect | Status: assigned Priority: major | Milestone: 0.5 Component: Decoder | Version: 0.3.1 Keywords: review | ---------------------+------------------------------------------------------ Changes (by nick): * keywords: => review * owner: nick => thijs Comment: echo test and slaves look good. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 21:11:05 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 20:11:05 -0000 Subject: [pyamf-tickets] #430: Release 0.4rc3 Message-ID: <033.c022fd46085140a368c91facf2af7613@pyamf.org> #430: Release 0.4rc3 ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: new Priority: blocker | Milestone: 0.4 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ We're going to have another Release Candidate, hopefully the last one. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 21:12:33 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 20:12:33 -0000 Subject: [pyamf-tickets] #356: Remove fpconst dependency for Windows with Python 2.6 In-Reply-To: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> References: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> Message-ID: <042.415b00248990afef518014b4e60ced3b@pyamf.org> #356: Remove fpconst dependency for Windows with Python 2.6 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: thijs Type: enhancement | Status: accepted Priority: major | Milestone: 0.4 Component: Installer | Version: 0.3.1 Keywords: review | -------------------------+-------------------------------------------------- Changes (by thijs): * status: assigned => accepted * milestone: 0.5 => 0.4 -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 21:13:10 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 20:13:10 -0000 Subject: [pyamf-tickets] #390: encoding/decoding dates prior to 1970 with Windows In-Reply-To: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> References: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> Message-ID: <043.b46a10182e8f4b9e7235474624d437eb@pyamf.org> #390: encoding/decoding dates prior to 1970 with Windows ---------------------+------------------------------------------------------ Reporter: arman0 | Owner: thijs Type: defect | Status: accepted Priority: major | Milestone: 0.4 Component: Decoder | Version: 0.3.1 Keywords: review | ---------------------+------------------------------------------------------ Changes (by thijs): * status: assigned => accepted * milestone: 0.5 => 0.4 -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 21:17:30 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 20:17:30 -0000 Subject: [pyamf-tickets] #392: exceptions.AssertionError: != In-Reply-To: <033.91fa92ea990e28461d1611c72a5e4318@pyamf.org> References: <033.91fa92ea990e28461d1611c72a5e4318@pyamf.org> Message-ID: <042.a0c1274a30fc8eb819b0479068561a6b@pyamf.org> #392: exceptions.AssertionError: != ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: reopened Priority: major | Milestone: 0.5 Component: Testing | Version: 0.4 Resolution: | Keywords: ----------------------+----------------------------------------------------- Changes (by thijs): * status: closed => reopened * resolution: fixed => * milestone: 0.4 => 0.5 Comment: Looks like it's [http://buildbot.pyamf.org/builders/x86-winxp- py26/builds/9/steps/python2.6-test_4/logs/stdio back] :-/ -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 21:18:57 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 20:18:57 -0000 Subject: [pyamf-tickets] #402: fpconst should be installed on all win32 buildslaves by default In-Reply-To: <032.acab1dbf9774ae292106736d363e870d@pyamf.org> References: <032.acab1dbf9774ae292106736d363e870d@pyamf.org> Message-ID: <041.68da6380555221c23fc9488262b7146b@pyamf.org> #402: fpconst should be installed on all win32 buildslaves by default ----------------------+----------------------------------------------------- Reporter: nick | Owner: feisley Type: defect | Status: reopened Priority: major | Milestone: 0.4 Component: Testing | Version: 0.3.1 Resolution: | Keywords: ----------------------+----------------------------------------------------- Changes (by thijs): * status: closed => reopened * resolution: fixed => * component: Remoting => Testing Comment: It's [http://buildbot.pyamf.org/builders/x86-winxp- py26/builds/9/steps/python2.6-test_4/logs/stdio back]. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 21:41:34 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 20:41:34 -0000 Subject: [pyamf-tickets] #356: Remove fpconst dependency for Windows with Python 2.6 In-Reply-To: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> References: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> Message-ID: <042.0a2ee26d7b89bd8dbd771179f5fbc7d4@pyamf.org> #356: Remove fpconst dependency for Windows with Python 2.6 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: assigned Priority: major | Milestone: 0.4 Component: Installer | Version: 0.3.1 Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * keywords: review => * owner: thijs => nick * status: accepted => assigned Comment: Looks like it's [http://buildbot.pyamf.org/builders/x86-winxp- py26/builds/11/steps/python2.6-test/logs/stdio working], please merge. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 21:47:27 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 20:47:27 -0000 Subject: [pyamf-tickets] #402: fpconst should be installed on the win32 buildslaves by default (was: fpconst should be installed on all win32 buildslaves by default) In-Reply-To: <032.acab1dbf9774ae292106736d363e870d@pyamf.org> References: <032.acab1dbf9774ae292106736d363e870d@pyamf.org> Message-ID: <041.5e9a85d27d5680849a4b959891f44cbd@pyamf.org> #402: fpconst should be installed on the win32 buildslaves by default ----------------------+----------------------------------------------------- Reporter: nick | Owner: feisley Type: defect | Status: closed Priority: major | Milestone: 0.4 Component: Testing | Version: 0.3.1 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by thijs): * status: reopened => closed * resolution: => fixed Old description: > Otherwise we get failed builds like > [http://buildbot.pyamf.org/builders/x86-win2003-py25/builds/100/steps/python2.5-test/logs/stdio > this] New description: Otherwise we get failed builds like [http://buildbot.pyamf.org/builders/x86-win2003-py25/builds/100/steps/python2.5-test/logs/stdio this]. It shouldn't be installed on the Python 2.6 slave because that one doesn't have any problems with floats. -- Comment: #356 fixed this one. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 22:01:59 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 21:01:59 -0000 Subject: [pyamf-tickets] #356: Remove fpconst dependency for Windows with Python 2.6 In-Reply-To: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> References: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> Message-ID: <042.d36c1c21a2baf60158f659cd522f843d@pyamf.org> #356: Remove fpconst dependency for Windows with Python 2.6 --------------------------+------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: closed Priority: major | Milestone: 0.4 Component: Installer | Version: 0.3.1 Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Merged to source:pyamf/branches/release-0.4 and source:pyamf/trunk -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 22:52:08 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 21:52:08 -0000 Subject: [pyamf-tickets] #356: Remove fpconst dependency for Windows with Python 2.6 In-Reply-To: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> References: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> Message-ID: <042.9149fa344e0e17691ff3b814188de34a@pyamf.org> #356: Remove fpconst dependency for Windows with Python 2.6 --------------------------+------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: reopened Priority: major | Milestone: 0.4 Component: Installer | Version: 0.3.1 Resolution: | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: closed => reopened * resolution: fixed => Comment: win32-python2.4 slave is failing .. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 7 23:11:31 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 07 Jan 2009 22:11:31 -0000 Subject: [pyamf-tickets] #356: Remove fpconst dependency for Windows with Python 2.6 In-Reply-To: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> References: <033.5aa14d9c6d6c74fa6dca64b2700d439a@pyamf.org> Message-ID: <042.377984d50f4cc0676e3fc47b58bd8316@pyamf.org> #356: Remove fpconst dependency for Windows with Python 2.6 --------------------------+------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: closed Priority: major | Milestone: 0.4 Component: Installer | Version: 0.3.1 Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: reopened => closed * resolution: => fixed Comment: Fixed in r2005 -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 8 10:53:29 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 08 Jan 2009 09:53:29 -0000 Subject: [pyamf-tickets] #377: Porting C-Extension Module to Python 3.0 In-Reply-To: <033.89ff9943ac068869772f5a3137a306d4@pyamf.org> References: <033.89ff9943ac068869772f5a3137a306d4@pyamf.org> Message-ID: <042.e70dbd15b8f24c003b8dd2d0494e4bf8@pyamf.org> #377: Porting C-Extension Module to Python 3.0 --------------------------+------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: closed Priority: minor | Milestone: Python 3000 Component: C-Extension | Version: 0.4 Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Cython is now in operation - Py3k taken care of. -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 8 11:01:04 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 08 Jan 2009 10:01:04 -0000 Subject: [pyamf-tickets] #252: Add egg export feature to package script In-Reply-To: <033.71bde58a1920b3944fc7c735254710e3@pyamf.org> References: <033.71bde58a1920b3944fc7c735254710e3@pyamf.org> Message-ID: <042.d8e08c1ce8798cdcbeabcff6e042e1e2@pyamf.org> #252: Add egg export feature to package script -----------------------+---------------------------------------------------- Reporter: thijs | Owner: nick Type: task | Status: new Priority: minor | Milestone: At some point Component: Installer | Version: 0.3 Keywords: | -----------------------+---------------------------------------------------- Comment(by nick): The eggs are now platform dependant (since the introduction of cpyamf) so using the package script is a not an option. I recommend integrating the egg building into the buildslaves which would upload the result to the master (roughly 220K for each egg). -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 8 17:23:31 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 08 Jan 2009 16:23:31 -0000 Subject: [pyamf-tickets] #343: Refactor the test suite to be python implementation independent In-Reply-To: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> References: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> Message-ID: <041.20b6ce2c91e390bb6c87283478210a48@pyamf.org> #343: Refactor the test suite to be python implementation independent -------------------------+-------------------------------------------------- Reporter: nick | Owner: thijs Type: enhancement | Status: assigned Priority: minor | Milestone: 0.4 Component: Testing | Version: 0.3.1 Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * keywords: => review * milestone: 0.5 => 0.4 -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 8 18:47:51 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 08 Jan 2009 17:47:51 -0000 Subject: [pyamf-tickets] #428: Move ubuntu buildslaves In-Reply-To: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> References: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> Message-ID: <042.35be6c1681f67962e2325715f5fbc58f@pyamf.org> #428: Move ubuntu buildslaves ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: task | Status: assigned Priority: critical | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Comment(by nick): Ubuntu build slaves have now been moved to callisto (thanks to Dark Horse Networks for providing hardware/support) - however i am getting this issue: http://buildbot.pyamf.org/builders/ubuntu-py24/builds/6/steps/svn- update/logs/stdio I can create the build dir and then the next build will run fine but then the dir is deleted and the error will appear in the next build. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 10 21:14:59 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 10 Jan 2009 20:14:59 -0000 Subject: [pyamf-tickets] #428: Move ubuntu buildslaves In-Reply-To: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> References: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> Message-ID: <042.c68496e8672843d5ffaa8d097ed8c5ee@pyamf.org> #428: Move ubuntu buildslaves ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: assigned Priority: critical | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: review | ----------------------+----------------------------------------------------- Changes (by nick): * keywords: => review * owner: nick => thijs Comment: The error has now been sorted - see http://buildbot.net/trac/ticket/284 Django & Twisted installed on all slaves. I have also created 4 debian64 python23-6 slaves to cover that distribution also. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 10 21:32:51 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 10 Jan 2009 20:32:51 -0000 Subject: [pyamf-tickets] #431: Don't fire a build on every commit to branches Message-ID: <032.932689b90dc0786c1d0e18318d92c1e0@pyamf.org> #431: Don't fire a build on every commit to branches -------------------------+-------------------------------------------------- Reporter: nick | Owner: thijs Type: enhancement | Status: new Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Lots of commits are thrown into the branches - including debug stuff. When a ticket is ready for merging a manual build should be fired by the reviewer and an auto build should be fired when merging to trunk. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 10 21:38:12 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 10 Jan 2009 20:38:12 -0000 Subject: [pyamf-tickets] #390: encoding/decoding dates prior to 1970 with Windows In-Reply-To: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> References: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> Message-ID: <043.0ec27cea93b0cc80a61e03c19d368491@pyamf.org> #390: encoding/decoding dates prior to 1970 with Windows ---------------------+------------------------------------------------------ Reporter: arman0 | Owner: thijs Type: defect | Status: accepted Priority: major | Milestone: 0.4 Component: Decoder | Version: 0.3.1 Keywords: review | ---------------------+------------------------------------------------------ Comment(by nick): For reference: source:pyamf/branches/negative-timestamp-390 -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 10 21:42:27 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 10 Jan 2009 20:42:27 -0000 Subject: [pyamf-tickets] #432: Only run PyFlakes on the pyamf tree Message-ID: <032.1ff1eecc791e299b7f6eec5aa9d728f7@pyamf.org> #432: Only run PyFlakes on the pyamf tree ---------------------+------------------------------------------------------ Reporter: nick | Owner: thijs Type: task | Status: new Priority: minor | Milestone: Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Otherwise we get false positives such as: http://buildbot.pyamf.org/builders/ubuntu- py24/builds/10/steps/pyflakes/logs/stdio -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 10 21:44:46 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 10 Jan 2009 20:44:46 -0000 Subject: [pyamf-tickets] #433: Only run PyFlakes on the pyamf tree Message-ID: <032.8d444565c76d4961e1bbbd9edec8ef74@pyamf.org> #433: Only run PyFlakes on the pyamf tree ---------------------+------------------------------------------------------ Reporter: nick | Owner: thijs Type: task | Status: new Priority: minor | Milestone: Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Otherwise we get false positives such as: http://buildbot.pyamf.org/builders/ubuntu- py24/builds/10/steps/pyflakes/logs/stdio -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 10 21:46:24 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 10 Jan 2009 20:46:24 -0000 Subject: [pyamf-tickets] #433: Only run PyFlakes on the pyamf tree In-Reply-To: <032.8d444565c76d4961e1bbbd9edec8ef74@pyamf.org> References: <032.8d444565c76d4961e1bbbd9edec8ef74@pyamf.org> Message-ID: <041.b575424a43f6e4443e9e33b27fb179d9@pyamf.org> #433: Only run PyFlakes on the pyamf tree ------------------------+--------------------------------------------------- Reporter: nick | Owner: thijs Type: task | Status: closed Priority: minor | Milestone: Component: Testing | Version: 0.4 Resolution: duplicate | Keywords: ------------------------+--------------------------------------------------- Changes (by nick): * status: new => closed * resolution: => duplicate Comment: Duplicate of #432. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 10 21:49:36 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 10 Jan 2009 20:49:36 -0000 Subject: [pyamf-tickets] #390: encoding/decoding dates prior to 1970 with Windows In-Reply-To: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> References: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> Message-ID: <043.a1899bfbe3015337d3ef8034f9fdb0ad@pyamf.org> #390: encoding/decoding dates prior to 1970 with Windows ---------------------+------------------------------------------------------ Reporter: arman0 | Owner: nick Type: defect | Status: assigned Priority: major | Milestone: 0.4 Component: Decoder | Version: 0.3.1 Keywords: | ---------------------+------------------------------------------------------ Changes (by thijs): * keywords: review => * status: accepted => assigned * owner: thijs => nick Comment: Replying to [comment:7 nick]: > echo test and slaves look good. In that case merge. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 10 22:31:34 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 10 Jan 2009 21:31:34 -0000 Subject: [pyamf-tickets] #390: encoding/decoding dates prior to 1970 with Windows In-Reply-To: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> References: <034.5bb436d07ccee5df6c3eebd6ef53dbbf@pyamf.org> Message-ID: <043.10f41771263ab39ffde071fccbe31e8a@pyamf.org> #390: encoding/decoding dates prior to 1970 with Windows ----------------------+----------------------------------------------------- Reporter: arman0 | Owner: nick Type: defect | Status: closed Priority: major | Milestone: 0.4 Component: Decoder | Version: 0.3.1 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 11 05:06:20 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 11 Jan 2009 04:06:20 -0000 Subject: [pyamf-tickets] #392: exceptions.AssertionError: != In-Reply-To: <033.91fa92ea990e28461d1611c72a5e4318@pyamf.org> References: <033.91fa92ea990e28461d1611c72a5e4318@pyamf.org> Message-ID: <042.6dbcc9ab3d9dac586666c512ab569839@pyamf.org> #392: exceptions.AssertionError: != ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: closed Priority: major | Milestone: 0.5 Component: Testing | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by nick): * status: reopened => closed * resolution: => fixed Comment: Fixed. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 11 05:07:57 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 11 Jan 2009 04:07:57 -0000 Subject: [pyamf-tickets] #428: Move ubuntu buildslaves In-Reply-To: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> References: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> Message-ID: <042.908b8fb93390494abce65e3dc735c7ef@pyamf.org> #428: Move ubuntu buildslaves ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: assigned Priority: critical | Milestone: 0.4 Component: Website | Version: 0.4 Keywords: review | ----------------------+----------------------------------------------------- Changes (by nick): * milestone: 0.5 => 0.4 -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 11 17:06:45 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 11 Jan 2009 16:06:45 -0000 Subject: [pyamf-tickets] #343: Refactor the test suite to be python implementation independent In-Reply-To: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> References: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> Message-ID: <041.c857f880b4d703d9d728cc0ba09b76c3@pyamf.org> #343: Refactor the test suite to be python implementation independent -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: assigned Priority: minor | Milestone: 0.4 Component: Testing | Version: 0.3.1 Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * keywords: review => * owner: thijs => nick Comment: Tested with ParseDump and EchoTest and looks good now, please merge. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 11 17:09:19 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 11 Jan 2009 16:09:19 -0000 Subject: [pyamf-tickets] #428: Move ubuntu buildslaves In-Reply-To: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> References: <033.70ba1a7ec752befbafc6ca21a2387c59@pyamf.org> Message-ID: <042.b7ec31b700382f993558314f8c24ea9a@pyamf.org> #428: Move ubuntu buildslaves -----------------------+---------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: closed Priority: critical | Milestone: 0.4 Component: Website | Version: 0.4 Resolution: fixed | Keywords: -----------------------+---------------------------------------------------- Changes (by thijs): * keywords: review => * status: assigned => closed * resolution: => fixed Comment: Awesome, good stuff! -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 11 17:29:29 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 11 Jan 2009 16:29:29 -0000 Subject: [pyamf-tickets] #343: Refactor the test suite to be python implementation independent In-Reply-To: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> References: <032.8c0796b9ab6b09f3b787e55e3d304d2a@pyamf.org> Message-ID: <041.605f3c2a4aac3ad62511fb6deec55cd6@pyamf.org> #343: Refactor the test suite to be python implementation independent --------------------------+------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: closed Priority: minor | Milestone: 0.4 Component: Testing | Version: 0.3.1 Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 11 17:34:22 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 11 Jan 2009 16:34:22 -0000 Subject: [pyamf-tickets] #434: need twisted client API using defer Message-ID: <035.985b1d3065feb21a2b37015ef0e62ae8@pyamf.org> #434: need twisted client API using defer -------------------------+-------------------------------------------------- Reporter: cassidy | Owner: nick Type: enhancement | Status: new Priority: major | Milestone: 0.5 Component: Client | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- I need a client side API using twisted's defer (for async method calls) but didn't find one in existing API. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 11 19:36:36 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 11 Jan 2009 18:36:36 -0000 Subject: [pyamf-tickets] #435: Return XML instead of XMLDocument Message-ID: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> #435: Return XML instead of XMLDocument ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- When I create a server that returns elementtree data, and request it with a AMF3 Flex client, it's being returned as flash.xml.XMLDocument data instead of an toplevel XML instance. See attached test files that demonstrate the problem. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 11 19:55:24 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 11 Jan 2009 18:55:24 -0000 Subject: [pyamf-tickets] #269: Issues with PyAMF and Jython In-Reply-To: <033.e52e403024bdb47ab854aeb6669eb8cc@pyamf.org> References: <033.e52e403024bdb47ab854aeb6669eb8cc@pyamf.org> Message-ID: <042.02a6330da434563d73cc6c6c45ef8723@pyamf.org> #269: Issues with PyAMF and Jython -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: accepted Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.3 Keywords: | -------------------------+-------------------------------------------------- Comment(by thijs): Blocked by #353 and http://bugs.jython.org/issue1227 -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 11 19:59:37 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 11 Jan 2009 18:59:37 -0000 Subject: [pyamf-tickets] #420: Create example that uses the SQLAlchemy Adapter In-Reply-To: <033.50980369e7f89a7c2776b18e6efa6bcf@pyamf.org> References: <033.50980369e7f89a7c2776b18e6efa6bcf@pyamf.org> Message-ID: <042.67549848ecabd94cff18d17de9862b47@pyamf.org> #420: Create example that uses the SQLAlchemy Adapter ----------------------+----------------------------------------------------- Reporter: thijs | Owner: dthompso Type: task | Status: assigned Priority: major | Milestone: 0.5 Component: Examples | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by thijs): * owner: thijs => dthompso * status: new => assigned Comment: See [source:examples/branches/sqlalchemy_examples_420] -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 12 23:57:35 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 12 Jan 2009 22:57:35 -0000 Subject: [pyamf-tickets] #422: Add read/write_24bit_uint to util.DataTypeMixIn. In-Reply-To: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> References: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> Message-ID: <041.44fe8f46722ed1981742e7d5c681071c@pyamf.org> #422: Add read/write_24bit_uint to util.DataTypeMixIn. -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: accepted Priority: minor | Milestone: 0.4 Component: Utility | Version: Keywords: | -------------------------+-------------------------------------------------- Changes (by nick): * status: new => accepted * type: defect => enhancement * milestone: 0.5 => 0.4 -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 00:00:16 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 12 Jan 2009 23:00:16 -0000 Subject: [pyamf-tickets] #422: Add read/write_24bit_uint to util.DataTypeMixIn. In-Reply-To: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> References: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> Message-ID: <041.4356e386cc13f945b62c2170de752667@pyamf.org> #422: Add read/write_24bit_uint to util.DataTypeMixIn. -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: accepted Priority: minor | Milestone: 0.4 Component: Utility | Version: Keywords: | -------------------------+-------------------------------------------------- Comment(by nick): Branching to source:pyamf/branches/24int-422 -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 00:03:50 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 12 Jan 2009 23:03:50 -0000 Subject: [pyamf-tickets] #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. Message-ID: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- I'm working on it. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 00:23:19 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 12 Jan 2009 23:23:19 -0000 Subject: [pyamf-tickets] #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. In-Reply-To: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> References: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> Message-ID: <045.dda40049ad696a1b21b99e98abbd4270@pyamf.org> #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: dthompso Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by nick): * owner: nick => dthompso * priority: major => blocker * status: new => assigned -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 02:44:30 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 01:44:30 -0000 Subject: [pyamf-tickets] #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. In-Reply-To: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> References: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> Message-ID: <045.590a59d74fbba76380b1ed8a6006a92e@pyamf.org> #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: dthompso Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Comment(by dthompso): My fix in 'branches/sa_0.5.0-436' is ready for review. I had some pending improvements I threw in there too. The change to the 'is_class_sa_mapped' function fixed the problem with SA 0.5.0, all the other changes are improvements. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 03:07:22 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 02:07:22 -0000 Subject: [pyamf-tickets] #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. In-Reply-To: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> References: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> Message-ID: <045.c6b991921742b63e5a96ee1b40f54f86@pyamf.org> #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: dthompso Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Comment(by nick): Generally looking good. Some comments: {{{ #!python ['_sa_class_manager', '_sa_adapter', '_sa_appender', '_sa_instrumented', '_sa_iterator', '_sa_remover', '_sa_initiator'] }}} are all extra excluded attributes. Are these necessary - especially the last 5? Shouldn't {{{ #!python pyamf.add_type(collections.InstrumentedList, util.to_list) pyamf.add_type(collections.InstrumentedDict, util.to_dict) pyamf.add_type(collections.InstrumentedSet, util.to_set) }}} cover these most of these cases? I haven't delved too deep into SA's behaviour so I could be/probably am missing something .. Tests are required for the `applyAttributes` behaviour. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 06:07:10 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 05:07:10 -0000 Subject: [pyamf-tickets] #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. In-Reply-To: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> References: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> Message-ID: <045.f9b5a3a642deac1c0b017dba8212596c@pyamf.org> #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: dthompso Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Comment(by dthompso): I'm not sure if we need '_sa_class_manager' or not, I just saw that one sitting around. The other extra attributes are used by SA for custom collections. They hold the information needed by SA to use a custom class that does not inherit from one of the 3 Instrumented... classes as if it were a collection class. See here for more info: [http://www.sqlalchemy.org/docs/05/mappers.html#custom-collection- implementations] We have one important custom collection in our code base, but I'm not sure how commonly other people use them. I changed the existing test 'test_lazy_load_attributes' to test for the new behavior (lazy-loaded attributes should not be in __dict__ even if they were set in __init__). -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 18:59:42 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 17:59:42 -0000 Subject: [pyamf-tickets] #437: Move Jython buildslave to different server Message-ID: <033.f16137b48b0e77b18c75dc4812cf1203@pyamf.org> #437: Move Jython buildslave to different server ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: task | Status: new Priority: major | Milestone: 0.5 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ The Jython buildslave on the main PyAMF webserver is slowing down the site severely, so it should moved to a different machine. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 19:14:38 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 18:14:38 -0000 Subject: [pyamf-tickets] #422: Add read/write_24bit_uint to util.DataTypeMixIn. In-Reply-To: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> References: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> Message-ID: <041.9cd8fdad8a4b7ca924a280b85474a403@pyamf.org> #422: Add read/write_24bit_uint to util.DataTypeMixIn. -------------------------+-------------------------------------------------- Reporter: nick | Owner: thijs Type: enhancement | Status: assigned Priority: minor | Milestone: 0.4 Component: Utility | Version: Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * keywords: => review * status: accepted => assigned * owner: nick => thijs -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 19:16:46 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 18:16:46 -0000 Subject: [pyamf-tickets] #438: Setup PyAMF rsync backup Message-ID: <033.4bccdfb705c5fd749ecc83f062fdf762@pyamf.org> #438: Setup PyAMF rsync backup ----------------------+----------------------------------------------------- Reporter: thijs | Owner: feisley Type: task | Status: new Priority: critical | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- We need to backup the PyAMF site and resources every night and setup mirrors. We have several volunteers for this, but feisley is the main man to get this going. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 19:21:09 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 18:21:09 -0000 Subject: [pyamf-tickets] #423: Add a consume method that will chop the head off the data stream at the current stream position. In-Reply-To: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> References: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> Message-ID: <041.bb5d32727da575608c4fbbf0ca93bc63@pyamf.org> #423: Add a consume method that will chop the head off the data stream at the current stream position. -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: accepted Priority: minor | Milestone: 0.5 Component: Utility | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by nick): * status: new => accepted * type: defect => enhancement Comment: Branching to source:pyamf/branches/util-consume-423 -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 19:21:50 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 18:21:50 -0000 Subject: [pyamf-tickets] #439: Get rid of draft background image in source browser Message-ID: <033.83aa80941e9aaad9b930755c2e94973f@pyamf.org> #439: Get rid of draft background image in source browser ---------------------+------------------------------------------------------ Reporter: thijs | Owner: thijs Type: defect | Status: new Priority: minor | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ The source browser in Trac uses a 'draft' background image for some files like [source:pyamf/trunk/cpyamf/amf3.pyx]. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 19:38:21 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 18:38:21 -0000 Subject: [pyamf-tickets] #423: Add a consume method that will chop the head off the data stream at the current stream position. In-Reply-To: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> References: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> Message-ID: <041.0e9bdefa8b62734531ffcd0303be03ee@pyamf.org> #423: Add a consume method that will chop the head off the data stream at the current stream position. -------------------------+-------------------------------------------------- Reporter: nick | Owner: thijs Type: enhancement | Status: assigned Priority: minor | Milestone: 0.5 Component: Utility | Version: 0.4 Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * keywords: => review * owner: nick => thijs * status: accepted => assigned -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 20:16:30 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 19:16:30 -0000 Subject: [pyamf-tickets] #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. In-Reply-To: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> References: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> Message-ID: <045.905b02b28be08e43b65b0e552a44ca54@pyamf.org> #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: dthompso Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Comment(by dthompso): I made another modification to ensure that decoded objects can be merged correctly. All tests pass with SA 0.5.0 and SA 0.4.8. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 20:56:35 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 19:56:35 -0000 Subject: [pyamf-tickets] #423: Add a consume method that will chop the head off the data stream at the current stream position. In-Reply-To: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> References: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> Message-ID: <041.6fac308da64c2f9f2c458953eeac7288@pyamf.org> #423: Add a consume method that will chop the head off the data stream at the current stream position. -------------------------+-------------------------------------------------- Reporter: nick | Owner: thijs Type: enhancement | Status: assigned Priority: minor | Milestone: 0.4 Component: Utility | Version: 0.4 Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * milestone: 0.5 => 0.4 -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 21:05:46 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 20:05:46 -0000 Subject: [pyamf-tickets] #422: Add read/write_24bit_uint to util.DataTypeMixIn. In-Reply-To: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> References: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> Message-ID: <041.38b6b71cb04c60aaff7c2219c8e46e10@pyamf.org> #422: Add read/write_24bit_uint to util.DataTypeMixIn. -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: assigned Priority: minor | Milestone: 0.4 Component: Utility | Version: Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * keywords: review => * owner: thijs => nick Comment: Unit tests, EchoTest and ParseDump succeed. Please merge after adding {{{@rtype}}} and {{{@return}}} markup for the new methods, and adding a changelog entry. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 21:15:29 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 20:15:29 -0000 Subject: [pyamf-tickets] #440: epydoc signatures should be added to all util.StringIOProxy, util.DataTypeMixIn and util.BufferedByteStream classes Message-ID: <032.f9b631ce7a6fb9fe1c72c9ea2d6738a7@pyamf.org> #440: epydoc signatures should be added to all util.StringIOProxy, util.DataTypeMixIn and util.BufferedByteStream classes ---------------------------+------------------------------------------------ Reporter: nick | Owner: thijs Type: defect | Status: new Priority: minor | Milestone: 0.5 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 21:17:40 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 20:17:40 -0000 Subject: [pyamf-tickets] #423: Add a consume method that will chop the head off the data stream at the current stream position. In-Reply-To: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> References: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> Message-ID: <041.9d868d003d7a6c6550f81839034f3da3@pyamf.org> #423: Add a consume method that will chop the head off the data stream at the current stream position. -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: assigned Priority: minor | Milestone: 0.4 Component: Utility | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * keywords: review => * owner: thijs => nick Comment: Unit tests, EchoTest and ParseDump succeed. After replacing {{{`tell()`}}} with {{{C{tell()}}}}, duplicating the {{{consume}}} docs into util.pyx, and adding a changelog entry it can be merged. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 21:25:22 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 20:25:22 -0000 Subject: [pyamf-tickets] #422: Add read/write_24bit_uint to util.DataTypeMixIn. In-Reply-To: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> References: <032.a3a37c612cdb624de6bdfa9337d47156@pyamf.org> Message-ID: <041.906bcf1bb12e66c6b6893c5c54c0afd9@pyamf.org> #422: Add read/write_24bit_uint to util.DataTypeMixIn. --------------------------+------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: closed Priority: minor | Milestone: 0.4 Component: Utility | Version: Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: `rtype` and `return` signatures have been given their own ticket #440. Merged to source:pyamf/branches/release-0.4 in r2041 -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 21:28:46 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 20:28:46 -0000 Subject: [pyamf-tickets] #435: Return XML instead of XMLDocument In-Reply-To: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> References: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> Message-ID: <042.32ac72c35579c6a92cbfbbff0908ab00@pyamf.org> #435: Return XML instead of XMLDocument ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.5 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by thijs): * milestone: 0.4 => 0.5 -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 21:36:04 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 20:36:04 -0000 Subject: [pyamf-tickets] #423: Add a consume method that will chop the head off the data stream at the current stream position. In-Reply-To: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> References: <032.32e06a9c64d540dadd902901bb917a11@pyamf.org> Message-ID: <041.73ee26f72bd1d6bd97f1e59c4dd14177@pyamf.org> #423: Add a consume method that will chop the head off the data stream at the current stream position. --------------------------+------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: closed Priority: minor | Milestone: 0.4 Component: Utility | Version: 0.4 Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Merged to source:pyamf/branches/release-0.4 in r2043. -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 21:39:42 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 20:39:42 -0000 Subject: [pyamf-tickets] #432: Only run PyFlakes on the pyamf tree In-Reply-To: <032.1ff1eecc791e299b7f6eec5aa9d728f7@pyamf.org> References: <032.1ff1eecc791e299b7f6eec5aa9d728f7@pyamf.org> Message-ID: <041.0a51fe55f1b052500e75326994ed0297@pyamf.org> #432: Only run PyFlakes on the pyamf tree ---------------------+------------------------------------------------------ Reporter: nick | Owner: thijs Type: task | Status: accepted Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Changes (by thijs): * status: new => accepted * milestone: => 0.5 -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 22:12:11 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 21:12:11 -0000 Subject: [pyamf-tickets] #432: Only run PyFlakes on the pyamf tree In-Reply-To: <032.1ff1eecc791e299b7f6eec5aa9d728f7@pyamf.org> References: <032.1ff1eecc791e299b7f6eec5aa9d728f7@pyamf.org> Message-ID: <041.cdb96f026a7db6640e61a0595c63c964@pyamf.org> #432: Only run PyFlakes on the pyamf tree ----------------------+----------------------------------------------------- Reporter: nick | Owner: thijs Type: task | Status: closed Priority: minor | Milestone: 0.4 Component: Testing | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by thijs): * status: accepted => closed * resolution: => fixed * milestone: 0.5 => 0.4 Comment: Fixed with r2045 -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 22:24:56 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 21:24:56 -0000 Subject: [pyamf-tickets] #440: epydoc signatures should be added to all util.StringIOProxy, util.DataTypeMixIn and util.BufferedByteStream classes In-Reply-To: <032.f9b631ce7a6fb9fe1c72c9ea2d6738a7@pyamf.org> References: <032.f9b631ce7a6fb9fe1c72c9ea2d6738a7@pyamf.org> Message-ID: <041.7487abed9bcae48fe0c74a098d1b2c38@pyamf.org> #440: epydoc signatures should be added to all util.StringIOProxy, util.DataTypeMixIn and util.BufferedByteStream classes ---------------------------+------------------------------------------------ Reporter: nick | Owner: thijs Type: defect | Status: new Priority: minor | Milestone: 0.5 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Comment(by thijs): I ran the epydoc check command on the trunk, results below: {{{ $ epydoc --check pyamf/util/ Warning: Undocumented: - pyamf.util.BufferedByteStream.__add__() - pyamf.util.DataTypeMixIn.ENDIAN_BIG - pyamf.util.DataTypeMixIn.ENDIAN_LITTLE - pyamf.util.DataTypeMixIn.ENDIAN_NATIVE - pyamf.util.DataTypeMixIn.ENDIAN_NETWORK - pyamf.util.DataTypeMixIn.endian - pyamf.util.IndexedCollection.__contains__() - pyamf.util.IndexedCollection.__eq__() - pyamf.util.IndexedCollection.__getitem__() - pyamf.util.IndexedCollection.__init__() - pyamf.util.IndexedCollection.__iter__() - pyamf.util.IndexedCollection.__len__() - pyamf.util.IndexedCollection.append() - pyamf.util.IndexedCollection.clear() - pyamf.util.IndexedCollection.getByReference() - pyamf.util.IndexedCollection.getReferenceTo() - pyamf.util.IndexedCollection.remove() - pyamf.util.IndexedMap.__init__() - pyamf.util.IndexedMap.append() - pyamf.util.IndexedMap.clear() - pyamf.util.IndexedMap.getMappedByReference() - pyamf.util.IndexedMap.map() - pyamf.util.IndexedMap.remove() - pyamf.util.StringIOProxy.__len__() - pyamf.util.StringIOProxy.close() - pyamf.util.StringIOProxy.flush() - pyamf.util.StringIOProxy.getvalue() - pyamf.util.StringIOProxy.next() - pyamf.util.StringIOProxy.read() - pyamf.util.StringIOProxy.readline() - pyamf.util.StringIOProxy.seek() - pyamf.util.StringIOProxy.tell() - pyamf.util.StringIOProxy.truncate() - pyamf.util.StringIOProxy.write() - pyamf.util.StringIOProxy.writelines() - pyamf.util.get_class_alias() - pyamf.util.imports.PY_EXT - pyamf.util.imports.loadedModules - pyamf.util.imports.postLoadHooks - pyamf.util.negative_timestamp_broken - pyamf.util.read_double_workaround() - pyamf.util.write_double_workaround() - pyamf.util.xml_types Warning: No description: - object.__new__() - pyamf.util.IndexedCollection - pyamf.util.StringIOProxy.readlines() }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 13 22:28:01 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 13 Jan 2009 21:28:01 -0000 Subject: [pyamf-tickets] #419: Put the changelog in the API docs In-Reply-To: <033.209be78cfaf0e68649600fc3e938e6ea@pyamf.org> References: <033.209be78cfaf0e68649600fc3e938e6ea@pyamf.org> Message-ID: <042.4b783c6471dfca07d8e73fdeaadf3459@pyamf.org> #419: Put the changelog in the API docs ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: enhancement | Status: accepted Priority: minor | Milestone: 0.5 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Changes (by thijs): * priority: major => minor * status: new => accepted Comment: This can be done by adding the following option to [source:pyamf/trunk/setup.cfg]: {{{ # An alternative help file. The named file should contain the # body of an HTML file; navigation bars will be added to it. help: my_helpfile.html }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 14 01:02:49 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 14 Jan 2009 00:02:49 -0000 Subject: [pyamf-tickets] #419: Put the changelog in the API docs In-Reply-To: <033.209be78cfaf0e68649600fc3e938e6ea@pyamf.org> References: <033.209be78cfaf0e68649600fc3e938e6ea@pyamf.org> Message-ID: <042.068728ad160879803170c24f67b73b06@pyamf.org> #419: Put the changelog in the API docs ----------------------------+----------------------------------------------- Reporter: thijs | Owner: thijs Type: enhancement | Status: closed Priority: minor | Milestone: 0.4 Component: Documentation | Version: 0.4 Resolution: fixed | Keywords: ----------------------------+----------------------------------------------- Changes (by thijs): * status: accepted => closed * resolution: => fixed * milestone: 0.5 => 0.4 Comment: Fixed with r2051 -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 14 02:19:30 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 14 Jan 2009 01:19:30 -0000 Subject: [pyamf-tickets] #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. In-Reply-To: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> References: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> Message-ID: <045.8e4f41b8989fe6284685f3e9468c992e@pyamf.org> #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: dthompso Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Comment(by nick): I found an obscure bug in AMF3 that didn't handle anonymous classes and class definition references correctly, which I committed to the branch - the build slaves were showing test failures. Code & tests & EchoTest look good. Please merge. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 14 19:53:54 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 14 Jan 2009 18:53:54 -0000 Subject: [pyamf-tickets] #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. In-Reply-To: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> References: <036.823d37e3e618294eb4330e447c0a78a2@pyamf.org> Message-ID: <045.83cb7b25773f2086f45ebf323a79c2b0@pyamf.org> #436: Upgrade from SA 0.5.0rc4 to 0.5.0 causes SQLAlchemy adapter tests to fail. -----------------------+---------------------------------------------------- Reporter: dthompso | Owner: dthompso Type: defect | Status: closed Priority: blocker | Milestone: 0.4 Component: Adapters | Version: 0.4 Resolution: fixed | Keywords: -----------------------+---------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Merged this to source:pyamf/branches/release-0.4 as we're pushing 0.4rc3. -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 14 22:43:09 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 14 Jan 2009 21:43:09 -0000 Subject: [pyamf-tickets] #430: Release 0.4rc3 In-Reply-To: <033.c022fd46085140a368c91facf2af7613@pyamf.org> References: <033.c022fd46085140a368c91facf2af7613@pyamf.org> Message-ID: <042.9899fd93cc7595c27bf66b804e7c77f5@pyamf.org> #430: Release 0.4rc3 ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: closed Priority: blocker | Milestone: 0.4 Component: Website | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by thijs): * status: new => closed * component: Testing => Website * resolution: => fixed Comment: Fixed with r2063 -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 15 05:39:27 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 15 Jan 2009 04:39:27 -0000 Subject: [pyamf-tickets] #441: 2052 Breaks _sqlalchemy adapter Message-ID: <036.ba16b2d06cb56da2bf08e32d0894e88f@pyamf.org> #441: 2052 Breaks _sqlalchemy adapter ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- The getLazyAttrs method does not work correctly. You can't determine which attributes are lazy on a class wide basis. Which attributes are lazy is specific to an individual object, and is determined by how the object was originally queried, and if the lazy-loaded attributes have been accessed (at which time SA automatically loads them). You also can't use the mapper to determine which attributes are lazy, because prop.lazy is an attribute that tells SA how to perform a query, not whether an individual object has loaded that attribute yet. Similarly, in the ApplyAttributes method, you must use the lazy attribute list that came from the client, because the client may have loaded some of those attributes after the persistent object was originally queried and encoded. -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 15 13:18:40 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 15 Jan 2009 12:18:40 -0000 Subject: [pyamf-tickets] #441: 2052 Breaks _sqlalchemy adapter In-Reply-To: <036.ba16b2d06cb56da2bf08e32d0894e88f@pyamf.org> References: <036.ba16b2d06cb56da2bf08e32d0894e88f@pyamf.org> Message-ID: <045.9d2e35fedbece960cabc17a560975c53@pyamf.org> #441: 2052 Breaks _sqlalchemy adapter ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: dthompso Type: defect | Status: assigned Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: review | ----------------------+----------------------------------------------------- Changes (by nick): * keywords: => review * status: new => assigned * owner: nick => dthompso Comment: Yep, using class lazy attrs is not the right thing to do here .. I have attached a diff which corrects this behaviour -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 15 20:26:01 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 15 Jan 2009 19:26:01 -0000 Subject: [pyamf-tickets] #441: 2052 Breaks _sqlalchemy adapter In-Reply-To: <036.ba16b2d06cb56da2bf08e32d0894e88f@pyamf.org> References: <036.ba16b2d06cb56da2bf08e32d0894e88f@pyamf.org> Message-ID: <045.b01e82c47e0ba1cd85e6a845023eb2b9@pyamf.org> #441: 2052 Breaks _sqlalchemy adapter ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: dthompso Type: defect | Status: assigned Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: review | ----------------------+----------------------------------------------------- Comment(by dthompso): Patch looks good and works with our system. Thanks! -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 15 21:10:10 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 15 Jan 2009 20:10:10 -0000 Subject: [pyamf-tickets] #252: Integrate egg building into the buildslave (was: Add egg export feature to package script) In-Reply-To: <033.71bde58a1920b3944fc7c735254710e3@pyamf.org> References: <033.71bde58a1920b3944fc7c735254710e3@pyamf.org> Message-ID: <042.986cae6a055da8c4708f2591b6826cd7@pyamf.org> #252: Integrate egg building into the buildslave -----------------------+---------------------------------------------------- Reporter: thijs | Owner: nick Type: task | Status: new Priority: minor | Milestone: At some point Component: Installer | Version: 0.3 Keywords: | -----------------------+---------------------------------------------------- Old description: > The [source:pyamf/sandbox/release/package.py package script] currently > doesn't create any .egg files. It should be able to do this for multiple > versions of Python. New description: The platform-specific eggs should be build by the buildslaves and uploaded to the master. -- Comment(by thijs): Sounds good, updated the ticket summary and description. -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 15 21:23:01 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 15 Jan 2009 20:23:01 -0000 Subject: [pyamf-tickets] #442: Fix custom Test buildstep that marks failed tests as successful Message-ID: <033.a0b0a49c3dea17d19a1228735a4d031d@pyamf.org> #442: Fix custom Test buildstep that marks failed tests as successful ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.4 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ The buildslave marks test runs as successful when they're failing, which can be seen [http://buildbot.pyamf.org/builders/x86-macosx- py25/builds/64/steps/python2.5-test_2/logs/stdio here] for example. This is a bug in our custom [source:/pyamf/sandbox/buildbot/pyamf.py test buildstep] and can be fixed by following the [http://buildbot.net/trac/ticket/275 instructions] from the buildbot developers. -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 15 21:27:16 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 15 Jan 2009 20:27:16 -0000 Subject: [pyamf-tickets] #442: Fix custom Test buildstep that marks failed tests as successful In-Reply-To: <033.a0b0a49c3dea17d19a1228735a4d031d@pyamf.org> References: <033.a0b0a49c3dea17d19a1228735a4d031d@pyamf.org> Message-ID: <042.5c29a132d22161aac3e1ce982625c9c9@pyamf.org> #442: Fix custom Test buildstep that marks failed tests as successful ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.4 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Comment(by thijs): Made an update in r2065 based on the perl test buildstep, but probably still needs some work (regexp) and testing. -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 15 23:34:17 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 15 Jan 2009 22:34:17 -0000 Subject: [pyamf-tickets] #441: 2052 Breaks _sqlalchemy adapter In-Reply-To: <036.ba16b2d06cb56da2bf08e32d0894e88f@pyamf.org> References: <036.ba16b2d06cb56da2bf08e32d0894e88f@pyamf.org> Message-ID: <045.eb07a173e07bad96459ca24e1a73e0a4@pyamf.org> #441: 2052 Breaks _sqlalchemy adapter ----------------------+----------------------------------------------------- Reporter: dthompso | Owner: nick Type: defect | Status: accepted Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by nick): * keywords: review => * status: assigned => accepted * owner: dthompso => nick Comment: Branching to source:pyamf/branches/sa-lazy-attrs-441 -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 15 23:43:33 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 15 Jan 2009 22:43:33 -0000 Subject: [pyamf-tickets] #441: 2052 Breaks _sqlalchemy adapter In-Reply-To: <036.ba16b2d06cb56da2bf08e32d0894e88f@pyamf.org> References: <036.ba16b2d06cb56da2bf08e32d0894e88f@pyamf.org> Message-ID: <045.e20452075fffbe64bea05cd35d434b2a@pyamf.org> #441: 2052 Breaks _sqlalchemy adapter -----------------------+---------------------------------------------------- Reporter: dthompso | Owner: nick Type: defect | Status: closed Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Resolution: fixed | Keywords: -----------------------+---------------------------------------------------- Changes (by nick): * status: accepted => closed * resolution: => fixed -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 16 00:22:00 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 15 Jan 2009 23:22:00 -0000 Subject: [pyamf-tickets] #442: Fix custom Test buildstep that marks failed tests as successful In-Reply-To: <033.a0b0a49c3dea17d19a1228735a4d031d@pyamf.org> References: <033.a0b0a49c3dea17d19a1228735a4d031d@pyamf.org> Message-ID: <042.ff62dc465f86c0499ad4ec0e9904acb5@pyamf.org> #442: Fix custom Test buildstep that marks failed tests as successful ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: closed Priority: major | Milestone: 0.4 Component: Testing | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by nick): * status: new => closed * resolution: => fixed Comment: This has now been sorted check the [http://buildbot.pyamf/waterfall waterfall] -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 16 10:53:06 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 16 Jan 2009 09:53:06 -0000 Subject: [pyamf-tickets] #443: Implement auto aliasing Message-ID: <032.5797f786ec9d31c4d52d60730a5be07a@pyamf.org> #443: Implement auto aliasing -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: new Priority: major | Milestone: Component: Encoder | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- I was reading up on some [http://marxsoftware.blogspot.com/2009/01/bare- bones-blazeds-object-remoting.html BlazeDS magikery] and it appears that it supports auto aliasing .. that is when an instance is fed into the encoder its full package/module name + class name is automatically registered (server side at least), presumably if not already registered. This is something that PyAMF ought to support - it would get us out of a lot of jams regarding decoding untyped objects - especially with SQLAlchemy. The feature should be optional as not to break backward compatibility (we may set this as the default for 0.5). From the linked blog post: {{{ #!python # file-name: dustin.py class Person(object): __slots__ = ('firstName', 'lastName') def __str__(self): return '%s %s' % (self.firstName, self.lastName) }}} {{{ #!python # file-name: gateway.py from dustin import Person class HelloWorldRemotingServer(object): def processHello(self, name): return "Hello, %s!" % (name,) def processName(self, p): assert isinstance(p, Person) return "Your name is %s, %s %s!" % (p.lastName, p.firstName, p.lastName) services = { 'HelloWorld': HelloWorldRemotingServer() } if __name__ == '__main__': from pyamf.remoting.gateway.wsgi import WSGIGateway from wsgiref import simple_server gw = WSGIGateway(services) httpd = simple_server.WSGIServer( ('localhost', 8000), simple_server.WSGIRequestHandler, ) httpd.set_app(gw) try: httpd.serve_forever() except (KeyboardInterrupt, SystemExit): pass }}} Look mum - no XML! -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 16 11:37:17 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 16 Jan 2009 10:37:17 -0000 Subject: [pyamf-tickets] #444: BufferedByteStream.truncate(100) doesn't work as expected Message-ID: <032.16909237061b20c2515a9811661a6570@pyamf.org> #444: BufferedByteStream.truncate(100) doesn't work as expected ---------------------+------------------------------------------------------ Reporter: nick | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.4 Component: Utility | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ {{{ #!python from pyamf.util import BufferedByteStream x = BufferedByteStream('hello') x.truncate(3) assert x.getvalue() == 'hel' }}} The actual value is `''`. -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 16 12:03:40 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 16 Jan 2009 11:03:40 -0000 Subject: [pyamf-tickets] #444: BufferedByteStream.truncate(100) doesn't work as expected In-Reply-To: <032.16909237061b20c2515a9811661a6570@pyamf.org> References: <032.16909237061b20c2515a9811661a6570@pyamf.org> Message-ID: <041.48201977fd21966afd37a63c35a1b09f@pyamf.org> #444: BufferedByteStream.truncate(100) doesn't work as expected ---------------------+------------------------------------------------------ Reporter: nick | Owner: nick Type: defect | Status: accepted Priority: major | Milestone: 0.4 Component: Utility | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Changes (by nick): * status: new => accepted Comment: Branching to source:pyamf/branches/truncate-444 -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 16 12:04:16 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 16 Jan 2009 11:04:16 -0000 Subject: [pyamf-tickets] #444: BufferedByteStream.truncate(100) doesn't work as expected In-Reply-To: <032.16909237061b20c2515a9811661a6570@pyamf.org> References: <032.16909237061b20c2515a9811661a6570@pyamf.org> Message-ID: <041.adfda6f725c6c533a48128864c2da473@pyamf.org> #444: BufferedByteStream.truncate(100) doesn't work as expected ---------------------+------------------------------------------------------ Reporter: nick | Owner: feisley Type: defect | Status: assigned Priority: major | Milestone: 0.4 Component: Utility | Version: 0.4 Keywords: review | ---------------------+------------------------------------------------------ Changes (by nick): * keywords: => review * status: accepted => assigned * owner: nick => feisley Comment: Buildslaves look good. -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 16 20:01:55 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 16 Jan 2009 19:01:55 -0000 Subject: [pyamf-tickets] #420: Create example that uses the SQLAlchemy Adapter In-Reply-To: <033.50980369e7f89a7c2776b18e6efa6bcf@pyamf.org> References: <033.50980369e7f89a7c2776b18e6efa6bcf@pyamf.org> Message-ID: <042.c81b7553f177ac0ea40fe07fd396ef94@pyamf.org> #420: Create example that uses the SQLAlchemy Adapter ----------------------+----------------------------------------------------- Reporter: thijs | Owner: dthompso Type: task | Status: assigned Priority: major | Milestone: 0.5 Component: Examples | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Comment(by dthompso): I committed some example code that needs to be reviewed. [http://pyamf.org/browser/examples/branches/sqlalchemy_examples_420 example] -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 12:19:52 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 11:19:52 -0000 Subject: [pyamf-tickets] #429: Grab version nr for setuptools from pyamf.__version__ In-Reply-To: <033.2494d02167f54b117ea00871f6dcefee@pyamf.org> References: <033.2494d02167f54b117ea00871f6dcefee@pyamf.org> Message-ID: <042.0f2ed0b0db577b455946d9f569884ecc@pyamf.org> #429: Grab version nr for setuptools from pyamf.__version__ -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: accepted Priority: minor | Milestone: 0.5 Component: Installer | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by nick): * status: new => accepted Comment: Branching to source:pyamf/branches/setup-version-429 -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 12:57:51 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 11:57:51 -0000 Subject: [pyamf-tickets] #429: Grab version nr for setuptools from pyamf.__version__ In-Reply-To: <033.2494d02167f54b117ea00871f6dcefee@pyamf.org> References: <033.2494d02167f54b117ea00871f6dcefee@pyamf.org> Message-ID: <042.4d17d4d8c33c0081c24478acc7d944bc@pyamf.org> #429: Grab version nr for setuptools from pyamf.__version__ -------------------------+-------------------------------------------------- Reporter: thijs | Owner: thijs Type: enhancement | Status: assigned Priority: minor | Milestone: 0.5 Component: Installer | Version: 0.4 Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * keywords: => review * status: accepted => assigned * owner: nick => thijs -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 20:14:31 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 19:14:31 -0000 Subject: [pyamf-tickets] #269: Issues with PyAMF and Jython In-Reply-To: <033.e52e403024bdb47ab854aeb6669eb8cc@pyamf.org> References: <033.e52e403024bdb47ab854aeb6669eb8cc@pyamf.org> Message-ID: <042.efdcaf0fbbbd95573edece3486d07e5e@pyamf.org> #269: Issues with PyAMF and Jython -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: accepted Priority: minor | Milestone: 0.5 Component: Testing | Version: 0.3 Keywords: | -------------------------+-------------------------------------------------- Old description: > I tested PyAMF on [http://www.jython.org Jython] with different versions > and quite a few tests failed: > > - PyAMF r1441 and Jython - trunk > [http://fisheye3.atlassian.com/changelog/jython/?cs=4725 r4725] > ([attachment:jython-r4725.log log]) > - PyAMF r1458 and Jython - trunk > [http://fisheye3.atlassian.com/changelog/jython/?cs=4758 r4758] > ([attachment:jython-r4758.log log]) > - PyAMF r1531 and Jython - trunk > [http://fisheye3.atlassian.com/changelog/jython/?cs=4927 r4927] > (tests=427, failures=19, errors=125) > - PyAMF r1586 and Jython - asm branch > [http://fisheye3.atlassian.com/changelog/jython/?cs=5026 r5026] > ([http://buildbot.pyamf.org/builders/amd64-ubuntu-jython/builds/6/steps > /jython-test/logs/stdio/text failures=15, errors=14)] > - PyAMF r1597 and Jython - trunk > [http://fisheye3.atlassian.com/changelog/jython/?cs=5215 r5215] > ([http://buildbot.pyamf.org/builders/amd64-ubuntu-jython/builds/18/steps > /jython-test/logs/stdio/text failures=18, errors=1]) > - PyAMF r1699 and Jython - trunk > [http://fisheye3.atlassian.com/changelog/jython/?cs=5372 r5372] > ([http://buildbot.pyamf.org/builders/amd64-ubuntu-jython/builds/103/steps > /jython-test/logs/stdio/text failures=15, errors=1]) > - PyAMF r1848 and Jython - trunk > [http://fisheye3.atlassian.com/changelog/jython/?cs=5770 r5770] > ([http://buildbot.pyamf.org/builders/amd64-ubuntu-jython/builds/108/steps > /jython-test/logs/stdio/text failures=18, errors=1]) > > == How to reproduce == > > 1. Grab the Jython trunk: > {{{ > #!sh > svn co https://jython.svn.sourceforge.net/svnroot/jython/trunk jython- > trunk > }}} > > 2. Compile Jython and set {{{JYTHON_HOME}}}: > {{{ > #!sh > cd jython-trunk > ant > export JYTHON_HOME=/path/to/jython-trunk/dist > chmod 777 $JYTHON_HOME/bin/jython > }}} > > 3. Grab the PyAMF trunk, install setuptools with: > {{{ > #!sh > $JYTHON_HOME/bin/jython ez_setup.py > }}} > > 4. Run the tests from the PyAMF trunk: > {{{ > #!sh > $JYTHON_HOME/bin/jython setup.py test > }}} New description: I tested PyAMF on [http://www.jython.org Jython] with different versions and quite a few tests failed: - PyAMF r1441 and Jython - trunk [http://fisheye3.atlassian.com/changelog/jython/?cs=4725 r4725] ([attachment:jython-r4725.log log]) - PyAMF r1458 and Jython - trunk [http://fisheye3.atlassian.com/changelog/jython/?cs=4758 r4758] ([attachment:jython-r4758.log log]) - PyAMF r1531 and Jython - trunk [http://fisheye3.atlassian.com/changelog/jython/?cs=4927 r4927] (tests=427, failures=19, errors=125) - PyAMF r1586 and Jython - asm branch [http://fisheye3.atlassian.com/changelog/jython/?cs=5026 r5026] ([http://buildbot.pyamf.org/builders/amd64-ubuntu-jython/builds/6/steps /jython-test/logs/stdio/text failures=15, errors=14)] - PyAMF r1597 and Jython - trunk [http://fisheye3.atlassian.com/changelog/jython/?cs=5215 r5215] ([http://buildbot.pyamf.org/builders/amd64-ubuntu-jython/builds/18/steps /jython-test/logs/stdio/text failures=18, errors=1]) - PyAMF r1699 and Jython - trunk [http://fisheye3.atlassian.com/changelog/jython/?cs=5372 r5372] ([http://buildbot.pyamf.org/builders/amd64-ubuntu-jython/builds/103/steps /jython-test/logs/stdio/text failures=15, errors=1]) - PyAMF r1848 and Jython - trunk [http://fisheye3.atlassian.com/changelog/jython/?cs=5770 r5770] ([http://buildbot.pyamf.org/builders/amd64-ubuntu-jython/builds/108/steps /jython-test/logs/stdio/text failures=18, errors=1]) - PyAMF r2078 and Jython trunk [http://fisheye3.atlassian.com/changelog/jython/?cs=5939 r5939] [http://buildbot.pyamf.org/builders/jython25/builds/25/steps/python2.5-test_2/logs/stdio/text failures=4]) == How to reproduce == 1. Grab the Jython trunk: {{{ #!sh svn co https://jython.svn.sourceforge.net/svnroot/jython/trunk jython- trunk }}} 2. Compile Jython and set {{{JYTHON_HOME}}}: {{{ #!sh cd jython-trunk ant export JYTHON_HOME=/path/to/jython-trunk/dist chmod 777 $JYTHON_HOME/bin/jython }}} 3. Grab the PyAMF trunk, install setuptools with: {{{ #!sh $JYTHON_HOME/bin/jython ez_setup.py }}} 4. Run the tests from the PyAMF trunk: {{{ #!sh $JYTHON_HOME/bin/jython setup.py test }}} -- Comment(by thijs): Replying to [comment:15 thijs]: > Blocked by #353 and http://bugs.jython.org/issue1227 Both issues have been fixed in the Jython trunk now. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 20:16:08 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 19:16:08 -0000 Subject: [pyamf-tickets] #353: Bytearray test hack showing in Jython In-Reply-To: <033.7ab88d6b724bc380e58306e1cbfc2367@pyamf.org> References: <033.7ab88d6b724bc380e58306e1cbfc2367@pyamf.org> Message-ID: <042.07c271e711bc8714c333f749a3973549@pyamf.org> #353: Bytearray test hack showing in Jython ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: task | Status: closed Priority: minor | Milestone: 0.4 Component: Testing | Version: 0.3.1 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by thijs): * status: accepted => closed * resolution: => fixed * milestone: 0.5 => 0.4 Comment: Fixed in Jython's trunk (r5938) and the test is now passing. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 20:24:34 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 19:24:34 -0000 Subject: [pyamf-tickets] #445: Setup weekly bug report mail Message-ID: <033.2d3411dddfc9117ee0eb6b5e7df761e8@pyamf.org> #445: Setup weekly bug report mail ---------------------+------------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: new Priority: major | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Twisted has a weekly bug report email that is send to their main mailinglist. Would be cool to have something similar for PyAMF. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 20:24:44 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 19:24:44 -0000 Subject: [pyamf-tickets] #437: Move Jython buildslave to different server In-Reply-To: <033.f16137b48b0e77b18c75dc4812cf1203@pyamf.org> References: <033.f16137b48b0e77b18c75dc4812cf1203@pyamf.org> Message-ID: <042.327a20a25c4c2838bcdd0ae752503815@pyamf.org> #437: Move Jython buildslave to different server ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: task | Status: closed Priority: major | Milestone: 0.5 Component: Testing | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by nick): * status: new => closed * resolution: => fixed Comment: The Jython buildslave has now been moved to callisto. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 20:40:28 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 19:40:28 -0000 Subject: [pyamf-tickets] #429: Grab version nr for setuptools from pyamf.__version__ In-Reply-To: <033.2494d02167f54b117ea00871f6dcefee@pyamf.org> References: <033.2494d02167f54b117ea00871f6dcefee@pyamf.org> Message-ID: <042.b09289bb982ca0291e4f94ab44bd9985@pyamf.org> #429: Grab version nr for setuptools from pyamf.__version__ -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: assigned Priority: minor | Milestone: 0.4 Component: Installer | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * keywords: review => * owner: thijs => nick * milestone: 0.5 => 0.4 Comment: I guess an entry in the changelog would be useful when you merge it. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 20:51:23 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 19:51:23 -0000 Subject: [pyamf-tickets] #429: Grab version nr for setuptools from pyamf.__version__ In-Reply-To: <033.2494d02167f54b117ea00871f6dcefee@pyamf.org> References: <033.2494d02167f54b117ea00871f6dcefee@pyamf.org> Message-ID: <042.6d58786a8a999a7dbeaa7b21783996b8@pyamf.org> #429: Grab version nr for setuptools from pyamf.__version__ --------------------------+------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: closed Priority: minor | Milestone: 0.4 Component: Installer | Version: 0.4 Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Fixed in r2080. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 20:52:14 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 19:52:14 -0000 Subject: [pyamf-tickets] #438: Setup PyAMF rsync backup In-Reply-To: <033.4bccdfb705c5fd749ecc83f062fdf762@pyamf.org> References: <033.4bccdfb705c5fd749ecc83f062fdf762@pyamf.org> Message-ID: <042.3243eca7621463a35066db56b3b58e00@pyamf.org> #438: Setup PyAMF rsync backup ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: assigned Priority: critical | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by nick): * status: new => assigned * owner: feisley => thijs Comment: We need some permissions setup on saturn to achieve this. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 20:55:58 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 19:55:58 -0000 Subject: [pyamf-tickets] #85: Twisted WSGI adaptor In-Reply-To: <033.9fa0e1dc855ed88894db0168560e2f25@pyamf.org> References: <033.9fa0e1dc855ed88894db0168560e2f25@pyamf.org> Message-ID: <042.1db94ff01a2dd1cf412937efd166c9c4@pyamf.org> #85: Twisted WSGI adaptor --------------------------+------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: closed Priority: minor | Milestone: At some point Component: Gateway | Version: 0.1a Resolution: wontfix | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: new => closed * resolution: => wontfix Comment: web2 is now deprecated so this is no longer required. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 21:02:55 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 20:02:55 -0000 Subject: [pyamf-tickets] #85: Twisted WSGI adaptor In-Reply-To: <033.9fa0e1dc855ed88894db0168560e2f25@pyamf.org> References: <033.9fa0e1dc855ed88894db0168560e2f25@pyamf.org> Message-ID: <042.b8f54c5afef8cb0eb25c93dbbedd3174@pyamf.org> #85: Twisted WSGI adaptor --------------------------+------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: reopened Priority: minor | Milestone: At some point Component: Gateway | Version: Resolution: | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: closed => reopened * version: 0.1a => * resolution: wontfix => Comment: Re-opening this because wsgi is supported in `twisted.web`. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 21:17:18 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 20:17:18 -0000 Subject: [pyamf-tickets] #446: Jython example Message-ID: <033.e8def5e28b3a79fb81472dbe806c7287@pyamf.org> #446: Jython example ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: new Priority: major | Milestone: 0.5 Component: Examples | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Now that the test suite passes on Jython 2.5 it would be cool to have a Jython example showing how to use PyAMF with Java. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 21:28:26 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 20:28:26 -0000 Subject: [pyamf-tickets] #420: Create example that uses the SQLAlchemy Adapter In-Reply-To: <033.50980369e7f89a7c2776b18e6efa6bcf@pyamf.org> References: <033.50980369e7f89a7c2776b18e6efa6bcf@pyamf.org> Message-ID: <042.2ff50201f5db57715d1b3532af57a8ad@pyamf.org> #420: Create example that uses the SQLAlchemy Adapter ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: task | Status: accepted Priority: major | Milestone: 0.5 Component: Examples | Version: 0.4 Keywords: review | ----------------------+----------------------------------------------------- Changes (by nick): * keywords: => review * status: assigned => accepted * owner: dthompso => nick -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 21:33:27 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 20:33:27 -0000 Subject: [pyamf-tickets] #444: BufferedByteStream.truncate(100) doesn't work as expected In-Reply-To: <032.16909237061b20c2515a9811661a6570@pyamf.org> References: <032.16909237061b20c2515a9811661a6570@pyamf.org> Message-ID: <041.50a1b98f56326ab7929eae26acd9a079@pyamf.org> #444: BufferedByteStream.truncate(100) doesn't work as expected ---------------------+------------------------------------------------------ Reporter: nick | Owner: nick Type: defect | Status: assigned Priority: major | Milestone: 0.4 Component: Utility | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Changes (by thijs): * keywords: review => * owner: feisley => nick Comment: Merge with a changelog entry, thx. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 21:37:08 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 20:37:08 -0000 Subject: [pyamf-tickets] #447: test_amf3.ComplexEncodingTestCase failing for Jyton Message-ID: <033.d86c3b90679015b09a4c1f3b8a903bc9@pyamf.org> #447: test_amf3.ComplexEncodingTestCase failing for Jyton ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.5 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ From the buildslave [http://buildbot.pyamf.org/builders/jython25/builds/30/steps/python2.5-test_2/logs/stdio log]: {{{ FAIL: test_complex_dict (pyamf.tests.test_amf3.ComplexEncodingTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/buildbot/slaves/pyamf/jython25/build/pyamf/tests/test_amf3.py", line 1624, in test_complex_dict self.complex_test() File "/home/buildbot/slaves/pyamf/jython25/build/pyamf/tests/test_amf3.py", line 1613, in complex_test self.assertEquals(self.TestSubObject, class_defs[2].klass) AssertionError: != ====================================================================== FAIL: test_complex_encode_decode_dict (pyamf.tests.test_amf3.ComplexEncodingTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/buildbot/slaves/pyamf/jython25/build/pyamf/tests/test_amf3.py", line 1632, in test_complex_encode_decode_dict self.complex_encode_decode_test(decoded['objects']) File "/home/buildbot/slaves/pyamf/jython25/build/pyamf/tests/test_amf3.py", line 1618, in complex_encode_decode_test self.assertEquals(self.TestSubObject, obj.sub_obj.__class__) AssertionError: != ---------------------------------------------------------------------- }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 21:40:55 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 20:40:55 -0000 Subject: [pyamf-tickets] #444: BufferedByteStream.truncate(100) doesn't work as expected In-Reply-To: <032.16909237061b20c2515a9811661a6570@pyamf.org> References: <032.16909237061b20c2515a9811661a6570@pyamf.org> Message-ID: <041.996567c657f9c058a126550b2bac8946@pyamf.org> #444: BufferedByteStream.truncate(100) doesn't work as expected ----------------------+----------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: closed Priority: major | Milestone: 0.4 Component: Utility | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Merged in r2082. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 21:51:14 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 20:51:14 -0000 Subject: [pyamf-tickets] #447: test_amf3.ComplexEncodingTestCase failing for Jython (was: test_amf3.ComplexEncodingTestCase failing for Jyton) In-Reply-To: <033.d86c3b90679015b09a4c1f3b8a903bc9@pyamf.org> References: <033.d86c3b90679015b09a4c1f3b8a903bc9@pyamf.org> Message-ID: <042.cdaeeb3c2540d0f8bfed0d29738926f5@pyamf.org> #447: test_amf3.ComplexEncodingTestCase failing for Jython ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.5 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Comment(by thijs): Fix typo -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 22:02:36 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 21:02:36 -0000 Subject: [pyamf-tickets] #443: Implement auto aliasing In-Reply-To: <032.5797f786ec9d31c4d52d60730a5be07a@pyamf.org> References: <032.5797f786ec9d31c4d52d60730a5be07a@pyamf.org> Message-ID: <041.91936abf5d6641638432488bf7d19ac6@pyamf.org> #443: Implement auto aliasing -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: new Priority: major | Milestone: At some point Component: Encoder | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * milestone: => At some point Comment: Assigning ticket to a milestone so it isnt singled out on the ticket overview page. -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 17 22:11:18 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 17 Jan 2009 21:11:18 -0000 Subject: [pyamf-tickets] #421: Add note about optional adapter/gateway dependencies in the installation instructions In-Reply-To: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> References: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> Message-ID: <042.b1aa041275eb047fcd026a8a30e3cf9e@pyamf.org> #421: Add note about optional adapter/gateway dependencies in the installation instructions ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: enhancement | Status: accepted Priority: major | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Changes (by thijs): * status: new => accepted * milestone: 0.5 => 0.4 -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 02:48:02 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 01:48:02 -0000 Subject: [pyamf-tickets] #448: test_infinites failing for Python 2.5 on win32 Message-ID: <033.16d8657be2ad2194fa3d68da8884078d@pyamf.org> #448: test_infinites failing for Python 2.5 on win32 ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: new Priority: blocker | Milestone: 0.4 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ See the buildslave [http://buildbot.pyamf.org/builders/winxp32-py25/builds/64/steps/python2.5-test_4/logs/stdio/text log]: {{{ =============================================================================== [FAIL]: pyamf.tests.test_amf0.DecoderTestCase.test_infinites Traceback (most recent call last): File "C:\Python25\lib\unittest.py", line 260, in run testMethod() File "c:\buildbot\pyamf\winxp32-py25\build\pyamf\tests\test_amf0.py", line 576, in test_infinites self.assertTrue(isNaN(x)) exceptions.AssertionError: =============================================================================== [FAIL]: pyamf.tests.test_amf3.DecoderTestCase.test_infinites Traceback (most recent call last): File "C:\Python25\lib\unittest.py", line 260, in run testMethod() File "c:\buildbot\pyamf\winxp32-py25\build\pyamf\tests\test_amf3.py", line 771, in test_infinites self.assertTrue(_util.isNaN(x)) exceptions.AssertionError: =============================================================================== [FAIL]: pyamf.tests.test_util.DataTypeMixInTestCase.test_nan Traceback (most recent call last): File "C:\Python25\lib\unittest.py", line 260, in run testMethod() File "c:\buildbot\pyamf\winxp32-py25\build\pyamf\tests\test_util.py", line 500, in test_nan self.assertTrue(_util.isNaN(x.read_double())) exceptions.AssertionError: ------------------------------------------------------------------------------- }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 03:09:44 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 02:09:44 -0000 Subject: [pyamf-tickets] #449: Support for SQLAlchemy 0.5.1 Message-ID: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> #449: Support for SQLAlchemy 0.5.1 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: new Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- [http://sqlalchemy.org SQLAlchemy 0.5.1] was released on Jan 17 and the test results now show {{{SADeprecationWarning}}}s: {{{ /home/thijs/pyamf/pyamf/tests/adapters/test_sqlalchemy.py:115: sqlalchemy.exc.SADeprecationWarning: Use session.add() [OK] pyamf.tests.adapters.test_sqlalchemy.SATestCase.test_encode_decode_persistent ... /home/thijs/pyamf/pyamf/tests/adapters/test_sqlalchemy.py:99: sqlalchemy.exc.SADeprecationWarning: Use session.add() [OK] pyamf.tests.adapters.test_sqlalchemy.SATestCase.test_encode_decode_transient ... [OK] pyamf.tests.adapters.test_sqlalchemy.SATestCase.test_encode_decode_with_references ... /home/thijs/pyamf/pyamf/tests/adapters/test_sqlalchemy.py:194: sqlalchemy.exc.SADeprecationWarning: Use session.add() [OK] pyamf.tests.adapters.test_sqlalchemy.SATestCase.test_lazy_load_attributes ... /home/thijs/pyamf/pyamf/tests/adapters/test_sqlalchemy.py:155: sqlalchemy.exc.SADeprecationWarning: Use session.add() /home/thijs/pyamf/pyamf/tests/adapters/test_sqlalchemy.py:157: sqlalchemy.exc.SADeprecationWarning: Use session.expunge_all() [OK] pyamf.tests.adapters.test_sqlalchemy.SATestCase.test_merge_with_lazy_loaded_attrs ... /home/thijs/pyamf/pyamf/tests/adapters/test_sqlalchemy.py:175: sqlalchemy.exc.SADeprecationWarning: Use session.add() /home/thijs/pyamf/pyamf/tests/adapters/test_sqlalchemy.py:177: sqlalchemy.exc.SADeprecationWarning: Use session.expunge_all() [OK] pyamf.tests.adapters.test_sqlalchemy.SATestCase.test_sa_merge ... /home/thijs/pyamf/pyamf/tests/adapters/test_sqlalchemy.py:137: sqlalchemy.exc.SADeprecationWarning: Use session.add() [OK] }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 03:36:44 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 02:36:44 -0000 Subject: [pyamf-tickets] #449: Support for SQLAlchemy 0.5.1 In-Reply-To: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> References: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> Message-ID: <042.4dd3579d5af85565aac5a5376637e560@pyamf.org> #449: Support for SQLAlchemy 0.5.1 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: new Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Comment(by thijs): I updated the tarball for the buildslaves to use 0.5.1. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 03:51:54 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 02:51:54 -0000 Subject: [pyamf-tickets] #450: Add cython to extras_require Message-ID: <033.59bd837b2638ba854cb8bb31954394b1@pyamf.org> #450: Add cython to extras_require -----------------------+---------------------------------------------------- Reporter: thijs | Owner: nick Type: task | Status: new Priority: major | Milestone: 0.4 Component: Installer | Version: 0.4 Keywords: | -----------------------+---------------------------------------------------- [http://cython.org Cython] is an optional extra required to build the C-extension, and should be added in setup.py. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 04:22:11 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 03:22:11 -0000 Subject: [pyamf-tickets] #421: Add note about optional adapter/gateway dependencies in the installation instructions In-Reply-To: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> References: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> Message-ID: <042.5337061b77f965001e046ca6a3525fbb@pyamf.org> #421: Add note about optional adapter/gateway dependencies in the installation instructions ---------------------------+------------------------------------------------ Reporter: thijs | Owner: nick Type: enhancement | Status: assigned Priority: major | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: review | ---------------------------+------------------------------------------------ Changes (by thijs): * keywords: => review * status: accepted => assigned * owner: thijs => nick Comment: See attached patch and updated [wiki:Install] page. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 04:27:23 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 03:27:23 -0000 Subject: [pyamf-tickets] #450: Add cython to extras_require In-Reply-To: <033.59bd837b2638ba854cb8bb31954394b1@pyamf.org> References: <033.59bd837b2638ba854cb8bb31954394b1@pyamf.org> Message-ID: <042.23c4b3f80eb67cc5008e3443d7859cd7@pyamf.org> #450: Add cython to extras_require -----------------------+---------------------------------------------------- Reporter: thijs | Owner: nick Type: task | Status: assigned Priority: major | Milestone: 0.4 Component: Installer | Version: 0.4 Keywords: review | -----------------------+---------------------------------------------------- Changes (by thijs): * keywords: => review * status: new => assigned Comment: See attached patch. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 09:38:02 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 08:38:02 -0000 Subject: [pyamf-tickets] #421: Add note about optional adapter/gateway dependencies in the installation instructions In-Reply-To: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> References: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> Message-ID: <042.6ab478326e5c51258f63437991876961@pyamf.org> #421: Add note about optional adapter/gateway dependencies in the installation instructions ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: enhancement | Status: assigned Priority: major | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Changes (by nick): * keywords: review => * owner: nick => thijs Comment: I wouldn't include Cython as part of the optional modules. We use Cython to build the cpyamf/*.c from cpyamf/*.pyx files and is purely a developers tool. But apart from that, good to go. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 10:24:43 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 09:24:43 -0000 Subject: [pyamf-tickets] #435: Return XML instead of XMLDocument In-Reply-To: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> References: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> Message-ID: <042.7fe42f397f6b7186c64029621683b13c@pyamf.org> #435: Return XML instead of XMLDocument ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: accepted Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by nick): * status: new => accepted * milestone: 0.5 => 0.4 -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 10:43:23 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 09:43:23 -0000 Subject: [pyamf-tickets] #435: Return XML instead of XMLDocument In-Reply-To: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> References: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> Message-ID: <042.239c85e70f38cf931eecbe59f81c0661@pyamf.org> #435: Return XML instead of XMLDocument ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: accepted Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Comment(by nick): Branching to source:pyamf/branches/xmldoc-xml-435 -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 10:47:27 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 09:47:27 -0000 Subject: [pyamf-tickets] #435: Return XML instead of XMLDocument In-Reply-To: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> References: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> Message-ID: <042.a25ba02bb65ebd751dc4d27da018620d@pyamf.org> #435: Return XML instead of XMLDocument ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: defect | Status: assigned Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: review | ----------------------+----------------------------------------------------- Changes (by nick): * keywords: => review * status: accepted => assigned * owner: nick => thijs Comment: I have added a `use_amf3` flag to `amf0.Encoder`. If client type is set to `pyamf.ClientTypes.Flash9` then this flag is set to `True`. At the moment, only `writeXML` takes any notice of this flag but the attached swf now does as expected (XML = True, XMLDocument = False). -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 12:10:13 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 11:10:13 -0000 Subject: [pyamf-tickets] #448: test_infinites failing for Python 2.5 on win32 In-Reply-To: <033.16d8657be2ad2194fa3d68da8884078d@pyamf.org> References: <033.16d8657be2ad2194fa3d68da8884078d@pyamf.org> Message-ID: <042.9390ec1613bc31fa8c4b05a14f88c876@pyamf.org> #448: test_infinites failing for Python 2.5 on win32 ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: accepted Priority: blocker | Milestone: 0.4 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Changes (by nick): * status: new => accepted Comment: Branching to source:pyamf/branches/infinites-win32-448 -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 15:03:23 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 14:03:23 -0000 Subject: [pyamf-tickets] #448: test_infinites failing for Python 2.5 on win32 In-Reply-To: <033.16d8657be2ad2194fa3d68da8884078d@pyamf.org> References: <033.16d8657be2ad2194fa3d68da8884078d@pyamf.org> Message-ID: <042.94096334b3330db7637c76c7b2690f98@pyamf.org> #448: test_infinites failing for Python 2.5 on win32 ---------------------+------------------------------------------------------ Reporter: thijs | Owner: thijs Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Testing | Version: 0.4 Keywords: review | ---------------------+------------------------------------------------------ Changes (by nick): * keywords: => review * status: accepted => assigned * owner: nick => thijs Comment: Clean bill of health from the buildslaves .. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 15:21:35 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 14:21:35 -0000 Subject: [pyamf-tickets] #449: Support for SQLAlchemy 0.5.1 In-Reply-To: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> References: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> Message-ID: <042.3b3dd844f4605c3b92d788fbba0f442c@pyamf.org> #449: Support for SQLAlchemy 0.5.1 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: accepted Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by nick): * status: new => accepted Comment: Branching to source:pyamf/branches/sa-0.5.1-compat-449 -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 15:22:47 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 14:22:47 -0000 Subject: [pyamf-tickets] #449: Support for SQLAlchemy 0.5.1 In-Reply-To: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> References: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> Message-ID: <042.326ffc701794b9fe65ae84b79afe1204@pyamf.org> #449: Support for SQLAlchemy 0.5.1 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: thijs Type: enhancement | Status: assigned Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * keywords: => review * status: accepted => assigned * owner: nick => thijs Comment: I have provided compatibility functions in the BaseTestCase. This removes the deprecation warnings when running with SQLAlchemy==0.5.1 -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 17:28:17 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 16:28:17 -0000 Subject: [pyamf-tickets] #450: Add cython to extras_require In-Reply-To: <033.59bd837b2638ba854cb8bb31954394b1@pyamf.org> References: <033.59bd837b2638ba854cb8bb31954394b1@pyamf.org> Message-ID: <042.6d08d9632590cb167883c8cb9370fa10@pyamf.org> #450: Add cython to extras_require -----------------------+---------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: assigned Priority: major | Milestone: 0.4 Component: Installer | Version: 0.4 Keywords: | -----------------------+---------------------------------------------------- Changes (by nick): * keywords: review => * owner: nick => thijs Comment: Looks good. Please apply/merge -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 17:35:56 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 16:35:56 -0000 Subject: [pyamf-tickets] #122: Setup documentation tools In-Reply-To: <033.4f5b96b2c71b6165196fe40774b0a8b3@pyamf.org> References: <033.4f5b96b2c71b6165196fe40774b0a8b3@pyamf.org> Message-ID: <042.ab7cfb59d9092779f7ffcc48d96bfe27@pyamf.org> #122: Setup documentation tools ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: task | Status: accepted Priority: critical | Milestone: 0.5 Component: Documentation | Version: Keywords: | ---------------------------+------------------------------------------------ Changes (by thijs): * keywords: review => * owner: nick => thijs * status: assigned => accepted -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 17:45:41 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 16:45:41 -0000 Subject: [pyamf-tickets] #450: Add cython to extras_require In-Reply-To: <033.59bd837b2638ba854cb8bb31954394b1@pyamf.org> References: <033.59bd837b2638ba854cb8bb31954394b1@pyamf.org> Message-ID: <042.4f252aca61ae9a32770f1b6a437e29a3@pyamf.org> #450: Add cython to extras_require ------------------------+--------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: closed Priority: major | Milestone: 0.4 Component: Installer | Version: 0.4 Resolution: fixed | Keywords: ------------------------+--------------------------------------------------- Changes (by thijs): * status: assigned => closed * resolution: => fixed Comment: Applied in r2093. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 17:55:33 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 16:55:33 -0000 Subject: [pyamf-tickets] #421: Add note about optional adapter/gateway dependencies in the installation instructions In-Reply-To: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> References: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> Message-ID: <042.0f9e94d2ce90e5a7624c6fc088747882@pyamf.org> #421: Add note about optional adapter/gateway dependencies in the installation instructions ---------------------------+------------------------------------------------ Reporter: thijs | Owner: nick Type: enhancement | Status: assigned Priority: major | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: review | ---------------------------+------------------------------------------------ Changes (by thijs): * keywords: => review * owner: thijs => nick Comment: I updated the patch and added a section for the C-extension. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 17:59:10 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 16:59:10 -0000 Subject: [pyamf-tickets] #421: Add note about optional adapter/gateway dependencies in the installation instructions In-Reply-To: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> References: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> Message-ID: <042.d6bc63452cff82b85d9c2952f1620f95@pyamf.org> #421: Add note about optional adapter/gateway dependencies in the installation instructions ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: enhancement | Status: assigned Priority: major | Milestone: 0.4 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ Changes (by nick): * keywords: review => * owner: nick => thijs Comment: Looks good. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 17:59:10 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 16:59:10 -0000 Subject: [pyamf-tickets] #449: Support for SQLAlchemy 0.5.1 In-Reply-To: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> References: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> Message-ID: <042.c9da07828c83d6eba1f11b0aba4392cf@pyamf.org> #449: Support for SQLAlchemy 0.5.1 -------------------------+-------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: assigned Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by thijs): * keywords: review => * owner: thijs => nick Comment: Looks good, please merge with a changelog entry. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 18:01:39 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 17:01:39 -0000 Subject: [pyamf-tickets] #448: test_infinites failing for Python 2.5 on win32 In-Reply-To: <033.16d8657be2ad2194fa3d68da8884078d@pyamf.org> References: <033.16d8657be2ad2194fa3d68da8884078d@pyamf.org> Message-ID: <042.3b3bfd9fa88a8368ab36084aae38e162@pyamf.org> #448: test_infinites failing for Python 2.5 on win32 ---------------------+------------------------------------------------------ Reporter: thijs | Owner: nick Type: defect | Status: assigned Priority: blocker | Milestone: 0.4 Component: Testing | Version: 0.4 Keywords: | ---------------------+------------------------------------------------------ Changes (by thijs): * keywords: review => * owner: thijs => nick Comment: I don't have access to a win32 machine so if the slaves are happy then I'm happy. Please merge with a changelog entry. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 18:07:45 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 17:07:45 -0000 Subject: [pyamf-tickets] #449: Support for SQLAlchemy 0.5.1 In-Reply-To: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> References: <033.af486a0778fabe312dcbeff035402b6b@pyamf.org> Message-ID: <042.c2d6f45335c10145c0179d31fe4d5760@pyamf.org> #449: Support for SQLAlchemy 0.5.1 --------------------------+------------------------------------------------- Reporter: thijs | Owner: nick Type: enhancement | Status: closed Priority: major | Milestone: 0.4 Component: Adapters | Version: 0.4 Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Merged in r2094. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 18:08:31 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 17:08:31 -0000 Subject: [pyamf-tickets] #435: Return XML instead of XMLDocument In-Reply-To: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> References: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> Message-ID: <042.816112ccfa445fcd1b9188353ed5187d@pyamf.org> #435: Return XML instead of XMLDocument ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: assigned Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by thijs): * keywords: review => * owner: thijs => nick Comment: Tested with ParseDump, EchoTest and the test.swf, all look good, please merge with a changelog entry. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 18:11:40 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 17:11:40 -0000 Subject: [pyamf-tickets] #421: Add note about optional adapter/gateway dependencies in the installation instructions In-Reply-To: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> References: <033.75dc02c04f9f170b95d7d3090b354562@pyamf.org> Message-ID: <042.2ff9a638546cbf3156b4c4acfd94acb2@pyamf.org> #421: Add note about optional adapter/gateway dependencies in the installation instructions ----------------------------+----------------------------------------------- Reporter: thijs | Owner: thijs Type: enhancement | Status: closed Priority: major | Milestone: 0.4 Component: Documentation | Version: 0.4 Resolution: fixed | Keywords: ----------------------------+----------------------------------------------- Changes (by thijs): * status: assigned => closed * resolution: => fixed Comment: Applied in r2095. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 18:14:07 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 17:14:07 -0000 Subject: [pyamf-tickets] #448: test_infinites failing for Python 2.5 on win32 In-Reply-To: <033.16d8657be2ad2194fa3d68da8884078d@pyamf.org> References: <033.16d8657be2ad2194fa3d68da8884078d@pyamf.org> Message-ID: <042.f51175cf5b66ee7aad04790644d754ae@pyamf.org> #448: test_infinites failing for Python 2.5 on win32 ----------------------+----------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: closed Priority: blocker | Milestone: 0.4 Component: Testing | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Merged in r2096. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 18:22:30 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 17:22:30 -0000 Subject: [pyamf-tickets] #435: Return XML instead of XMLDocument In-Reply-To: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> References: <033.c05968922f43003aabd53bffe7b28376@pyamf.org> Message-ID: <042.38639eda7e5186020daf48d38fda93ad@pyamf.org> #435: Return XML instead of XMLDocument -----------------------+---------------------------------------------------- Reporter: thijs | Owner: nick Type: defect | Status: closed Priority: major | Milestone: 0.4 Component: Remoting | Version: 0.4 Resolution: fixed | Keywords: -----------------------+---------------------------------------------------- Changes (by nick): * status: assigned => closed * resolution: => fixed Comment: Merged in r2097. -- PyAMF - Ticket URL: From tickets at pyamf.org Sun Jan 18 19:41:01 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sun, 18 Jan 2009 18:41:01 -0000 Subject: [pyamf-tickets] #417: Release 0.4 final In-Reply-To: <033.a073f642c43fd4a9856ebdd72d5e1b46@pyamf.org> References: <033.a073f642c43fd4a9856ebdd72d5e1b46@pyamf.org> Message-ID: <042.56177b80de52ccf4beba53ae106485e1@pyamf.org> #417: Release 0.4 final ----------------------+----------------------------------------------------- Reporter: thijs | Owner: thijs Type: task | Status: closed Priority: blocker | Milestone: 0.4 Component: Website | Version: 0.4 Resolution: fixed | Keywords: ----------------------+----------------------------------------------------- Changes (by thijs): * status: new => closed * resolution: => fixed Comment: Updated wiki pages, added tarballs, uploaded to pypi. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 19 07:09:52 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 19 Jan 2009 06:09:52 -0000 Subject: [pyamf-tickets] #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer Message-ID: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer -------------------------+-------------------------------------------------- Reporter: sparkle | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- using PyAMF 0.4 released at January 18th test = pyamf.util.BufferedByteStream('abcdef') print test.read() print len(test) test.consume() print len(test) test.truncate() print len(test) print out this in cpyamf abcdef 6 6 0 but this in pyamf abcdef 6 0 0 which is the right behavior? -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 19 10:05:15 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 19 Jan 2009 09:05:15 -0000 Subject: [pyamf-tickets] #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer In-Reply-To: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> References: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> Message-ID: <044.31a04087cd16cd0b534efa6037209e68@pyamf.org> #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer -------------------------+-------------------------------------------------- Reporter: sparkle | Owner: nick Type: defect | Status: accepted Priority: minor | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by nick): * priority: major => minor * status: new => accepted Comment: The correct behaviour is the pure python version. I will attach a patch which corrects cpyamf. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 19 10:06:52 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 19 Jan 2009 09:06:52 -0000 Subject: [pyamf-tickets] #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer In-Reply-To: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> References: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> Message-ID: <044.8b9e8bdf29a79a038ebad4b56b4b5980@pyamf.org> #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer -------------------------+-------------------------------------------------- Reporter: sparkle | Owner: nick Type: defect | Status: accepted Priority: minor | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Comment(by nick): The patch is rather lengthy but that is mainly due to the regeneration of the C code using cython. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 19 10:15:28 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 19 Jan 2009 09:15:28 -0000 Subject: [pyamf-tickets] #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer In-Reply-To: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> References: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> Message-ID: <044.44e8726d53624d3dd5139d072644bc8b@pyamf.org> #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer -------------------------+-------------------------------------------------- Reporter: sparkle | Owner: nick Type: defect | Status: accepted Priority: minor | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Comment(by nick): Branching to source:pyamf/branches/cpyamf-consume-451 -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 19 10:20:53 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 19 Jan 2009 09:20:53 -0000 Subject: [pyamf-tickets] #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer In-Reply-To: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> References: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> Message-ID: <044.d76b1f2ae3ffd1a458a2c1355675a640@pyamf.org> #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer -------------------------+-------------------------------------------------- Reporter: sparkle | Owner: sparkle Type: defect | Status: assigned Priority: minor | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * keywords: => review * status: accepted => assigned * owner: nick => sparkle Comment: The attached patch has been applied to the branch and the buildbots all report okay. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 19 11:40:08 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 19 Jan 2009 10:40:08 -0000 Subject: [pyamf-tickets] #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer In-Reply-To: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> References: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> Message-ID: <044.bb75c3177f8f6f2a6bb487688ac50a85@pyamf.org> #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer -------------------------+-------------------------------------------------- Reporter: sparkle | Owner: sparkle Type: defect | Status: assigned Priority: minor | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: review | -------------------------+-------------------------------------------------- Old description: > using PyAMF 0.4 released at January 18th > > test = pyamf.util.BufferedByteStream('abcdef') > print test.read() > print len(test) > test.consume() > print len(test) > test.truncate() > print len(test) > > print out this in cpyamf > abcdef > 6 > 6 > 0 > > but this in pyamf > abcdef > 6 > 0 > 0 > > which is the right behavior? New description: using PyAMF 0.4 released at January 18th {{{ #!python test = pyamf.util.BufferedByteStream('abcdef') print test.read() print len(test) test.consume() print len(test) test.truncate() print len(test) }}} print out this in cpyamf: {{{ abcdef 6 6 0 }}} but this in pyamf: {{{ abcdef 6 0 0 }}} which is the right behavior? -- Comment(by thijs): Fixing markup. -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 19 11:43:29 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 19 Jan 2009 10:43:29 -0000 Subject: [pyamf-tickets] #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer In-Reply-To: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> References: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> Message-ID: <044.f125aabdbbf7b94b993d4f720efc2c89@pyamf.org> #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer -------------------------+-------------------------------------------------- Reporter: sparkle | Owner: sparkle Type: defect | Status: assigned Priority: minor | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: review | -------------------------+-------------------------------------------------- Comment(by thijs): Haven't tested it yet and will continue the review later on but there's a typo in the comment of the test: {{{ #!python # move the strem pos to the end }}} -- PyAMF - Ticket URL: From tickets at pyamf.org Mon Jan 19 16:39:15 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Mon, 19 Jan 2009 15:39:15 -0000 Subject: [pyamf-tickets] #438: Setup PyAMF rsync backup In-Reply-To: <033.4bccdfb705c5fd749ecc83f062fdf762@pyamf.org> References: <033.4bccdfb705c5fd749ecc83f062fdf762@pyamf.org> Message-ID: <042.21b65a28e872942ad881f472d18336c7@pyamf.org> #438: Setup PyAMF rsync backup ----------------------+----------------------------------------------------- Reporter: thijs | Owner: feisley Type: task | Status: assigned Priority: critical | Milestone: 0.5 Component: Website | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by thijs): * owner: thijs => feisley Comment: What kind of permissions? -- PyAMF - Ticket URL: From tickets at pyamf.org Tue Jan 20 12:49:47 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Tue, 20 Jan 2009 11:49:47 -0000 Subject: [pyamf-tickets] #434: need twisted client API using defer In-Reply-To: <035.985b1d3065feb21a2b37015ef0e62ae8@pyamf.org> References: <035.985b1d3065feb21a2b37015ef0e62ae8@pyamf.org> Message-ID: <044.b3806abfcb0112176c549dacce3ed964@pyamf.org> #434: need twisted client API using defer -------------------------+-------------------------------------------------- Reporter: cassidy | Owner: nick Type: enhancement | Status: accepted Priority: major | Milestone: 0.5 Component: Client | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Changes (by nick): * status: new => accepted Comment: Branching to source:pyamf/branches/twisted-client-434 -- PyAMF - Ticket URL: From tickets at pyamf.org Wed Jan 21 20:31:23 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Wed, 21 Jan 2009 19:31:23 -0000 Subject: [pyamf-tickets] #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer In-Reply-To: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> References: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> Message-ID: <044.6e99799e8b39ba1f104a078cc5786f63@pyamf.org> #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer -------------------------+-------------------------------------------------- Reporter: sparkle | Owner: thijs Type: defect | Status: assigned Priority: minor | Milestone: 0.5 Component: C-Extension | Version: 0.4 Keywords: review | -------------------------+-------------------------------------------------- Changes (by nick): * owner: sparkle => thijs -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 22 18:13:00 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 22 Jan 2009 17:13:00 -0000 Subject: [pyamf-tickets] #452: Add more info to the README file Message-ID: <033.888e3e44b43d983069632b9b76a54e3a@pyamf.org> #452: Add more info to the README file ---------------------------+------------------------------------------------ Reporter: thijs | Owner: thijs Type: defect | Status: new Priority: minor | Milestone: 0.5 Component: Documentation | Version: 0.4 Keywords: | ---------------------------+------------------------------------------------ The [source:pyamf/trunk/README.txt] file currently mirrors the WikiStart page's content, but is missing the statements about the supported frameworks and cpyamf. -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 23 21:52:14 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 23 Jan 2009 20:52:14 -0000 Subject: [pyamf-tickets] #234: Expose the AMF request envelope In-Reply-To: <032.c69de8c132bf6695025a02b2f9d3dbc2@pyamf.org> References: <032.c69de8c132bf6695025a02b2f9d3dbc2@pyamf.org> Message-ID: <041.e4c565a78c6fefd4985e0981582fee85@pyamf.org> #234: Expose the AMF request envelope -------------------------+-------------------------------------------------- Reporter: nick | Owner: Type: enhancement | Status: assigned Priority: major | Milestone: 0.5 Component: Remoting | Version: 0.3 Keywords: hack | -------------------------+-------------------------------------------------- Comment(by thijs): See http://lists.pyamf.org/archives/users/2009-January/000883.html -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 29 23:32:57 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 29 Jan 2009 22:32:57 -0000 Subject: [pyamf-tickets] #453: am0.Encoder has a use_amf3 option that isn't used well Message-ID: <032.521b92f157bee9cd98bc05f38734f4a8@pyamf.org> #453: am0.Encoder has a use_amf3 option that isn't used well -------------------------+-------------------------------------------------- Reporter: nick | Owner: nick Type: enhancement | Status: new Priority: minor | Milestone: 0.4.1 Component: AMF0 | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Change it. -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 29 23:34:53 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 29 Jan 2009 22:34:53 -0000 Subject: [pyamf-tickets] #454: GAE adapter breaks if trying to encode non saved objects Message-ID: <032.968f5d1388c063b6e526f9d7766cffd4@pyamf.org> #454: GAE adapter breaks if trying to encode non saved objects ----------------------+----------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: new Priority: critical | Milestone: 0.4.1 Component: Adapter | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- because the `_key` attribute is ignored. -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 29 23:36:41 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 29 Jan 2009 22:36:41 -0000 Subject: [pyamf-tickets] #455: Check unicode __repr__ functions Message-ID: <032.ef23b661198cddb0194cde024560282d@pyamf.org> #455: Check unicode __repr__ functions ----------------------+----------------------------------------------------- Reporter: nick | Owner: nick Type: task | Status: new Priority: major | Milestone: 0.4.1 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- As the logger will fall over if this isn't handled carefully. -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 29 23:38:37 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 29 Jan 2009 22:38:37 -0000 Subject: [pyamf-tickets] #456: Remove _*_cache attributes from django objects Message-ID: <032.2306f4914cb69670f4b25abffe9a8217@pyamf.org> #456: Remove _*_cache attributes from django objects ----------------------+----------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.4.1 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Also the foreignkey attributes aren't being followed correctly. -- PyAMF - Ticket URL: From tickets at pyamf.org Thu Jan 29 23:40:38 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Thu, 29 Jan 2009 22:40:38 -0000 Subject: [pyamf-tickets] #457: Check django.db.models.TimeField encoding Message-ID: <032.59c54f0f959e95dad270e7764380f46f@pyamf.org> #457: Check django.db.models.TimeField encoding ----------------------+----------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: new Priority: major | Milestone: 0.4.1 Component: Remoting | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Needs to be encoded as a `datetime.datetime`. -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 30 13:28:38 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 30 Jan 2009 12:28:38 -0000 Subject: [pyamf-tickets] #454: GAE adapter breaks if trying to encode non saved objects In-Reply-To: <032.968f5d1388c063b6e526f9d7766cffd4@pyamf.org> References: <032.968f5d1388c063b6e526f9d7766cffd4@pyamf.org> Message-ID: <041.36a7e5a3e331dc5d378443ca7159f7bc@pyamf.org> #454: GAE adapter breaks if trying to encode non saved objects ----------------------+----------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: accepted Priority: critical | Milestone: 0.4.1 Component: Adapter | Version: 0.4 Keywords: | ----------------------+----------------------------------------------------- Changes (by nick): * status: new => accepted Comment: Branching to source:pyamf/branches/gae-non-saved-454 -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 30 13:57:24 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 30 Jan 2009 12:57:24 -0000 Subject: [pyamf-tickets] #458: generate exception when encoding duplicate keys Message-ID: <034.eb6e97af34aa1d35563ecaf250a42db8@pyamf.org> #458: generate exception when encoding duplicate keys -------------------------+-------------------------------------------------- Reporter: arman0 | Owner: nick Type: enhancement | Status: new Priority: blocker | Milestone: 0.4.1 Component: Encoder | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- {{{ >>> pyamf.decode(pyamf.encode({0:0, '0':1})).next() {u'0': 1} }}} My guess is that the user almost always has a bug when encoding a python dict which will result in duplicate AS object keys. Therefore, it would be help for pyamf to raise an exception in such cases. -arman -- PyAMF - Ticket URL: From tickets at pyamf.org Fri Jan 30 17:34:27 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Fri, 30 Jan 2009 16:34:27 -0000 Subject: [pyamf-tickets] #458: generate exception when encoding duplicate keys In-Reply-To: <034.eb6e97af34aa1d35563ecaf250a42db8@pyamf.org> References: <034.eb6e97af34aa1d35563ecaf250a42db8@pyamf.org> Message-ID: <043.5ff5fe7d91896a8f066d1715914193cf@pyamf.org> #458: generate exception when encoding duplicate keys -------------------------+-------------------------------------------------- Reporter: arman0 | Owner: nick Type: enhancement | Status: new Priority: blocker | Milestone: 0.4.1 Component: Encoder | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Description changed by thijs: Old description: > {{{ > >>> pyamf.decode(pyamf.encode({0:0, '0':1})).next() > {u'0': 1} > }}} > My guess is that the user almost always has a bug when encoding a python > dict which will result in duplicate AS object keys. Therefore, it would > be help for pyamf to raise an exception in such cases. > > -arman New description: {{{ #!python >>> pyamf.decode(pyamf.encode({0:0, '0':1})).next() {u'0': 1} }}} My guess is that the user almost always has a bug when encoding a python dict which will result in duplicate AS object keys. Therefore, it would be help for pyamf to raise an exception in such cases. -arman -- -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 31 14:13:12 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 31 Jan 2009 13:13:12 -0000 Subject: [pyamf-tickets] #434: need twisted client API using defer In-Reply-To: <035.985b1d3065feb21a2b37015ef0e62ae8@pyamf.org> References: <035.985b1d3065feb21a2b37015ef0e62ae8@pyamf.org> Message-ID: <044.22ba69a6a145667d664a64bee8202838@pyamf.org> #434: need twisted client API using defer -------------------------+-------------------------------------------------- Reporter: cassidy | Owner: nick Type: enhancement | Status: accepted Priority: major | Milestone: 0.5 Component: Client | Version: 0.4 Keywords: | -------------------------+-------------------------------------------------- Comment(by cassidy): Thanks. I integrated your twisted client in my application [1] and it seems to work great! [1] https://launchpad.net/elisa-plugin-rtbf -- PyAMF - Ticket URL: From tickets at pyamf.org Sat Jan 31 20:39:16 2009 From: tickets at pyamf.org (tickets at pyamf.org) Date: Sat, 31 Jan 2009 19:39:16 -0000 Subject: [pyamf-tickets] #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer In-Reply-To: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> References: <035.ddb1619db08cbbc059162f7b7e6fe637@pyamf.org> Message-ID: <044.6107264c418c7a930538ccde5a3a51f1@pyamf.org> #451: the new method consume works different between pyamf and cpyamf if the pos is at the end of the buffer -------------------------+-------------------------------------------------- Reporter: sparkle | Owner: thijs Type: defect | Status: assigned Priority: minor | Milestone: 0.4.1 Component: C-Extension | Version: 0.4 Keywords: review | -------------------------+-------------------------------------------------- Changes (by thijs): * milestone: 0.5 => 0.4.1 -- PyAMF - Ticket URL: