- User Since
- Jan 17 2017, 12:46 PM (333 w, 1 d)
Aug 1 2018
@kyrios123 I think it's spyder version 4 that will drop python2 and possibly require a newer pylint. Also, remember that this is a stand-alone package, and those users are not going to be happy if they are stuck on LTS for 18 months. It doesn't matter either way, it's done now. It's up to the triage team if they wish to accept it.
@kyrios123 Nobody said it, but I'm assuming that either spyder or some other package will require it in the next 18 months, or, more likely, people will request the new features. The same treatment will be required for many Python packages in the short-term. It doesn't do any harm, anyway, this package can be deleted when we drop Python 2.
@kyrios123 It's not a WIP, I've been testing this locally for a while, just rebuilding and submitting atm. As for pylint 2, you are correct that no packages need it right now. However the work to separate the packages will be mandatory at some point, and it's nice for people who use pylint as a stand-alone package to have the latest features, so might as well do it now.
Reference new python3-astroid package.
@sunnyflunk I'm just putting all the work in place for when the discussion has been had. Will let you know when I'm done in this area and I can explain what I'm proposing.
Hey @debug, I'm moving the python3 support for this package to a new package, as per other packages. I figured I would just update this existing diff rather than creating a new one. Hope that's ok with you!
Update to 1.6.5 instead
May 27 2018
Thanks for the consultation @JoshStrobl and apologies for the slow response and lack of activity over the past few weeks. Very busy at work, got back-to-back major releases going out. I'll be back to packaging soon!
Mar 16 2018
@rjurga No problem, good luck with your thesis, I can take this over tonight after work if no one has any objections.
Mar 15 2018
@DataDrake Can you land this (and D2447) before the sync please? Thanks!
Mar 13 2018
Mar 12 2018
Mar 11 2018
@DataDrake I've now tested against pitivi and networkx. Both appear to be working fine.
Mar 6 2018
Mar 5 2018
Mar 2 2018
@JoshStrobl I've just done some quick runtime tests with subliminal and pulseaudio-dlna. Seems to be working fine, subliminal is a couple of versions out of date (from 2016) so I may submit a patch for that, not sure how many people use it though.
Mar 1 2018
Feb 22 2018
Feb 21 2018
@joebonrichie They don't actually specify any rundeps (apart from when running on PyPy) either in the setup.py or documentation. Tornado is listed under the test requirements though. I think this may be to do with the deprecation of the bundled tornado implementation, they might have just forgotten to update the setup file to say that full tornado is now required. Anyway, I've added it now, so this should be good to go.
Add tornado rundep
Closing due to D2335 also adding unit tests.
I already had a diff open for this (D2234) but I'll close it as you've gone to the effort of adding unit tests as well.
Feb 19 2018
Update to 4.8.2
Feb 17 2018
Version 1.5.0 is now available.
Feb 13 2018
Feb 12 2018
Fix version number
Update to 4.3.4
Feb 10 2018
No problem @JoshStrobl, done now.
Include python3 kernel in $pkgfiles.
Feb 9 2018
Feb 8 2018
Update to 4.3.3
Feb 4 2018
Just noticed this switched to the Python-2.0 license in version 3.1.1.
Same as D2182, the rundeps are not required a builddeps.
Hi @rjurga, I'm the original packager of the existing jupyter stuff, I'm glad to see that people are using them! Thanks for taking this on, and for reporting the other problems with the current packages, I'll see what I can do to resolve those. Anyway, I have a couple of comments regarding this diff:
Feb 3 2018
Feb 1 2018
Will do @sunnyflunk, I'll let you know here if I spot anything. Thanks for all the work to do the upgrade, bet you can't wait to do it all again for 3.7! How much did you manage to script?
Jan 30 2018
Fix typo in the description that I meant to fix in previous releases, but kept forgetting!
Jan 27 2018
Jan 24 2018
Jan 18 2018
Jan 17 2018
Jan 15 2018
Jan 9 2018
Jan 7 2018
Jan 6 2018
@JoshStrobl I was wondering why I'd left them out of the initial package, guess I'd thought of this then subsequently forgotten haha. Thanks for working through my backlog today!