@Mego Originally our program had insanely bad threading, so we decided to migrate to asyncio for performance benefits in concurrency. I was assigned that issue and started from scratch to do it; trying to get everything PEP compatible and as efficient as possible
@Mego IMO lookup-2 is better because it's almost totally PEP compatible. My problem with lookup-1 (speaking strictly of the style) is the 1-class-per-file structure and the camelCase
@Mego I'm having an argument with one of my friends/co-developers on a project, and we can't agree on which codebase to use. We each have a repo that branched off in the last 40 or so commits. We need an outside opinion on which one is cleaner/better
@JonathanAllan I can't read your mind.. Can you at least try to work with me? I've asked several times for you input as to what could make it for clear for you.
@JonathanAllan No I still do not; most of the participants, I think, would understand what I'm saying, but does "A program must consist of some explicit data or code." clear it up for you?
@JonathanAllan: What makes the other challenges I linked different from mine in their description? Both have a good amount of upvotes, and neither specify what you've quoted. Not only those two, but many more, as well. I have no problem adding more information if it's unclear, but from what you've brought up, I can't understand what's unclear.