ST3: Package Control doesn't load anymore #490

Closed
ElectronicWar opened this Issue Jun 25, 2013 · 7 comments

Projects

None yet

4 participants

@ElectronicWar

Running ST3 Dev Build 3045 on Win8 Pro x64.
Package Control stopped working with an error message on start. I already pulled the latest revision from GitHub with no result. A new, clean install of PC isn't working as well.

Here's the console output:

reloading plugin Package Control.Package Control
Traceback (most recent call last):
  File "C:\Users\Manuel\Programs\Sublime Text 3\sublime_plugin.py", line 73, in reload_plugin
    m = importlib.import_module(modulename)
  File "X/importlib/__init__.py", line 88, in import_module
  File "<frozen importlib._bootstrap>", line 1577, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1558, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1525, in _find_and_load_unlocked
  File "C:\Users\Manuel\Programs\Sublime Text 3\sublime_plugin.py", line 663, in load_module
    exec(compile(source, source_path, 'exec'), mod.__dict__)
  File "C:\Users\Manuel\Programs\Sublime Text 3\Data\Packages\Package Control\Package Control.py", line 60, in <module>
    from .package_control import reloader
ImportError: No module named 'Package Control.Package Control.package_control'
plugins loaded

Possible regression in ST3?

@FichteFoll
Contributor

Most likely related to the plugin loading changes from 3045 to fix overriding of installed packages (see http://www.sublimetext.com/forum/viewtopic.php?f=3&t=12564). I'd say this is an ST regression and will investigate this further.

Edit: FYI, I can't reproduce this, it works fine on my Win7x64 with ST 3045.

Edit2: Try this in the ST console:

>>> __import__("Package Control").package_control
<module 'Package Control.package_control' from 'C:\\Program Files\\Sublime Text 3 Portable Beta\\Data\\Packages\\Package Control\\package_control\\__init__.py'>
@sorahn
sorahn commented Jun 25, 2013

Same thing over here.

Here's the log from startup.

https://gist.github.com/drbrts/1bb89ec8f3cabf14ddba

@FichteFoll I tried running your command.

__import__("Package Control").package_control <module 'Package Control.package_control' from '/Users/drbrts/Library/Application Support/Sublime Text 3/Packages/Package Control/package_control/__init__.py'>

And I get a python syntax error.

>>> __import__("Package Control").package_control<module 'Package Control.package_control' from '/Users/drbrts/Library/Application Support/Sublime Text 3/Packages/Package Control/package_control/__init__.py'>
  File "<string>", line 1
    __import__("Package Control").package_control<module 'Package Control.package_control' from '/Users/drbrts/Library/Application Support/Sublime Text 3/Packages/Package Control/package_control/__init__.py'>
                                                                                         ^
SyntaxError: invalid syntax
@FichteFoll
Contributor

Ah okay, you were sopossed to run only that after the >>> (which is the Python prompt because I copied it from the output). The second line is what it should output.

__import__("Package Control").package_control
@jinschoi

Same issue here, 3045 on OS X.

@FichteFoll, running your command gives:

import("Package Control").package_control
Traceback (most recent call last):
File "", line 1, in
AttributeError: 'module' object has no attribute 'package_control'

@ElectronicWar

ST3 Dev Build 3046 seems to fix the issue, I will try to confirm tonight at my home installation as well.

Release Date: 26 June 2013
API: Supporting a distinction between Python modules and packages, to ensure relative imports work as expected
@sorahn
sorahn commented Jun 26, 2013

@ElectronicWar @FichteFoll Confirmed fixed over here.

@FichteFoll I haven't been back to my work laptop that I was having the problem on yesterday, but I just updated my home laptop to the same setup (ST3 3046) and it works just fine.

Thanks guys!

@ElectronicWar

Fix confirmed on my home install as well (ST3 Dev 3046 non-portable, Win8 Pro x64).
I am gonna close the issue now. Thanks for your contributions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment