Home Download Buy Blog Forum Support

Process for Porting Plugins

Re: Process for Porting Plugins

Postby Clams on Fri Feb 01, 2013 3:04 pm

For relative import you need to add a . before the name of the module
Clams
 
Posts: 47
Joined: Fri Dec 30, 2011 7:44 am

Re: Process for Porting Plugins

Postby LONGMAN on Fri Feb 01, 2013 6:46 pm

Clams wrote:For relative import you need to add a . before the name of the module

import ./blablabla ?
AutoBackups: ST2 / ST3
CodeFormatter: ST2 / ST3
StringUtilities: ST2 / ST3
LONGMAN
 
Posts: 68
Joined: Mon Nov 26, 2012 5:03 pm
Location: Tbilisi, Georgia

Re: Process for Porting Plugins

Postby ggreer on Sat Feb 02, 2013 3:31 am

wbond wrote:I followed up with Jon via email asking if we can get ssl on Windows in the next build.


It looks like it's fixed in the current build. <3
ggreer
 
Posts: 3
Joined: Tue Jan 29, 2013 9:03 am
Location: San Francisco

Re: Process for Porting Plugins

Postby phyllisstein on Sat Feb 02, 2013 4:36 am

LONGMAN wrote:
Clams wrote:For relative import you need to add a . before the name of the module

import ./blablabla ?


I think it's
Code: Select all
import .blablabla
or
Code: Select all
from . import blablabla


I know the latter has been working fine with the stuff I've been trying to port.
phyllisstein
 
Posts: 49
Joined: Fri Aug 24, 2012 5:28 am

Previous

Return to Plugin Development

Who is online

Users browsing this forum: No registered users and 9 guests