jaydee wrote:Note: You might want to update the site's download links with this, as they still point to 1.05 :)
They do? They're linking to 1.2 for me... perhaps a caching issue?
sublimator wrote:What do you mean exactly?
sublimator wrote:A good practice for when updating sublime ( core or plugins ) is to have everything under version control.
sublimator wrote:Where are you getting these plugins? As a sublime-package from the wiki or from the community repo?
sublimator wrote:(For the moment) I'd recommend getting them as a subversion checkout where you can do things like `svn update and svn log`.
If not version control then why not? And if not then how else to solve the problem? Are you talking having package assets have a UUID like TextMate/e/Intype has? Ability to disable bundles etc?
sublimator wrote:I'm not really following you here Artee. You think it's too hard for a non programmer?
sublimator wrote:__author__ and __version__ I can do if it will make you happy (though version control has that inbuilt ) but I don't particularly like massive docstrings. __author__ and __version__ won't solve any problems in and of themselves though.
sublimator wrote:You want a package index like PyPi?
sublimator wrote:PyPi is built upon a lot of setuptools/distutils infrastructure that simply isn't applicable unfortunately.
sublimator wrote:Who is going to do that job?
Users browsing this forum: Google [Bot] and 12 guests