Messed columns in api.eve.CharacterAffiliation() about eveapi HOT 3 CLOSED

Known issue and is a CCP bug. The columns attribute and the actual row data
must be in proper order as per the design for the API.
Processing columns out of order would incur a performance hit which why it
was done positionally.

On Fri, Jul 25, 2014 at 10:21 PM, brammator [email protected]
wrote:

Looks like eveapi lib take columns by position, not by xml attribute name:

for i in api.eve.CharacterAffiliation(ids='735566805,91989271,233838523,1427330454').characters:... print i...Row(characterName:735566805,characterID:brammator,corporationName:98104433,corporationID:SUB ZERO.,allianceName:1411711376,allianceID:Legion of xXDEATHXx,factionName:0,factionID:)Row(characterName:91989271,characterID:Y U NO,corporationName:98104433,corporationID:SUB ZERO.,allianceName:1411711376,allianceID:Legion of xXDEATHXx,factionName:0,<
/span>factionID:)Row(characterName:233838523,characterID:Karer II,corporationName:1139652088,corporationID:Legion of xXDEATHXx Support,allianceName:1411711376,allianceID:Legion of xXDEATHXx,factionName:0,factionID:)Row(characterName:1427330454,characterID:Taemine,corporationName:98104433,corporationID:SUB ZERO.,allianceName:1411711376,allianceID:Legion of xXDEATHXx,factionName:0,factionID:)

Actual XML:

2014-07-25 20:11:49








2014-07-25 21:11:49```

—
Reply to this email directly or view it on GitHub
#20.

from eveapi.

Fixed by CCP

from eveapi.

YAY! Maybe one day I will be less terrible and just not screw this up to start with. :/

from eveapi.