Opened 12 years ago
Closed 12 years ago
#63 closed (invalid)
typo: Interface, Network, and ResourceMapping classes are multiply defined
| Reported by: | chaos@bbn.com | Owned by: | somebody |
|---|---|---|---|
| Priority: | minor | Milestone: | 2012-09-04 client release |
| Component: | Clients | Version: | |
| Keywords: | v0.5.0 | Cc: | |
| Dependencies: |
Description (last modified by )
The gmoc.py source code contains two "class Interface" definitions, two "class ResourceMapping" definitions, and two "class Network" definitions. This isn't very harmful, but it's confusing.
Change History (3)
comment:1 follow-up: 2 Changed 12 years ago by
| Description: | modified (diff) |
|---|---|
| Keywords: | v0.5.0 added; v0.4.0 removed |
| Summary: | typo: Interface and ResourceMapping classes are multiply defined → typo: Interface, Network, and ResourceMapping classes are multiply defined |
comment:2 Changed 12 years ago by
Replying to chaos@bbn.com:
This still exists in v0.5.0, and now there are multiple Network definitions as well.
This is on purpose. For some cases in which a class references another, if the referenced class hasn't been defined yet, Python will throw an error (at least on my machine it does. I'm running Python 2.7.3 under Linux Mint). So, I put stubs in.
comment:3 Changed 12 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Thanks for the info, Kevin. Closing as invalid.
Note: See
TracTickets for help on using
tickets.
This still exists in v0.5.0, and now there are multiple Network definitions as well.