WBwbond·Aug 10, 2013Recommendation phrase
I recommend pasting the Sublime Text console output into a new issue at https://github.com/wbond/sublime_package_control/issues.
In New Sublime Package Control Sitesublimehq
package_control
Python2011–2013
sublimehq / package_control
package_control
The Sublime Text package manager
7Distinct people
11Mentions
1Explicit recommenders
4.9KGitHub stars
What to know before exploring
What it is
The Sublime Text package manager
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
I recommend pasting the Sublime Text console output into a new issue at https://github.com/wbond/sublime_package_control/issues.
wbond used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month11 dated mentions
Observed mentions: 2011-08-15 19:03:02 UTC to 2013-08-10 13:20:27 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Aug 2011 | 2011-08-01 00:00:00 UTC | 2011-09-01 00:00:00 UTC | 1 | 0 | 1 |
| Sep 2011 | 2011-09-01 00:00:00 UTC | 2011-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2011 | 2011-10-01 00:00:00 UTC | 2011-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2011 | 2011-11-01 00:00:00 UTC | 2011-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2011 | 2011-12-01 00:00:00 UTC | 2012-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2012 | 2012-01-01 00:00:00 UTC | 2012-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2012 | 2012-02-01 00:00:00 UTC | 2012-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2012 | 2012-03-01 00:00:00 UTC | 2012-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2012 | 2012-04-01 00:00:00 UTC | 2012-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2012 | 2012-05-01 00:00:00 UTC | 2012-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2012 | 2012-06-01 00:00:00 UTC | 2012-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2012 | 2012-07-01 00:00:00 UTC | 2012-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2012 | 2012-08-01 00:00:00 UTC | 2012-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2012 | 2012-09-01 00:00:00 UTC | 2012-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2012 | 2012-10-01 00:00:00 UTC | 2012-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2012 | 2012-11-01 00:00:00 UTC | 2012-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2012 | 2012-12-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2013 | 2013-01-01 00:00:00 UTC | 2013-02-01 00:00:00 UTC | 2 | 0 | 2 |
| Feb 2013 | 2013-02-01 00:00:00 UTC | 2013-03-01 00:00:00 UTC | 1 | 0 | 1 |
| Mar 2013 | 2013-03-01 00:00:00 UTC | 2013-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2013 | 2013-04-01 00:00:00 UTC | 2013-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2013 | 2013-05-01 00:00:00 UTC | 2013-06-01 00:00:00 UTC | 2 | 0 | 2 |
| Jun 2013 | 2013-06-01 00:00:00 UTC | 2013-07-01 00:00:00 UTC | 2 | 0 | 2 |
| Jul 2013 | 2013-07-01 00:00:00 UTC | 2013-08-01 00:00:00 UTC | 1 | 1 | 0 |
| Aug 2013 | 2013-08-01 00:00:00 UTC | 2013-09-01 00:00:00 UTC | 2 | 0 | 2 |
What Hacker News says
11 sourcesNice looks! I'm having troubles finding how to set a package st3 compatible?
Found some info on github, but not much documentation, https://github.com/wbond/sublime_package_control/issues/291
In New Sublime Package Control SiteSublime Text 3 Compatible Packages · wbond/sublime_package_control Wiki
2 points · Open discussionSettings are mostly the same. Here are a list of supported ST3 packages: https://github.com/wbond/sublime_package_control/wiki/Sublim...
For the plugins I use, they all updated fine.
In Sublime Text 3 Public BetaFairly good. I've been using ST3 as my primary editor for the past month or so, and I've mostly had good results. Many plugins have a python3 branch on their github, or just work outright.
Will Bond, the creator of Package Manager maintains a list of compatible packages here: https://github.com/wbond/sublime_package_control/wiki/Sublim...
It's worth checking if any essential ones will work for you before switching.
Personally, my biggest issue is that wbond's Sublime FTP doesn't work, but the overall speed increase is so great that I'm trying to make my workflow work without it.
In Sublime Text 3 Public BetaI check this every couple of weeks, hoping to see SublimeCodeIntel appear as working: https://github.com/wbond/sublime_package_control/wiki/Sublim...
https://github.com/Kronuz/SublimeCodeIntel
In Upgrading to Sublime Text 3In the meantime I found this listing from Wbond of the ST3-compatible packages:
https://github.com/wbond/sublime_package_control/wiki/Sublim...
I found that Bracket Highlighter is actually compatible but the Github URL has to be added as a repo to Package Control.
In Sublime Text 3The big changes in ST3 aren't primarily user facing. Yes, there are some useful new features, but the reason that this is ST3 versus ST2.1 is because of the API changes.
Sublime Text X, which became ST2, started almost 3 years ago. Back then the API used Python 2.6, I imagine largely because that was the stable 2.x branch. 3.x was still bleeding edge, and not built into OS X.
Over time as more developers learned about Sublime Text, the plugin community exploded. Now there were some warts from the very beginning. On Windows, Python 2.x can't import from paths that contain non-ASCII characters. To get around this, Jon had to implement some hacks to get it all to work consistently.
As the plugin community has grown so much, we've found lots of edge cases and run into issues with developing against an aging version of Python. At this point, P
Read the rest
ython 2.6 is EOL in 7 months. It strikes me that it is a hard, but important choice to break backwards compatibility to fix a number of core issues in ST, but also to jump to a modern version of Python.
Python 3.3 came out just 5 months ago. Jon has rewritten the python bindings and restructured the way packages are imported to allow for importing across plugins. Luckily it isn't that hard to write Python that runs on 2.6 and 3.3, especially with 3.3 adding back in support for u"" strings.
So yes, it is going to continue to be a little while before the plugin community has finished all of the work porting plugins to ST3. There is a list of what already works at https://github.com/wbond/sublime_package_control/wiki/Sublim.... Also, Package Control is fully functional with ST3 now. The last remaining piece before the PC 2.0 release is taking this opportunity to fix some issues with the channel/repo/package structure of Package Control.
That said, this break is positioning Jon and the community to continue to build great stuff that is really useful. So yeah, it kinda sucks, but I have a strong sense users of ST will be much better off in the near future.
Not yet. I started prepping for the port to Python 3 a bit ago at https://github.com/wbond/sublime_package_control/tree/split_..., but the actual Python 3 changes are still in progress and not pushed (for the sake of not spoiling Jon's surprise).
In Sublime Text 3 BetaI started work prepping for Python 3 a little while ago at https://github.com/wbond/sublime_package_control/tree/split_..., however the actual Python 3 changes are in progress and have yet to be committed.
In Sublime Text 3 BetaDid you restart ST2 after pasting the console command? After restarting there should be commands in the command palette that start with "Package Control." If not, go to "Preferences > Browse Packages…" and then look for a folder called "Package Control." If it is not there, there must have been a bug with the download. If it is, look in the console to see if there is a message about Package Control looking for updates.
It may be easier to use GitHub issues to follow up with this: https://github.com/wbond/sublime_package_control/issues.
In Show HN: Sublime Text 2 Package Manager