As for inability to import EFT-style exports with old names - more proper resolution is to define new export format (ofc it should be common in both eft and pyfa), which avoids using just module names and probably includes more stuff than ship and its modules.

Current Pyfa version shows 2 med slots for Enyo, I suppose data needs a few days to be updated?

Windows: archive (right, no installer this time)
Mac: archive
Source: archive

Current Pyfa version shows 2 med slots for Enyo, I suppose data needs a few days to be updated?

If it still does after ensuring you have latest version (like DarkAegix said), please specify which build you're using (windows/mac/src).

I have one problem. Installed on windows xp 32bit, pyfa twice nuked my system. I right clicked on a fit item to have a look at the attributes, however the right click menu never appeared and system hung hard (had to power cycle/reset).

The one significant problem i have found is that mining yields don't show up. Looking at the forums it would seem that they should when the ship has 0 dps, so my assumption is that something broke. I'm using 1.1.2.

this could perhaps just be my incompetence, but right clicking on resistances is supposed to let you set resistance profiles, right? It works like this for a friend of mine on an earlier version of Pyfa but not for me apparently.

It was feature of old pyfa, based on gtk interface - and it didn't made its way into current version

Ah... well, i would love it if that found it's way back in!

hey so if i update to crucible 1.1, does it mean i have to remake all my fits again?

I already mentioned i thread, that such kind of problems (when purely userspace program kills your OS) is major sign that something is terribad with your OS. I don't think that pyfa causes it, but it may (indirectly) use some OS' functionality which is broken.

It works for me on current version. Could you try temporarily move [your user folder]/.pyfa folder somewhere and see if it helps?

When I do that I get an error when starting it up.

Bug:
I can't run pyfa on any windows7 machine I have access to (tried to use it on three different ones). On start i always get an alert that something went wrong and it crashes. Same for release and nightly builds.
I'm not at home now, so I can't check the log-file, but as far as I remember there's some kind of *.log file that can't be opened or createt in user/documents/.pyfa. Tried to create that file myself, but windows doesn't allow me to create a folder named ".pyfa".

If this bug is unknown I will upload the crash-log later.

1. make the item Info window automatically update when I select another item in market browser or in ship fitting. This will make selecting an item you want according to its parameters much faster.

2. When fitting Strategic Cruisers, make it possible to select another option for each fitted subsystem via right click menu. For example, right clicking on 'fuel catalyst' would bring other 3 subsystems in right click menu and clicking them would re-fit that subsystem instead of fuel catalyst.

3. Make an option to filter items that can't possibly fit into current ship from market window. For example hide cruiser/BS modules when fitting a frigate, other races subsystems when fitting a SC, different sizes of rigs than current ship's size, etc. Maybe not questionable modules (that don't fit normally but could with fitting mods/rigs/implants) but the obvious stuff...

I'll start by stating that I'm very computer-********, so it's pretty much a guarantee that I'm doing something wrong.

Do I need to download the extra bits at the bottom to make this work? (Python, wxPython, SQLAlchemy, etc.)

So far all I get when I unzip the package and run the executable is an error message informing me to check the error log, which contains a bunch of gibberish

I'm sorry to say I've had to go back to using that awful EFT since it's now the only working EVE fitting tool available. That's sad since PYFA had a much less clunky interface than EFT, and was generally easier to use. Please let us know when you decide to quit screwing around with the codebase and go back to simply maintaining a nice tool that was already working just fine; or if you figure out how to produce a working installer or binary distribution. Thanks.