{"action":"created","issue":{"url":"https://api.github.com/repos/vert-x3/vertx-lang-python/issues/1","labels_url":"https://api.github.com/repos/vert-x3/vertx-lang-python/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/vert-x3/vertx-lang-python/issues/1/comments","events_url":"https://api.github.com/repos/vert-x3/vertx-lang-python/issues/1/events","html_url":"https://github.com/vert-x3/vertx-lang-python/issues/1","id":66262991,"number":1,"title":"Build fails because of various errors","user":{"login":"dano","id":38807,"avatar_url":"https://avatars.githubusercontent.com/u/38807?v=3","gravatar_id":"","url":"https://api.github.com/users/dano","html_url":"https://github.com/dano","followers_url":"https://api.github.com/users/dano/followers","following_url":"https://api.github.com/users/dano/following{/other_user}","gists_url":"https://api.github.com/users/dano/gists{/gist_id}","starred_url":"https://api.github.com/users/dano/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dano/subscriptions","organizations_url":"https://api.github.com/users/dano/orgs","repos_url":"https://api.github.com/users/dano/repos","events_url":"https://api.github.com/users/dano/events{/privacy}","received_events_url":"https://api.github.com/users/dano/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/vert-x3/vertx-lang-python/labels/deferred","name":"deferred","color":"ededed"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":16,"created_at":"2015-04-04T02:03:12Z","updated_at":"2015-07-15T16:06:57Z","closed_at":null,"body":"Attempting a Maven build fails with a very long stack trace, most of which look something like this:\r\n\r\n`Address.java:27: error: Could not generate element for io.vertx.core.net.SocketAddress: [Error: unable to resolve method: io.vertx.codegen.Helper.getGenericType(java.lang.String) [arglength=1]]`\r\n\r\nA few other errors are mixed in, though:\r\n\r\n`[ERROR] diagnostic: /home/dan/code/vert.x/vertx-lang-python/target/vertx-core/io/vertx/core/dns/DnsClient.java:36: error: Could not generate element for io.vertx.core.dns.DnsClient: [Error: unable to resolve method: io.vertx.codegen.Helper.isBasicType(java.lang.String) [arglength=1]]`\r\n\r\n`[ERROR] diagnostic: /home/dan/code/vert.x/vertx-lang-python/target/vertx-core/io/vertx/core/Vertx.java:87: error: Could not generate model for vertx(io.vertx.core.VertxOptions): type io.vertx.core.VertxOptions is not legal for use for a parameter in code generation\r\n  static Vertx vertx(VertxOptions options) {`\r\n\r\n`[ERROR] diagnostic: /home/dan/code/vert.x/vertx-lang-python/target/vertx-core/io/vertx/core/file/FileSystem.java:492: error: Could not generate model for open(java.lang.String,io.vertx.core.file.OpenOptions,io.vertx.core.Handler<io.vertx.core.AsyncResult<io.vertx.core.file.AsyncFile>>): type io.vertx.core.file.OpenOptions is not legal for use for a parameter in code generation`\r\n\r\n`[ERROR] diagnostic: /home/dan/code/vert.x/vertx-lang-python/target/vertx-core/io/vertx/core/eventbus/Message.java:93: error: Could not generate model for reply(java.lang.Object,io.vertx.core.eventbus.DeliveryOptions): type io.vertx.core.eventbus.DeliveryOptions is not legal for use for a parameter in code generation\r\n`\r\n\r\nIt looks like the `getGenericType` and `isBasicType` methods were removed from vertx-codegen back in Decmber, in this commit: https://github.com/vert-x3/vertx-codegen/commit/e8329c4d940b4eebfd8e7671f1d37b2b97c617c7. I'm not sure if some other method should be used intead, or if those methods need to be added back in. The commit message just said it was cleaning up unused methods, so if that was the only reason for removal, adding them back probably makes sense. No idea about the other errors, though.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/vert-x3/vertx-lang-python/issues/comments/121663099","html_url":"https://github.com/vert-x3/vertx-lang-python/issues/1#issuecomment-121663099","issue_url":"https://api.github.com/repos/vert-x3/vertx-lang-python/issues/1","id":121663099,"user":{"login":"dano","id":38807,"avatar_url":"https://avatars.githubusercontent.com/u/38807?v=3","gravatar_id":"","url":"https://api.github.com/users/dano","html_url":"https://github.com/dano","followers_url":"https://api.github.com/users/dano/followers","following_url":"https://api.github.com/users/dano/following{/other_user}","gists_url":"https://api.github.com/users/dano/gists{/gist_id}","starred_url":"https://api.github.com/users/dano/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dano/subscriptions","organizations_url":"https://api.github.com/users/dano/orgs","repos_url":"https://api.github.com/users/dano/repos","events_url":"https://api.github.com/users/dano/events{/privacy}","received_events_url":"https://api.github.com/users/dano/received_events","type":"User","site_admin":false},"created_at":"2015-07-15T16:06:57Z","updated_at":"2015-07-15T16:06:57Z","body":"@ncoghlan I've been following PEP 492 very closely, and it was definitely on my mind when I suggested asyncio integration. I also think I may have been the one who piqued your curiosity about the lack of Python support in Vert.x 3 over in the \"solving multi-core Python\" thread on python-ideas. :)\r\n\r\nre: Jython asyncio integration, I haven't done any kind of in depth investigation, but I'm not sure how feasible it will be to *completely* replace the default `asyncio` event loop with a Vert.x event loop-based implementation, just because Vert.x seems to hide the existence of the event loop from its users as much as possible. Because of that, I'm not sure if we'll have the APIs available on the Vert.x side required to support all the APIs provided by the asyncio loop. At the very least, some kind of partial support should be possible. I also don't see any reason trollius can't be supported, though I haven't tested it with what I've hacked together so far.\r\n\r\nIn any case, the Py4J implementation can get away with running the default asyncio event loop along side the Vert.x loop, since they're running in separate processes, so that will work as a starting point."}}