Picard 3 alpha ready for testing

Downloaded standalone Windows version to a Win10 PC. MusicBrainz-Picard-3.0.0a2.exe
Ran okay as is. Started without issues.

I then deleted the folders created to make it “fresh” again.

Copied my current picard.ini file over and used:
picard -c "path\to\picard.ini"

Got crash :collision: :

Traceback (most recent call last):
  File "picard\config.py", line 477, in run_upgrade_hooks
  File "picard\config_upgrade.py", line 621, in upgrade_to_v3_0_0dev10
AttributeError: 'ImageFormat' object has no attribute 'lower'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "tagger.py", line 12, in <module>
  File "picard\tagger.py", line 1771, in main
  File "picard\tagger.py", line 255, in __init__
  File "picard\config_upgrade.py", line 717, in upgrade_config
  File "picard\config.py", line 479, in run_upgrade_hooks
picard.config.ConfigUpgradeError: Error during config upgrade from version 3.0.0.dev9 to 3.0.0.dev10 using upgrade_to_v3_0_0dev10()

Should I be stripping things out of my picard.ini? Do you want a copy buzzed to you via MB email? (I won’t post it here as it has auth tokens and other stuff in it) (Have emailed it to you @outsidecontext and it looks like it should survive the mail system as text unmangled as I see the same my end as I sent)

My picard.ini is old and messy and just been around for years through updates. But looking at that error I assume “ImageFormat” is a new setting?

As a test I then made a blank picard.ini and ran stand alone again. This time no crash and a selection of new settings added to the ini file.

But here is odd observation… the version numbers written at the top of picard.ini don’t make sense:

Successful run starting from an empty picard.ini file produces this:

[application]
version=3.0.0.alpha2

But when I ran with my original picard.ini, the crash had changed my original from:

[application]
version=2.13.3.final0

to:

[application]
version=3.0.0.dev9
1 Like