3 ms·
Changelogs like "Bugfixes to cffi and ctypes" are pretty useless. Do these bugs affect my code? Is my code going to explode horribly if I don't upgrade? Is my c
by hosay123 13y ago
Changelogs like "Bugfixes to cffi and ctypes" are pretty useless. Do these bugs affect my code? Is my code going to explode horribly if I don't upgrade? Is my code going to explode horribly if I do upgrade? etc.
- fijal 13y agoThey're useless for you. It typically means someone posted a bug on the issue tracker and it got fixed. If you did not try PyPy before, you can't know if it affects you. If you did and there were bugs in cffi/ctypes, this is a time to try, if you did and it worked it should continue working. I know this is useless for you, but be a little understanding, most releases that are genuinely useful contain tons of stuff like "we fixed performance of this corner case" or "we fixed this obscure crash" etc. What else would you suggest to put there? Also, how on earth is what you wrote related to ARM JIT support in the title?
- illumen 13y agoGood point. Most projects do it this way, and I think it's kind of good to have a high level summary like this. However, I've also seen projects that also link to specific related issues -- or even better blog pages, or documentation related to it. Mozilla with firefox does it this way for example. Your concern whether this release may break your code is only a test run away ;) But seriously... this is a valid, and common concern. I'd assume they are not intentionally introducing breaking changes, considering it's still targeting CPython compatibility. Also, there are no explicit breaks mentioned -- but I guess it might be good to communicate this explicitly.
- MostAwesomeDude 13y agoAs we say so often in the Python commmunity, "Try It And See." Do you use cffi and/or ctypes in your code? Have you run your tests against this newer PyPy?