pydev-code — For registered developers

Re: [Pydev-code] Extend rename-refactoring to properly cover all 'uses' of a method

[Fabio Z. <fa...@gm...>]

On Tue, Mar 24, 2015 at 4:13 PM, Andreas Pakulat <an...@fr...>
wrote:

> On 2015-03-24 18:48, Fabio Zadrozny wrote:
>
>> Hi Andreas,
>>
>> You're right in both cases:
>>
>> 1. Duplicate module names under the same project are not supported -- I
>> do have plans to improve on that to support namespace-based packages
>> (I actually dislike those and find them a hack in Python, but PyDev
>> should probably support that -- the issue here is that the indexing should
>> be per source folder and not only per-project), but there's no hard date
>> on that.
>>
>
> I assume thats a more extensive change that a 'newcomer' like me is
> unlikely to be able to resolve?
>
>  2. Folders which don't have __init__.py files are really invisible to
>> PyDev and that's what Python expects -- that'd usually be an error in
>> the project structure, so, PyDev itself should probably not support it...
>> although I'm Ok if you want to add that through some extension.
>>
>
> I see, in our case the subfolders are actually testcase directories and
> each testcase has a 'driving' test.py with a main function that is being
> executed. Most users have the test.py filled with shared function calls and
> hence renaming one of them in only one of the tests is a small disaster :)
>
> If 1. would be solved I could adapt the setup so that each testcase folder
> is setup up separately as a source folder which should make an extension
> unneeded if I understand things correctly. That would also likely better
> reflect the runtime python path.
>
> Since the lookup is done per-project already that should also cover the
> shared folder within each project that we have (to share between testcases
> but not 'globally').
>
> If you have any suggestions on where an extension for 2. would be best be
> inserted I'd be happy to hear them. Otherwise do you see any general
> problem with adjusting ModuleKey to consider name + file for
> compareTo/equal/hashCode - other than potential speed issues? We could
> carry as a custom patch for the time being.
>
>
​I think changing ModuleKey may end up breaking other things (and the speed
issues are likely to happen too on big projects), so, I'd recommend
​against it (and I can't really think of a better solution that's not the
proper fix -- which would be fixing item 1)...

As for item 1, I think the effort to make it work properly will be
substantial and will really require many changes, (which is why I haven't
tackled that so far...), so, I think it may be really harder to resolve on
your side...

Best Regards,

Fabio

Re: [Pydev-code] Extend rename-refactoring to properly cover all 'uses' of a method

[Andreas P. <an...@fr...>]

On 2015-03-24 18:48, Fabio Zadrozny wrote:
> Hi Andreas,
> 
> You're right in both cases:
> 
> 1. Duplicate module names under the same project are not supported -- I do 
> have plans to improve on that to support namespace-based packages
> (I actually dislike those and find them a hack in Python, but PyDev should 
> probably support that -- the issue here is that the indexing should
> be per source folder and not only per-project), but there's no hard date on 
> that.

I assume thats a more extensive change that a 'newcomer' like me is unlikely 
to be able to resolve?

> 2. Folders which don't have __init__.py files are really invisible to PyDev 
> and that's what Python expects -- that'd usually be an error in
> the project structure, so, PyDev itself should probably not support it... 
> although I'm Ok if you want to add that through some extension.

I see, in our case the subfolders are actually testcase directories and each 
testcase has a 'driving' test.py with a main function that is being executed. 
Most users have the test.py filled with shared function calls and hence 
renaming one of them in only one of the tests is a small disaster :)

If 1. would be solved I could adapt the setup so that each testcase folder is 
setup up separately as a source folder which should make an extension 
unneeded if I understand things correctly. That would also likely better 
reflect the runtime python path.

Since the lookup is done per-project already that should also cover the 
shared folder within each project that we have (to share between testcases 
but not 'globally').

If you have any suggestions on where an extension for 2. would be best be 
inserted I'd be happy to hear them. Otherwise do you see any general problem 
with adjusting ModuleKey to consider name + file for compareTo/equal/hashCode 
- other than potential speed issues? We could carry as a custom patch for the 
time being.

Andreas

-- 
Andreas Pakulat sq...@fr...
froglogic GmbH - Automated UI and Web Testing

Re: [Pydev-code] Extend rename-refactoring to properly cover all 'uses' of a method

[Fabio Z. <fa...@gm...>]

Hi Andreas,

You're right in both cases:

1. Duplicate module names under the same project are not supported -- I do
have plans to improve on that to support namespace-based packages (I
actually dislike those and find them a hack in Python, but PyDev should
probably support that -- the issue here is that the indexing should be per
source folder and not only per-project), but there's no hard date on that.

2. Folders which don't have __init__.py files are really invisible to PyDev
and that's what Python expects -- that'd usually be an error in the project
structure, so, PyDev itself should probably not support it... although I'm
Ok if you want to add that through some extension.

Best Regards,

Fabio


On Tue, Mar 24, 2015 at 2:02 PM, Andreas Pakulat <an...@fr...>
wrote:

> Hi Fabio,
>
> thanks for the hint. I think the issue is that in my example both source
> folders use the same module name, that is my project referencing the shared
> module looks like this:
>
> user (not a source folder)
>  - test1 (source folder)
>  |   - test.py
>  |
>  - test2 (source folder)
>      - test.py
>
> And getModulesWithToken builds a treemap based on the module names. For
> both files in my example the module name is 'test' and hence the second one
> is ignored when considering which modules contain the function that is
> about to be renamed.
>
> A quick try changing ModulesKey.compareTo to consider the path if the name
> is the same helps, but it seems the purpose of the class is to compare only
> based on the module name so I'm not sure what a proper fix for that
> situation would look like.
>
> This is with development just updated 2 hours ago.
>
> I've now also tried a scenario thats closer to my real-world usecase, that
> has just 1 source folder in the user project and inside that source folder
> there are two subfolders test1 and test2 each with a test.py. In this case
> the reference in neither of the two test modules is being renamed, I guess
> the fact that the two folders have no __init__.py declaring them packages
> makes PyDev ignore the modules inside?
>
> The layout for this case is like:
>
> user (not a source folder)
>  - base (source folder)
>      - test1 (not a source folder)
>      |   - test.py
>      |
>      - test2 (not a source folder)
>          - test.py
>
> I understand that neither may be a typical setup for PyDev projects but it
> would be great if I could make at least the last one work - possibly by
> allowing some extension mechanism to help determining that case and
> providing the modules that need to be considered.
>
> Andreas
>
>
> On 2015-03-23 17:47, Fabio Zadrozny wrote:
>
>> Hi Andreas,
>>
>> I recently changed some things in that area... (so, make sure you have
>> the latest development branch before starting to check it there to
>> avoid conflicts) the place which checks the modules we want to look for
>> tokens is:
>>
>> com.python.pydev.analysis.additionalinfo.AbstractAdditionalDependencyIn
>> fo.getModulesWithToken(IProject, String, IProgressMonitor), so, that'd
>> be the first thing to check (if the modules are being found there in that
>> situation).
>>
>> Best Regards,
>>
>> Fabio
>>
>> On Mon, Mar 23, 2015 at 1:32 PM, Andreas Pakulat <an...@fr...>
>> wrote:
>>
>>  Hi,
>>>
>>> I recently found that the renaming of functions with PyDev does not
>>> quite work as one would expect. Given the following setup there are two
>>> issues I see happening with 3.9.2:
>>>
>>> - 2 Projects shared and user
>>> - None of the two projects has its project directory set as a pydev
>>> source folder
>>> - The shared project has a linked folder that is set as a source folder
>>> - the linked folder has a single python module with a single function
>>> - The user project has two subfolders each is set up as a pydev source
>>> folder in that project
>>> - The user project has the shared project in its project references
>>> - Each of the subfolders has a test.py with a function and each imports
>>> and uses the function from the shared project's linked folder
>>>
>>> Now when renaming the shared function inside either of the test.py files
>>> it is being renamed in that file and in the module in the shared
>>> project, but it is not being renamed in the other test.py in the user
>>> project.
>>>
>>> If the renaming is initiated in the shared functions definition module
>>> in the shared project none of the references in the user project are
>>> adapted.
>>>
>>> I'm attaching two zip's one containing the two project the other one
>>> containing the linked folder.
>>>
>>> Since I saw several renaming tickets being in the backlog I wanted to
>>> see if I could find the culprit myself but couldn't. So I'd
>>> appreciate any pointers as to where to look for the part that gathers
>>> all 'places' that need to be adjusted when when renaming a function.
>>>
>>> Andreas
>>>
>>> --
>>> Andreas Pakulat sq...@fr...
>>> froglogic GmbH - Automated UI and Web Testing
>>> ------------------------------------------------------------
>>> ------------------
>>> Dive into the World of Parallel Programming The Go Parallel Website,
>>> sponsored
>>> by Intel and developed in partnership with Slashdot Media, is your hub
>>> for all
>>> things parallel software development, from weekly thought leadership
>>> blogs to
>>> news, videos, case studies, tutorials and more. Take a look and join the
>>> conversation now. http://goparallel.sourceforge.net/ [1]
>>> _______________________________________________
>>> pydev-code mailing list
>>> pyd...@li...
>>> https://lists.sourceforge.net/lists/listinfo/pydev-code [2]
>>>
>>
>>
>>
>> Links:
>> ------
>> [1] http://goparallel.sourceforge.net/
>> [2] https://lists.sourceforge.net/lists/listinfo/pydev-code
>>
>> ------------------------------------------------------------
>> ------------------
>> Dive into the World of Parallel Programming The Go Parallel Website,
>> sponsored
>> by Intel and developed in partnership with Slashdot Media, is your hub
>> for all
>> things parallel software development, from weekly thought leadership
>> blogs to
>> news, videos, case studies, tutorials and more. Take a look and join the
>> conversation now. http://goparallel.sourceforge.net/
>> _______________________________________________
>> pydev-code mailing list
>> pyd...@li...
>> https://lists.sourceforge.net/lists/listinfo/pydev-code
>>
>
> --
> Andreas Pakulat sq...@fr...
> froglogic GmbH - Automated UI and Web Testing
>

Re: [Pydev-code] Extend rename-refactoring to properly cover all 'uses' of a method

[Andreas P. <an...@fr...>]

Hi Fabio,

thanks for the hint. I think the issue is that in my example both source 
folders use the same module name, that is my project referencing the shared 
module looks like this:

user (not a source folder)
  - test1 (source folder)
  |   - test.py
  |
  - test2 (source folder)
      - test.py

And getModulesWithToken builds a treemap based on the module names. For both 
files in my example the module name is 'test' and hence the second one is 
ignored when considering which modules contain the function that is about to 
be renamed.

A quick try changing ModulesKey.compareTo to consider the path if the name is 
the same helps, but it seems the purpose of the class is to compare only 
based on the module name so I'm not sure what a proper fix for that situation 
would look like.

This is with development just updated 2 hours ago.

I've now also tried a scenario thats closer to my real-world usecase, that 
has just 1 source folder in the user project and inside that source folder 
there are two subfolders test1 and test2 each with a test.py. In this case 
the reference in neither of the two test modules is being renamed, I guess 
the fact that the two folders have no __init__.py declaring them packages 
makes PyDev ignore the modules inside?

The layout for this case is like:

user (not a source folder)
  - base (source folder)
      - test1 (not a source folder)
      |   - test.py
      |
      - test2 (not a source folder)
          - test.py

I understand that neither may be a typical setup for PyDev projects but it 
would be great if I could make at least the last one work - possibly by 
allowing some extension mechanism to help determining that case and providing 
the modules that need to be considered.

Andreas

On 2015-03-23 17:47, Fabio Zadrozny wrote:
> Hi Andreas,
> 
> I recently changed some things in that area... (so, make sure you have the 
> latest development branch before starting to check it there to
> avoid conflicts) the place which checks the modules we want to look for 
> tokens is:
> 
> com.python.pydev.analysis.additionalinfo.AbstractAdditionalDependencyInfo.getModulesWithToken(IProject, 
> String, IProgressMonitor), so, that'd
> be the first thing to check (if the modules are being found there in that 
> situation).
> 
> Best Regards,
> 
> Fabio
> 
> On Mon, Mar 23, 2015 at 1:32 PM, Andreas Pakulat <an...@fr...> 
> wrote:
> 
>> Hi,
>> 
>> I recently found that the renaming of functions with PyDev does not quite 
>> work as one would expect. Given the following setup there are two
>> issues I see happening with 3.9.2:
>> 
>> - 2 Projects shared and user
>> - None of the two projects has its project directory set as a pydev source 
>> folder
>> - The shared project has a linked folder that is set as a source folder
>> - the linked folder has a single python module with a single function
>> - The user project has two subfolders each is set up as a pydev source 
>> folder in that project
>> - The user project has the shared project in its project references
>> - Each of the subfolders has a test.py with a function and each imports and 
>> uses the function from the shared project's linked folder
>> 
>> Now when renaming the shared function inside either of the test.py files it 
>> is being renamed in that file and in the module in the shared
>> project, but it is not being renamed in the other test.py in the user 
>> project.
>> 
>> If the renaming is initiated in the shared functions definition module in 
>> the shared project none of the references in the user project are
>> adapted.
>> 
>> I'm attaching two zip's one containing the two project the other one 
>> containing the linked folder.
>> 
>> Since I saw several renaming tickets being in the backlog I wanted to see 
>> if I could find the culprit myself but couldn't. So I'd
>> appreciate any pointers as to where to look for the part that gathers all 
>> 'places' that need to be adjusted when when renaming a function.
>> 
>> Andreas
>> 
>> --
>> Andreas Pakulat sq...@fr...
>> froglogic GmbH - Automated UI and Web Testing
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming The Go Parallel Website, 
>> sponsored
>> by Intel and developed in partnership with Slashdot Media, is your hub for 
>> all
>> things parallel software development, from weekly thought leadership blogs 
>> to
>> news, videos, case studies, tutorials and more. Take a look and join the
>> conversation now. http://goparallel.sourceforge.net/ [1]
>> _______________________________________________
>> pydev-code mailing list
>> pyd...@li...
>> https://lists.sourceforge.net/lists/listinfo/pydev-code [2]
> 
> 
> 
> Links:
> ------
> [1] http://goparallel.sourceforge.net/
> [2] https://lists.sourceforge.net/lists/listinfo/pydev-code
> 
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, 
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for 
> all
> things parallel software development, from weekly thought leadership blogs 
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> pydev-code mailing list
> pyd...@li...
> https://lists.sourceforge.net/lists/listinfo/pydev-code

-- 
Andreas Pakulat sq...@fr...
froglogic GmbH - Automated UI and Web Testing

Re: [Pydev-code] Extend rename-refactoring to properly cover all 'uses' of a method

[Fabio Z. <fa...@gm...>]

Hi Andreas,

I recently changed some things in that area... (so, make sure you have the
latest development branch before starting to check it there to avoid
conflicts) the place which checks the modules we want to look for tokens is:

com.python.pydev.analysis.additionalinfo.AbstractAdditionalDependencyInfo.getModulesWithToken(IProject,
String, IProgressMonitor), so, that'd be the first thing to check (if the
modules are being found there in that situation).

Best Regards,

Fabio

On Mon, Mar 23, 2015 at 1:32 PM, Andreas Pakulat <an...@fr...>
wrote:

> Hi,
>
> I recently found that the renaming of functions with PyDev does not quite
> work as one would expect. Given the following setup there are two issues I
> see happening with 3.9.2:
>
> - 2 Projects shared and user
> - None of the two projects has its project directory set as a pydev source
> folder
> - The shared project has a linked folder that is set as a source folder
> - the linked folder has a single python module with a single function
> - The user project has two subfolders each is set up as a pydev source
> folder in that project
> - The user project has the shared project in its project references
> - Each of the subfolders has a test.py with a function and each imports
> and uses the function from the shared project's linked folder
>
> Now when renaming the shared function inside either of the test.py files
> it is being renamed in that file and in the module in the shared project,
> but it is not being renamed in the other test.py in the user project.
>
> If the renaming is initiated in the shared functions definition module in
> the shared project none of the references in the user project are adapted.
>
> I'm attaching two zip's one containing the two project the other one
> containing the linked folder.
>
> Since I saw several renaming tickets being in the backlog I wanted to see
> if I could find the culprit myself but couldn't. So I'd appreciate any
> pointers as to where to look for the part that gathers all 'places' that
> need to be adjusted when when renaming a function.
>
> Andreas
>
> --
> Andreas Pakulat sq...@fr...
> froglogic GmbH - Automated UI and Web Testing
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> pydev-code mailing list
> pyd...@li...
> https://lists.sourceforge.net/lists/listinfo/pydev-code
>
>

[Pydev-code] Extend rename-refactoring to properly cover all 'uses' of a method

[Andreas P. <an...@fr...>]

Hi,

I recently found that the renaming of functions with PyDev does not quite 
work as one would expect. Given the following setup there are two issues I 
see happening with 3.9.2:

- 2 Projects shared and user
- None of the two projects has its project directory set as a pydev source 
folder
- The shared project has a linked folder that is set as a source folder
- the linked folder has a single python module with a single function
- The user project has two subfolders each is set up as a pydev source folder 
in that project
- The user project has the shared project in its project references
- Each of the subfolders has a test.py with a function and each imports and 
uses the function from the shared project's linked folder

Now when renaming the shared function inside either of the test.py files it 
is being renamed in that file and in the module in the shared project, but it 
is not being renamed in the other test.py in the user project.

If the renaming is initiated in the shared functions definition module in the 
shared project none of the references in the user project are adapted.

I'm attaching two zip's one containing the two project the other one 
containing the linked folder.

Since I saw several renaming tickets being in the backlog I wanted to see if 
I could find the culprit myself but couldn't. So I'd appreciate any pointers 
as to where to look for the part that gathers all 'places' that need to be 
adjusted when when renaming a function.

Andreas

-- 
Andreas Pakulat sq...@fr...
froglogic GmbH - Automated UI and Web Testing

Re: [Pydev-code] Inter-PyDev dependencies too loose?

[Fabio Z. <fa...@gm...>]

Hi Andreas,

I agree the dependencies shouldn't be so loose...

Note that if you create a pull request to fix that you also have to update
the 'Pydev/update_versions.py' script in the repository to properly set
things when upgrading the version.

Best Regards,

Fabio

On Fri, Mar 13, 2015 at 4:59 PM, Andreas Pakulat <an...@fr...>
wrote:

> Hi,
>
> I'm wondering wether there's a reason for the rather loose dependencies
> between different PyDev plugins?
>
> For example org.python.pydev.shared_ui depends on
> org.python.pydev.shared_core but does not specify any version. So if
> someone
> ends up having http://pydev.org/updates in its software sites list and
> then
> installs say version 3.1.0 of org.python.pydev.shared_ui Eclipse will pick
> up
> org.python.pydev.shared_core version 3.9.2 - it seems to pick the latest
> version of plugins whenever there's no explicit restriction. This also
> happens for a few other plugins and trying to use PyDev with this mix of
> versions is going to fail horribly.
>
> Before posting a PR I just wanted to make sure I'm not overlooking
> something.
>
> Andreas
>
> --
> Andreas Pakulat sq...@fr...
> froglogic GmbH - Automated UI and Web Testing
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> pydev-code mailing list
> pyd...@li...
> https://lists.sourceforge.net/lists/listinfo/pydev-code
>

[Pydev-code] Inter-PyDev dependencies too loose?

[Andreas P. <an...@fr...>]

Hi,

I'm wondering wether there's a reason for the rather loose dependencies 
between different PyDev plugins?

For example org.python.pydev.shared_ui depends on 
org.python.pydev.shared_core but does not specify any version. So if someone 
ends up having http://pydev.org/updates in its software sites list and then 
installs say version 3.1.0 of org.python.pydev.shared_ui Eclipse will pick up 
org.python.pydev.shared_core version 3.9.2 - it seems to pick the latest 
version of plugins whenever there's no explicit restriction. This also 
happens for a few other plugins and trying to use PyDev with this mix of 
versions is going to fail horribly.

Before posting a PR I just wanted to make sure I'm not overlooking something.

Andreas

-- 
Andreas Pakulat sq...@fr...
froglogic GmbH - Automated UI and Web Testing

[Pydev-code] PyDev 3.9.2 Released

[Fabio Z. <fa...@gm...>]

What is PyDev?
---------------------------

PyDev is an open-source Python IDE on top of Eclipse for Python, Jython and
IronPython development.

It comes with goodies such as code completion, syntax highlighting, syntax
analysis, code analysis, refactor, debug, interactive console, etc.

Details on PyDev: http://pydev.org
Details on its development: http://pydev.blogspot.com


What is LiClipse?
---------------------------

LiClipse is a PyDev standalone with goodies such as support for Multiple
cursors, theming and a number of other languages such as Django Templates,
Kivy Language, Mako Templates, Html, Javascript, etc.

It's also a commercial counterpart which helps supporting the development
of PyDev.

Details on LiClipse: http://www.liclipse.com/


Release Highlights:
-------------------------------

* **Important**: PyDev requires Eclipse 3.8 or 4.3 onwards and Java 7! For
older versions, keep using PyDev 2.x (use LiClipse: http://www.liclipse.com
for a PyDev standalone with all requirements bundled).

* **PyVmMonitor Integration**

* PyVmMonitor: http://www.pyvmmonitor.com/ is now in public beta, so, the
PyDev integration
(Window > Show View > Other > PyDev > Profile) may be used to  profile your
programs.

* **Debugger**

* The debug view now has an interactive console (with history) attached to
it by default (which may be toggled on/off). (PyDev-507)
* Debugger no longer reopens a file when that file is already opened.
(PyDev-456)
* Handled issue when getting referrers for some object gave an error if it
was found in a dict where the key is not a string.
* When interactive console starts in debug session, a banner is no longer
shown.
* Stepping with #@DontTrace no longer returns through decorator call-site.
(PyDev-526)
* The default for tracing template render exceptions on Django is now false.

* **Interactive Console**

* F2 to send contents from editor to console now considers backslash
continuations. (PyDev-502)
* Interactive Console interrupt now properly interrupts a sleep call (when
possible). (PyDev-500)
* PyDev interactive console now has a user-specified encoding (by default
UTF-8). (PyDev-454)
* Scroll the console on stdout / stderr output. (PyDev-504, patch by James
Blackburn)
* Moved interactive console initial commands to a separate preferences page.
* Handling interrupted system call EINTR in the pydevconsole.py. (PyDev-534)
* Fixed racing condition where the output of the console could appear as a
user input. (PyDev-490, patch by James Blackburn)

* **Refactoring**

* Fixed issue where indentation lost on rename module refactoring.
(PyDev-498)
* The rename modules refactoring wizard now provides a way to do a simple
resource rename (to rename extensions).

* **Others**

* Converting filename from .pyx to .py doesn't loose indexing on the file
anymore. (PyDev-525)
* The Cython parser now properly scopes methods.
* Pasting contents directly in the PyDev package explorer to create a file
uses the proper delimiter.
* Fixed deadlock in ImageCache when rendering debug completions from
console. (PyDev-527)
* Fixed deadlock on racing condition when rendering PyTextHover. (PyDev-523)
* Tab settings were separated from the editor color settings and may now be
persisted in the project/user settings.
* Fixed surround with try..finally/except indentation on Ctrl+1 when some
line has a comment which has a different indentation.


Cheers,

--
Fabio Zadrozny
------------------------------------------------------
Software Developer

LiClipse
http://www.liclipse.com

PyDev - Python Development Environment for Eclipse
http://pydev.org
http://pydev.blogspot.com

PyVmMonitor - Python Profiler
http://www.pyvmmonitor.com/

[Pydev-code] PyDev 3.9.1 Released

[Fabio Z. <fa...@gm...>]

What is PyDev?
---------------------------

PyDev is an open-source Python IDE on top of Eclipse for Python, Jython and
IronPython development.

It comes with goodies such as code completion, syntax highlighting, syntax
analysis, code analysis, refactor, debug, interactive console, etc.

Details on PyDev: http://pydev.org
Details on its development: http://pydev.blogspot.com


What is LiClipse?
---------------------------

LiClipse is a PyDev standalone with goodies such as support for Multiple
cursors, theming and a number of other languages such as Django Templates,
Kivy Language, Mako Templates, Html, Javascript, etc.

It's also a commercial counterpart which helps supporting the development
of PyDev.

Details on LiClipse: http://www.liclipse.com/


Release Highlights:
-------------------------------

* **Important**: PyDev requires Eclipse 3.8 or 4.3 onwards and Java 7! For
older versions, keep using PyDev 2.x (use LiClipse: http://www.liclipse.com
for a PyDev standalone with all requirements bundled).

* **Preferences**

  * PyDev preferences may now be saved and persisted for each project or in
the user settings (not just in the workspace).
  * Currently Save actions, Code Formatter, Typing and Imports are
supported (more to come in upcoming releases).
  * The same pages in the preferences are used to save settings to
(multiple) projects or user settings.
  * Configuration files are saved in Yaml format and are meant to be saved
in version control.

* **Editor**

  * The option to apply auto-formating was changed to apply any save
actions in non-workspace files.
  * Editor icon improved for dark theme (patch by Fathony Luthfillah).
  * When running the pep8 code analysis, the markers shown are no longer 1
character off.

* **Django**

  * Improved Django 1.7 support (patch by David Lehrian).

* **Profiling**

  * Integration with PyVmMonitor: http://pyvmmonitor.github.io/ (currently
only available for backers of the effort).

    * A profiling view was created where the location of PyVmMonitor should
be specified.
    * Just turning the option on will make all runs from that point on run
with the selected profile backend enabled.

* **Debugger**

  * Connecting to subprocesses working in Python 3.4.
  * Attach to running process is now supported on Mac OS.

* **Others**

  * Unset VIRTUAL_ENV before running external Python to protect the
sys.path (patch by James Blackburn).
  * pytest: Expected failure is no longer marked as a failure.
  * pytest: The working dir is changed so that conftests are loaded
properly (to workaround issue in pytest:
https://bitbucket.org/hpk42/pytest/issue/639/conftest-being-loaded-twice-giving
).
  * Fixed issue where an unused import would not be properly removed if it
was not a from import.
  * Fixed exception when drawing minimap overview ruler.


Cheers,

--
Fabio Zadrozny
------------------------------------------------------
Software Developer

LiClipse
http://www.liclipse.com

PyDev - Python Development Environment for Eclipse
http://pydev.org
http://pydev.blogspot.com

PyVmMonitor - Python Profiler
http://pyvmmonitor.github.io/

[Pydev-code] Unable to navigate from python file to java method using "self" in Pydev

[Naman p. <pat...@cs...>]

Hi,

I have a file.py as follows :

*import unittest*
*from  com.bahmanm import Greeter*


*class A(unittest.TestCase, Greeter):*
*    def test_A(self):*
*        self.greet("Bahman")*

*if __name__ == "__main__":  *
*    unittest.main()*

In above case, Greeter is a java file as:

*package  com.bahmanm;*
*public class Greeter {*

* private String msg;*

* public Greeter() {*
*  msg = "Hello, ";*
* }*

* public void greet(String name) {*
*  System.out.println(msg + name);*
* }*
*}*


The code runs successfully, but I am not able to navigate from python code
to java code at line *self.greet("Bahman") *in the file.py code.

I am able to view the contents of Greeter file from line
*from  com.bahmanm import Greeter. * But am not able to check the code flow
at the function call.

I am using jython interpreter. I have also added the Java src path to
PYTHONPATH in Eclipse.

Any suggestion regarding the above navigation will be of great help.
Please find the corresponding attached source files.

[Pydev-code] PyDev 3.9.0 Released

[Fabio Z. <fa...@gm...>]

What is PyDev?
---------------------------

PyDev is an open-source Python IDE on top of Eclipse for Python, Jython and
IronPython development.

It comes with goodies such as code completion, syntax highlighting, syntax
analysis, code analysis, refactor, debug, interactive console, etc.

Details on PyDev: http://pydev.org
Details on its development: http://pydev.blogspot.com


What is LiClipse?
---------------------------

LiClipse is a PyDev standalone with goodies such as support for Multiple
cursors, theming and a number of other languages such as Django Templates,
Kivy Language, Mako Templates, Html, Javascript, etc.

It's also a commercial counterpart which helps supporting the development
of PyDev.

Details on LiClipse: http://www.liclipse.com/


Release Highlights:
-------------------------------

* **Important**: PyDev requires Eclipse 3.8 or 4.3 onwards and Java 7! For
older versions, keep using PyDev 2.x (use LiClipse: http://www.liclipse.com
for a PyDev standalone with all requirements bundled).

* **Vertical Indent Guide** is now available (may be customized in PyDev >
Editor > Vertical Indent Guide. PyDev-359).

* **Minimap**

    * The horizontal scrollbar is shown by default (again). It's still
possible to hide it in the Preferences > PyDev > Editor > Overview Ruler
Minimap.

    * Fixed critical issue where the minimap could lead to a repaint
recursion on some Linux versions (reproduced on Ubuntu 12. LiClipse-120).

* The PYTHONPATH is now properly passed to PyLint when using an external
executable (PyDev-475).

* Fixed issue where breakpoints in other editors (i.e.: CDT) where wrongly
being handled by PyDev (patch by Danny Yoo. PyDev-482).

* Fixed issue doing code-completion for builtins in Jython (PyDev-457).

* **Interactive Console**

    * When doing a code-completion with Ctrl+Space, let tab change the
focus instead of doing the tab-enabled completion.

    * Output given from the backend could end up being editable (PyDev-465).

    * input() was including the prompt in the input string (PyDev-465).

    * Debugger console was outputting greeting message when it shouldn't
(PyDev-464).

* **pep8**: --exclude can now be used in pep8 parameters (patch by
Sebastian Elsner. PyDev-466).

* **autopep8**: end line delimiter is now being kept (patch by Ben Blank.
PyDev-461).

* Unittest integration: Making sure we don't import the unittest module
before executing pytest (PyDev-455).

* Unittest integration: Fix to use the proper encoding when passing
stdout/stderr to the java side.

* Fixed issue when debugging file without extension (when there was no
default editor associated to the file name).

* Debugger: getpass properly working with additional arguments (PyDev-460).


Cheers,

--
Fabio Zadrozny
------------------------------------------------------
Software Developer

LiClipse
http://www.liclipse.com

PyDev - Python Development Environment for Eclipse
http://pydev.org
http://pydev.blogspot.com

[Pydev-code] Is there a way to control how PyDev traverses the PYTHONPATH?

[R. G. <rg...@ao...>]

Hi,

before I ask my question, let me give you some background:

I am working on a project whose source tree grew over many years (decades) and fundamental changes to the structure are more or less ruled out (not by me).
This project also uses Python code and we are starting to use PyDev for development.

The problem that we have is that on our development machines the package structure is different compared to our execution environment.
The difference is that (for reasons that are not entirely clear to me) the packages on the development host contain symbolic links
to other packages.

That means, on the execution environment we only have
lib/pkg1
lib/pkg2
lib/pkg3
...

but on the development machine we have

lib/pkg1
lib/pkg1/pkg42  (is a sym link to lib/pkg42)
lib/pkg1/pkg56 (is a sym link to lib/pkg56)
lib/pkg1/pkg77 (is a sym link to lib/pkg77)
lib/pkg2
...

It seems that PyDev (when analysing the PYTHONPATH) does a depth first search.
So it goes into pkg1, finds pkgs 42, 56 and 77 as sub-packages of pkg1.
Later, when it finds lib/pkg42, it seems to recognize that it already knows that package
(it seems to identify that package via its physical path) and does ignore it.

At least this is what we deduced from looking at the tree that is created in the PyDev package explorer.
Due to this PyDev is utterly (and understandably) confused and we get a lot of false errors/warning (missing import etc).

When we go and delete all symbolic links to other pkgs inside a pkg, PyDev works like a charm.
However, deleting all those symbolic links is a massive change to the source tree and can have unknown side effect
on other parts of our build infrastructure (it is a mixed language project).

Now the question:
Can we somehow tell pydev to NOT search for subpackages on the project specific PYTHONPATH?
Would it be possible to make this configurable in a future PyDev version (like defining a max-depth for
certain directories). The thing is, that the Python interpreter doesn't complain at all. It is "only" PyDev (but
we admit it is not a PyDev bug) getting confused by the weird structure.
Or maybe our analysis is wrong?

best regards
  Robert

Re: [Pydev-code] Has the analyze only open editors setting ever had a meaning?

[Andreas P. <an...@fr...>]

Hi Fabio,

On 2014-09-26 15:44, Fabio Zadrozny wrote:
> On Fri, Sep 26, 2014 at 10:34 AM, Andreas Pakulat <an...@fr...> 
> wrote:
>  util.py has just 1 function definition 'mycoolfun' and main.py is empty. 
> After a fresh start of Eclipse I open main.py and type myc and
> invoke code-completion. There's no entry for mycoolfunc. If I open util.py, 
> close it again and again invoke code-completion inside main.py the
> entry for 'mycoolfunc' shows up.
> 
>  My assumption was that this is caused by the 'analyze-only-open-editors' 
> setting, but changing the setting from its default value did not
> help.
> 
> Humm... that sounds like you have disabled auto-build (project > build 
> automatically)... if that's the case, you have to invoke the build
> manually for pydev to index those files (Ctrl+B)... or maybe something else 
> became wrong and the indexing became lost (if that's the case, a
> manual fix would be going to the project properties > pydev-pythonpath > 
> force restore internal info -- and it should definitely be kept up to
> date afterwards if auto build is turned on).

Automatic project building is enabled, but indeed cleaning the project fixes 
the problem. At least until the next restart of Eclipse. It seems there's no 
rebuild happening immediately after starting Eclipse and hence the 
information for completion is not available.

Andreas

-- 
Andreas Pakulat sq...@fr...
froglogic GmbH - Automated UI and Web Testing

Re: [Pydev-code] Has the analyze only open editors setting ever had a meaning?

[Fabio Z. <fa...@gm...>]

On Fri, Sep 26, 2014 at 10:34 AM, Andreas Pakulat <an...@fr...>
wrote:

> On 2014-09-26 12:57, Fabio Zadrozny wrote:
>
>> On Wed, Sep 24, 2014 at 9:25 AM, Andreas Pakulat <an...@fr...>
>> wrote:
>>
>>  Hi,
>>>
>>> I recently stumbled about the 'Builder' page and its 'Analyze only open
>>> editors' setting. It sounded like disabling this would help one of our
>>> customers who wanted to get completion for functions in modules that are
>>> not
>>> yet imported. Unfortunately it turns out this preference is not being
>>> used
>>> anywhere in the codebase and looking at the existing pydev tags has never
>>> been used.
>>>
>>> I'm wondering wether I'm missing something or wether this has really been
>>> added (to the ui) and then never used (by the builder)?
>>>
>>> On a related note: Is there a way to get pydev to create completions for
>>> functions/classes in files that haven't been opened yet (after starting
>>> eclipse)? (i.e. where do I have to look into the codebase to find the
>>> starting point)
>>>
>>
>> Hi Andreas,
>>
>> Actually, that's still used... if you take a look at the code, the getter
>> which uses the ANALYZE_ONLY_ACTIVE_EDITOR constant is
>> org.python.pydev.builder.PyDevBuilderPrefPage.
>> getAnalyzeOnlyActiveEditor().
>>
>
> Ah, I missed the public static getter and its uses during my grep :)
>
>  As for getting completions for functions/classes that haven't been
>> imported, I think I don't quite follow what you mean (you do have
>> context-insensitive code-completion which would add the import and the
>> token -- but apparently, that's not what you meant), so, can you
>> rephrase that to explain better your use case?
>>
>
> What I see happening is that completion does not include functions from
> modules that haven't been open in an editor. For example lets take this
> project:
>
> myproject
>  |
>  - module1
>  |    |
>  |    - util.py
>  |
>  - module2
>       |
>       - main.py
>
> util.py has just 1 function definition 'mycoolfun' and main.py is empty.
> After a fresh start of Eclipse I open main.py and type myc and invoke
> code-completion. There's no entry for mycoolfunc. If I open util.py, close
> it again and again invoke code-completion inside main.py the entry for
> 'mycoolfunc' shows up.
>
> My assumption was that this is caused by the 'analyze-only-open-editors'
> setting, but changing the setting from its default value did not help.
>
> Andreas
>
> PS: The project's root folder is configured as python path so that
> shouldn't be a problem.
> PPS: Tested this with the master branch as well as seeing it with the 2.8
> release.
>
>
Humm... that sounds like you have disabled auto-build (project > build
automatically)... if that's the case, you have to invoke the build manually
for pydev to index those files (Ctrl+B)... or maybe something else became
wrong and the indexing became lost (if that's the case, a manual fix would
be going to the project properties > pydev-pythonpath > force restore
internal info -- and it should definitely be kept up to date afterwards if
auto build is turned on).

Cheers,

Fabio

Re: [Pydev-code] Has the analyze only open editors setting ever had a meaning?

[Andreas P. <an...@fr...>]

On 2014-09-26 12:57, Fabio Zadrozny wrote:
> On Wed, Sep 24, 2014 at 9:25 AM, Andreas Pakulat <an...@fr...> 
> wrote:
> 
>> Hi,
>> 
>> I recently stumbled about the 'Builder' page and its 'Analyze only open
>> editors' setting. It sounded like disabling this would help one of our
>> customers who wanted to get completion for functions in modules that are 
>> not
>> yet imported. Unfortunately it turns out this preference is not being used
>> anywhere in the codebase and looking at the existing pydev tags has never
>> been used.
>> 
>> I'm wondering wether I'm missing something or wether this has really been
>> added (to the ui) and then never used (by the builder)?
>> 
>> On a related note: Is there a way to get pydev to create completions for
>> functions/classes in files that haven't been opened yet (after starting
>> eclipse)? (i.e. where do I have to look into the codebase to find the
>> starting point)
> 
> Hi Andreas,
> 
> Actually, that's still used... if you take a look at the code, the getter 
> which uses the ANALYZE_ONLY_ACTIVE_EDITOR constant is
> org.python.pydev.builder.PyDevBuilderPrefPage.getAnalyzeOnlyActiveEditor().

Ah, I missed the public static getter and its uses during my grep :)

> As for getting completions for functions/classes that haven't been imported, 
> I think I don't quite follow what you mean (you do have
> context-insensitive code-completion which would add the import and the token 
> -- but apparently, that's not what you meant), so, can you
> rephrase that to explain better your use case?

What I see happening is that completion does not include functions from 
modules that haven't been open in an editor. For example lets take this 
project:

myproject
  |
  - module1
  |    |
  |    - util.py
  |
  - module2
       |
       - main.py

util.py has just 1 function definition 'mycoolfun' and main.py is empty. 
After a fresh start of Eclipse I open main.py and type myc and invoke 
code-completion. There's no entry for mycoolfunc. If I open util.py, close it 
again and again invoke code-completion inside main.py the entry for 
'mycoolfunc' shows up.

My assumption was that this is caused by the 'analyze-only-open-editors' 
setting, but changing the setting from its default value did not help.

Andreas

PS: The project's root folder is configured as python path so that shouldn't 
be a problem.
PPS: Tested this with the master branch as well as seeing it with the 2.8 
release.

-- 
Andreas Pakulat sq...@fr...
froglogic GmbH - Automated UI and Web Testing

Re: [Pydev-code] Has the analyze only open editors setting ever had a meaning?

[Fabio Z. <fa...@gm...>]

On Fri, Sep 26, 2014 at 7:57 AM, Fabio Zadrozny <fa...@gm...> wrote:

>
> On Wed, Sep 24, 2014 at 9:25 AM, Andreas Pakulat <an...@fr...>
> wrote:
>
>> Hi,
>>
>> I recently stumbled about the 'Builder' page and its 'Analyze only open
>> editors' setting. It sounded like disabling this would help one of our
>> customers who wanted to get completion for functions in modules that are
>> not
>> yet imported. Unfortunately it turns out this preference is not being used
>> anywhere in the codebase and looking at the existing pydev tags has never
>> been used.
>>
>> I'm wondering wether I'm missing something or wether this has really been
>> added (to the ui) and then never used (by the builder)?
>>
>> On a related note: Is there a way to get pydev to create completions for
>> functions/classes in files that haven't been opened yet (after starting
>> eclipse)? (i.e. where do I have to look into the codebase to find the
>> starting point)
>>
>> Hi Andreas,
>
> Actually, that's still used... if you take a look at the code, the getter
> which uses the ANALYZE_ONLY_ACTIVE_EDITOR constant is
> org.python.pydev.builder.PyDevBuilderPrefPage.getAnalyzeOnlyActiveEditor().
>
> What it does is that if it's unchecked, we'll analyze all the files in the
> workspace when they're changed (by the pydev builder) and not only if
> there's an editor open for that file (so, usually it's not recommended as
> it can be a resource hog, but if you do have CPU/RAM to spare, it's still
> an option).
>
> As for getting completions for functions/classes that haven't been
> imported, I think I don't quite follow what you mean (you do have
> context-insensitive code-completion which would add the import and the
> token -- but apparently, that's not what you meant), so, can you rephrase
> that to explain better your use case?
>
> Cheers,
>
> Fabio
>


Re-reading I'm not sure I was clear on the analyze files... what I meant
was that we do code-analysis on files that haven't been opened in an editor
(the indexing is done for all files regardless of that setting -- so, if
the file is under the PYTHONPATH, it should always be indexed and kept up
to date with a builder).

Cheers,

Fabio

Re: [Pydev-code] Has the analyze only open editors setting ever had a meaning?

[Fabio Z. <fa...@gm...>]

On Wed, Sep 24, 2014 at 9:25 AM, Andreas Pakulat <an...@fr...>
wrote:

> Hi,
>
> I recently stumbled about the 'Builder' page and its 'Analyze only open
> editors' setting. It sounded like disabling this would help one of our
> customers who wanted to get completion for functions in modules that are
> not
> yet imported. Unfortunately it turns out this preference is not being used
> anywhere in the codebase and looking at the existing pydev tags has never
> been used.
>
> I'm wondering wether I'm missing something or wether this has really been
> added (to the ui) and then never used (by the builder)?
>
> On a related note: Is there a way to get pydev to create completions for
> functions/classes in files that haven't been opened yet (after starting
> eclipse)? (i.e. where do I have to look into the codebase to find the
> starting point)
>
> Hi Andreas,

Actually, that's still used... if you take a look at the code, the getter
which uses the ANALYZE_ONLY_ACTIVE_EDITOR constant is
org.python.pydev.builder.PyDevBuilderPrefPage.getAnalyzeOnlyActiveEditor().

What it does is that if it's unchecked, we'll analyze all the files in the
workspace when they're changed (by the pydev builder) and not only if
there's an editor open for that file (so, usually it's not recommended as
it can be a resource hog, but if you do have CPU/RAM to spare, it's still
an option).

As for getting completions for functions/classes that haven't been
imported, I think I don't quite follow what you mean (you do have
context-insensitive code-completion which would add the import and the
token -- but apparently, that's not what you meant), so, can you rephrase
that to explain better your use case?

Cheers,

Fabio

[Pydev-code] PyDev 3.8.0 Released

[Fabio Z. <fa...@gm...>]

What is PyDev?
---------------------------

PyDev is an open-source Python IDE on top of Eclipse for Python, Jython and
IronPython development.

It comes with goodies such as code completion, syntax highlighting, syntax
analysis, code analysis, refactor, debug, interactive console, etc.

Details on PyDev: http://pydev.org
Details on its development: http://pydev.blogspot.com


What is LiClipse?
---------------------------

LiClipse is a PyDev standalone with goodies such as support for Multiple
cursors, theming and a number of other languages such as Django Templates,
Kivy Language, Mako Templates, Html, Javascript, etc.

It's also a commercial counterpart which helps supporting the development
of PyDev.

Details on LiClipse: http://brainwy.github.io/liclipse/


Release Highlights:
-------------------------------

* **Important**: PyDev requires Eclipse 3.8 or 4.3 onwards and Java 7! For
older versions, keep using PyDev 2.x (use LiClipse:
http://brainwy.github.io/liclipse for a PyDev standalone with all
requirements bundled).

* **Debugger**

    * It's now possible to **attach debugger to running process in Windows
and Linux** (open debug perspective > PyDev > Attach to Process)

* pep8 upgraded to 1.5.7
* Fixed issue in dialog shown when PyDev editor is opened which could lead
to closing the IDE.
* Selecting PyQT API version using sip.setapi no longer fails in debug mode
(PyDev-452).
* Code completion tries to get docstring definition from class before
evaluating property (PyDev-412).
* Internal error error when parsing file with wrong syntax:
java.lang.ClassCastException for invalid dict (PyDev-411).
* runfile was restored in pydevconsole (Ctrl+Alt+Enter is working again).
* **Variables** and **Expressions** views working again when debugging
interactive console (PyDev-446).
* Pressing Shift to debug with Ctrl+F9 test runner now properly works in
Linux (PyDev-444).
* Fixed interpreter configuration when the interpreter prints something
before actually running interpreterInfo.py (PyDev-448).
* Fixed NullPointerException when debugging file without extension.


Cheers,

--
Fabio Zadrozny
------------------------------------------------------
Software Developer

LiClipse
http://brainwy.github.io/liclipse

PyDev - Python Development Environment for Eclipse
http://pydev.org
http://pydev.blogspot.com

[Pydev-code] Has the analyze only open editors setting ever had a meaning?

[Andreas P. <an...@fr...>]

Hi,

I recently stumbled about the 'Builder' page and its 'Analyze only open 
editors' setting. It sounded like disabling this would help one of our 
customers who wanted to get completion for functions in modules that are not 
yet imported. Unfortunately it turns out this preference is not being used 
anywhere in the codebase and looking at the existing pydev tags has never 
been used.

I'm wondering wether I'm missing something or wether this has really been 
added (to the ui) and then never used (by the builder)?

On a related note: Is there a way to get pydev to create completions for 
functions/classes in files that haven't been opened yet (after starting 
eclipse)? (i.e. where do I have to look into the codebase to find the 
starting point)

Andreas

-- 
Andreas Pakulat sq...@fr...
froglogic GmbH - Automated UI and Web Testing

[Pydev-code] PyDev 3.7.0 Released

[Fabio Z. <fa...@gm...>]

What is PyDev?
---------------------------

PyDev is an open-source Python IDE on top of Eclipse for Python, Jython and
IronPython development.

It comes with goodies such as code completion, syntax highlighting, syntax
analysis, code analysis, refactor, debug, interactive console, etc.

Details on PyDev: http://pydev.org
Details on its development: http://pydev.blogspot.com


What is LiClipse?
---------------------------

LiClipse is a PyDev standalone with goodies such as support for Multiple
cursors, theming and a number of other languages such as Django Templates,
Kivy Language, Mako Templates, Html, Javascript, etc.

It's also a commercial counterpart which helps supporting the development
of PyDev.

Details on LiClipse: http://brainwy.github.io/liclipse/


Release Highlights:
-------------------------------

* **Important**: PyDev requires Eclipse 3.8 or 4.3 onwards and Java 7! For
older versions, keep using PyDev 2.x (use LiClipse:
http://brainwy.github.io/liclipse for a PyDev standalone with all
requirements bundled).

* **Minimap**

    * Minimap is enabled by default.
    * The minimap now shows content based on the outline.
    * It's possible to customize the minimap selection color.
    * Fixed issue where the background in the minimap could have a part
with a different color until the image was fully redrawn.
    * Scrollbars hidden by default.

* **Editor**

    * Auto code-completion on all letter chars is enabled by default.

* **Debugger**

    * Merged debugger code with the PyCharm fork.
    * Fix the wrong signature of stackless.get_schedule_callback.
    * Breakpoints work in Django templates (requires the LiClipse:
http://brainwy.github.io/liclipse/ html/django editor to work).
    * Gevent debugging (must be enabled in the debugger preferences page).
    * Faster debugging when dealing with huge dicts/sets/lists/tuples.
    * QThreads can be debugged (for remote debugging, 'import pydevd' must
be done before any user code is executed for it to work).

* **Interactive Console**

    * Output is gotten asynchronously.
    * It's possible to interrupt the console.

* **Others**

    * Autopep8 now works with non ascii sources.
    * More than 20 levels of indentation no longer causes
ArrayOutOfBoundsException.
    * Fixed some NullPointerExceptions.
    * A bunch of other bugfixes.


Cheers,

--
Fabio Zadrozny
------------------------------------------------------
Software Developer

LiClipse
http://brainwy.github.io/liclipse

PyDev - Python Development Environment for Eclipse
http://pydev.org
http://pydev.blogspot.com

Re: [Pydev-code] celery errors in eclipse

[Fabio Z. <fa...@es...>]

Hi,

Just to note, this mailing list related to pydev development (not user
questions).

The proper channel for this would be creating an entry in stackoverflow.com
(and adding a 'pydev' tag in the entry).

There's already a post there which may get you going:
http://stackoverflow.com/questions/2112715/how-do-i-fix-pydev-undefined-variable-from-import-errors

Best Regards,

Fabio


On Wed, Jun 18, 2014 at 7:24 AM, xeon <xeo...@gm...> wrote:

> I am using celery in my program to invoke remote functions using a
> message queueing service (RabbitMQ).
>
> I call my function with celery with this:
> myfunc.apply_async(queue=cluster, args=(chain, cluster, )), but although
> the call is correct and it works, in eclipse I get the error that
> "undefined variable from import: apply_async".
>
> This happens, because to celery methods it is just need to append celery
> methods to my function, and not code them.
> That is true that I didn`t define apply_async function, nor imported. I
> just use it like celery docs suggests. Eclipse can`t see this.
>
> The celery community say that it is eclipse python linter causing the
> issue and they suggest to contact the pydev community regarding the matter.
>
> How I make this error disappears in the eclipse?
>
>
> --
> Thanks,
>
>
>
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> pydev-code mailing list
> pyd...@li...
> https://lists.sourceforge.net/lists/listinfo/pydev-code
>

[Pydev-code] celery errors in eclipse

[xeon <xeo...@gm...>]

I am using celery in my program to invoke remote functions using a 
message queueing service (RabbitMQ).

I call my function with celery with this: 
myfunc.apply_async(queue=cluster, args=(chain, cluster, )), but although 
the call is correct and it works, in eclipse I get the error that 
"undefined variable from import: apply_async".

This happens, because to celery methods it is just need to append celery 
methods to my function, and not code them.
That is true that I didn`t define apply_async function, nor imported. I 
just use it like celery docs suggests. Eclipse can`t see this.

The celery community say that it is eclipse python linter causing the 
issue and they suggest to contact the pydev community regarding the matter.

How I make this error disappears in the eclipse?


-- 
Thanks,

Re: [Pydev-code] Why are classes packaged into a jar inside the jar

[Andreas P. <an...@fr...>]

Hi Fabio,

I'll rebase the changes and create a pull request tomorrow.

Andreas

On 2014-05-22 20:53, Fabio Zadrozny wrote:
> Can you provide a patch against the latest version in development for me 
> to test? If everything works and I can find no issues, I can change
> it to work like that...
>
> Cheers,
>
> Fabio
>
> On Tue, May 20, 2014 at 4:43 PM, Andreas Pakulat <an...@fr...> 
> wrote:
>
>> Hi Fabio,
>>
>> just for your information, I also changed the other plugins now for 2.8 
>> and
>> 3.1 and pushed the branches to my clone:
>>
>> https://github.com/apaku/Pydev/tree/2.8.2_with_sdk [1]
>> https://github.com/apaku/Pydev/tree/3.1.0_with_sdk [2]
>>
>> Seems to work just fine here in Eclipse and makes exploring PyDev API a 
>> lot
>> easier.
>>
>> Andreas
>>
>> On 2014-05-17 17:44, Andreas Pakulat wrote:
>> > Hi Fabio,
>> >
>> > The change (based on 2.8.2 since thats what we currently use, so was
>> > easier
>> > to try out) for creating source packages and an sdk feature is at:
>> >
>> > https://github.com/apaku/Pydev/tree/build_src_packages [3]
>> >
>> > Based on that I changed the com.python.pydev.debug package to contain 
>> the
>> > class files directly inside the plugin jar (instead of creating another
>> > jar
>> > inside that) and created a branch for that as well:
>> >
>> > https://github.com/apaku/Pydev/tree/c.p.p.debug_no_jar_in_jar [4]
>> >
>> > Andreas
>> >
>> > On 2014-05-16 17:40, Fabio Zadrozny wrote:
>> >> Hi Andreas,
>> >>
>> >> Do you have the change you did on github so that I can take a look on
>> >> what'd change?
>> >>
>> >> On Fri, May 16, 2014 at 7:38 AM, Andreas Pakulat 
>> <an...@fr...>
>> >> wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> I was exploring how to get an 'sdk' bundle set up for PyDev and have 
>> the
>> >>> necessary source plugins and features now. Unfortunately it seems 
>> that
>> >>> Eclipse does not cope very well with the way PyDev plugins setup 
>> their
>> >>> classes. In particular having the class files inside a jar thats 
>> itself
>> >>> packed into the actual plugin jar does not allow Eclipse to
>> >>> automatically
>> >>> connect class files and sources.
>> >>>
>> >>> I've adjusted one of the plugins to not create such a jar-in-a-jar 
>> and
>> >>> for
>> >>> that plugin Eclipse can lookup sources for the classes of the plugin
>> >>> just
>> >>> fine.
>> >>>
>> >>> However before creating a pull request that changes this in all 
>> plugins
>> >>> I
>> >>> wanted to check wether there's a particular reason for doing this 
>> that
>> >>> I'm
>> >>> not seeing.
>> >>>
>> >>> Andreas
>> >>>
>> >>> --
>> >>> Andreas Pakulat sq...@fr...
>> >>> froglogic GmbH - Automated UI and Web Testing
>> >>>
>> >>>
>> >>>
>> >>> 
>> ------------------------------------------------------------------------------
>> >>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For 
>> FREE
>> >>> Instantly run your Selenium tests across 300+ browser/OS combos.
>> >>> Get unparalleled scalability from the best Selenium testing platform
>> >>> available
>> >>> Simple to use. Nothing to install. Get started now for free."
>> >>> http://p.sf.net/sfu/SauceLabs [5] [1]
>> >>> _______________________________________________
>> >>> pydev-code mailing list
>> >>> pyd...@li...
>> >>> https://lists.sourceforge.net/lists/listinfo/pydev-code [6] [2]
>> >>
>> >>
>> >>
>> >> Links:
>> >> ------
>> >> [1] http://p.sf.net/sfu/SauceLabs [5]
>> >> [2] https://lists.sourceforge.net/lists/listinfo/pydev-code [6]
>> >>
>> >>
>> >>
>> >> 
>> ------------------------------------------------------------------------------
>> >> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>> >> Instantly run your Selenium tests across 300+ browser/OS combos.
>> >> Get unparalleled scalability from the best Selenium testing platform
>> >> available
>> >> Simple to use. Nothing to install. Get started now for free."
>> >> http://p.sf.net/sfu/SauceLabs [5]
>> >>
>> >> _______________________________________________
>> >> pydev-code mailing list
>> >> pyd...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/pydev-code [6]
>>
>> --
>> Andreas Pakulat sq...@fr...
>> froglogic GmbH - Automated UI and Web Testing
>>
>> 
>> ------------------------------------------------------------------------------
>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>> Instantly run your Selenium tests across 300+ browser/OS combos.
>> Get unparalleled scalability from the best Selenium testing platform 
>> available
>> Simple to use. Nothing to install. Get started now for free."
>> http://p.sf.net/sfu/SauceLabs [5]
>> _______________________________________________
>> pydev-code mailing list
>> pyd...@li...
>> https://lists.sourceforge.net/lists/listinfo/pydev-code [6]
>
>
>
> Links:
> ------
> [1] https://github.com/apaku/Pydev/tree/2.8.2_with_sdk
> [2] https://github.com/apaku/Pydev/tree/3.1.0_with_sdk
> [3] https://github.com/apaku/Pydev/tree/build_src_packages
> [4] https://github.com/apaku/Pydev/tree/c.p.p.debug_no_jar_in_jar
> [5] http://p.sf.net/sfu/SauceLabs
> [6] https://lists.sourceforge.net/lists/listinfo/pydev-code
>
> 
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform 
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
>
> _______________________________________________
> pydev-code mailing list
> pyd...@li...
> https://lists.sourceforge.net/lists/listinfo/pydev-code

-- 
Andreas Pakulat sq...@fr...
froglogic GmbH - Automated UI and Web Testing

Re: [Pydev-code] Why are classes packaged into a jar inside the jar

[Fabio Z. <fa...@es...>]

Can you provide a patch against the latest version in development for me to
test? If everything works and I can find no issues, I can change it to work
like that...

Cheers,

Fabio


On Tue, May 20, 2014 at 4:43 PM, Andreas Pakulat <an...@fr...>wrote:

> Hi Fabio,
>
> just for your information, I also changed the other plugins now for 2.8 and
> 3.1 and pushed the branches to my clone:
>
> https://github.com/apaku/Pydev/tree/2.8.2_with_sdk
> https://github.com/apaku/Pydev/tree/3.1.0_with_sdk
>
> Seems to work just fine here in Eclipse and makes exploring PyDev API a lot
> easier.
>
> Andreas
>
> On 2014-05-17 17:44, Andreas Pakulat wrote:
> > Hi Fabio,
> >
> > The change (based on 2.8.2 since thats what we currently use, so was
> > easier
> > to try out) for creating source packages and an sdk feature is at:
> >
> > https://github.com/apaku/Pydev/tree/build_src_packages
> >
> > Based on that I changed the com.python.pydev.debug package to contain the
> > class files directly inside the plugin jar (instead of creating another
> > jar
> > inside that) and created a branch for that as well:
> >
> > https://github.com/apaku/Pydev/tree/c.p.p.debug_no_jar_in_jar
> >
> > Andreas
> >
> > On 2014-05-16 17:40, Fabio Zadrozny wrote:
> >> Hi Andreas,
> >>
> >> Do you have the change you did on github so that I can take a look on
> >> what'd change?
> >>
> >> On Fri, May 16, 2014 at 7:38 AM, Andreas Pakulat <an...@fr...
> >
> >> wrote:
> >>
> >>> Hi,
> >>>
> >>> I was exploring how to get an 'sdk' bundle set up for PyDev and have
> the
> >>> necessary source plugins and features now. Unfortunately it seems that
> >>> Eclipse does not cope very well with the way PyDev plugins setup their
> >>> classes. In particular having the class files inside a jar thats itself
> >>> packed into the actual plugin jar does not allow Eclipse to
> >>> automatically
> >>> connect class files and sources.
> >>>
> >>> I've adjusted one of the plugins to not create such a jar-in-a-jar and
> >>> for
> >>> that plugin Eclipse can lookup sources for the classes of the plugin
> >>> just
> >>> fine.
> >>>
> >>> However before creating a pull request that changes this in all plugins
> >>> I
> >>> wanted to check wether there's a particular reason for doing this that
> >>> I'm
> >>> not seeing.
> >>>
> >>> Andreas
> >>>
> >>> --
> >>> Andreas Pakulat sq...@fr...
> >>> froglogic GmbH - Automated UI and Web Testing
> >>>
> >>>
> >>>
> >>>
> ------------------------------------------------------------------------------
> >>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> >>> Instantly run your Selenium tests across 300+ browser/OS combos.
> >>> Get unparalleled scalability from the best Selenium testing platform
> >>> available
> >>> Simple to use. Nothing to install. Get started now for free."
> >>> http://p.sf.net/sfu/SauceLabs [1]
> >>> _______________________________________________
> >>> pydev-code mailing list
> >>> pyd...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/pydev-code [2]
> >>
> >>
> >>
> >> Links:
> >> ------
> >> [1] http://p.sf.net/sfu/SauceLabs
> >> [2] https://lists.sourceforge.net/lists/listinfo/pydev-code
> >>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> >> Instantly run your Selenium tests across 300+ browser/OS combos.
> >> Get unparalleled scalability from the best Selenium testing platform
> >> available
> >> Simple to use. Nothing to install. Get started now for free."
> >> http://p.sf.net/sfu/SauceLabs
> >>
> >> _______________________________________________
> >> pydev-code mailing list
> >> pyd...@li...
> >> https://lists.sourceforge.net/lists/listinfo/pydev-code
>
> --
> Andreas Pakulat sq...@fr...
> froglogic GmbH - Automated UI and Web Testing
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> pydev-code mailing list
> pyd...@li...
> https://lists.sourceforge.net/lists/listinfo/pydev-code
>