I'm experiencing this issue as well. For debugging purposes, I moved the
previous .cycle directory out of the way, created a new user, saved, and
on restart it asked me to create a new user again —despite having
created the new profile. So the bug is present even for data file
created in the new version, not only when trying to read old data.
On Mon, Sep 23, 2019 at 10:18:51AM +0200, Andreas Tille wrote:
> On Sun, Sep 22, 2019 at 11:11:47PM +0200, Ana Guerrero Lopez wrote:
> > Your current python3 porting is not helping here since many people will start
> > the application, will be prompted for a new user, will create it and erase
> > all their data. So please, revert your changes and if that means the package
> > will be removed from the archive, let it be. At least people will be able to
> > continue using it while they move to something else (or not), but won't lose
> > their data as it'll happen now.
> I've now pushed a change to salsa where I deactivated the whole 2to3
> port and replaced the warning about the port by some other warning that
> a port will be needed or the package will vanish. Hopefully this might
> attract some coders. BTW, I fully agree with you that the code quality
> might not be a good start.
> I tried to start the build here but I get:
> $ cycle
> Traceback (most recent call last):
> File "/usr/bin/cycle", line 213, in <module>
> app = MyApp(0)
> File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk3/wx/_core.py", line 8628, in __init__
> File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk3/wx/_core.py", line 8196, in _BootstrapApp
> return _core_.PyApp__BootstrapApp(*args, **kwargs)
> File "/usr/bin/cycle", line 193, in OnInit
> File "/usr/share/cycle/dialogs.py", line 304, in first_login
> users = get_users()
> File "/usr/share/cycle/dialogs.py", line 192, in get_users
> users.append((cPickle.loads(tmp[:n]), f))
> ValueError: unsupported pickle protocol: 3
> So I reverted to the Python2 version 0.3.1-14 (from testing) but I get
> absolutely the same error. I wonder whether my package is fine in terms
> of "works as broken as before" or whether I messed up something else.
> > Thanks for caring.
> Thanks to you. I'd be happy if you could check master and confirm
> that it is OK. I can even give you commit permissions so you can change
> anything you feel sensible and do the team upload yourself.
Please, add me to the group, I'll take care of the testing and upload.
On Mon, Sep 30, 2019 at 11:47:14PM +0200, Ana Guerrero Lopez wrote:
> > Thanks to you. I'd be happy if you could check master and confirm
> > that it is OK. I can even give you commit permissions so you can change
> > anything you feel sensible and do the team upload yourself.
> Please, add me to the group, I'll take care of the testing and upload.