[ann] Pythonid plugin released

Hello everyone,

Pythonid, the plugin providing support of the Python language in IntelliJ
IDEA, has finally been released. You can download it from the Plugin Manager.
(The version which was available yesterday did not download properly because
of the plugin repository problems: if you downloaded it and it did not work,
please try again now.)

The plugin is currently compatible only with IDEA 5.1.x. Demetra compatibility
will be provided in the next build of Demetra.

The plugin is open-source, and the source code is available at http://pythonid.dev.java.net.
People willing to contribute to the plugin development are very much welcome;
if you're interested, please contact me to discuss the details.

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


6 comments
Comment actions Permalink

Pythonid, the plugin providing support of the Python language in
IntelliJ IDEA, has finally been released.

Very nice, thank you :).

The plugin is currently compatible only with IDEA 5.1.x. Demetra
compatibility will be provided in the next build of Demetra.

The plugin is open-source, and the source code is available at
http://pythonid.dev.java.net. People willing to contribute to the plugin
development are very much welcome; if you're interested, please contact
me to discuss the details.

Maybe a few words about the infrastructure :). IMHO:
- the bug tracker should be on jetbrains JIRA (like many other plug-ins already do :) ), not
on dev.java.net .
- The same about the forums/discussion lists: on the jetbrains lists is much more faster and
comfortable :).
- a better package name would be better: at the moment the plug-in is called "1548.jar(zip)" :).
- a build.xml would help allot.
- it could be monitored/build by the Team Server demo installation ?

Thanks in advance,

Ahmed.



0
Comment actions Permalink

Hello Ahmed,

The download file name is currently determined by the plugin repository,
not by the plugin developer. I'll see what we can do to improve this.

As for build.xml and automated build - doing this cleanly would require packaging
openapi.jar and idea.jar into the plugin distrubution, which is not allowed
by the license and not a good idea in general. I'm not using anything outside
of the "extended API", but the extended API does live in idea.jar.

As for tracker and mailing list: it doesn't seem to be possible to disable
individual project services on dev.java.net. It's possible that we'll move
away from dev.java.net entirely, but before that, setting up a second issue
tracker on jetbrains.net in addition to the one at dev.java.net would only
confuse people.

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"

>> Pythonid, the plugin providing support of the Python language in
>> IntelliJ IDEA, has finally been released.
>>
AM> Very nice, thank you :).
AM>
>> The plugin is currently compatible only with IDEA 5.1.x. Demetra
>> compatibility will be provided in the next build of Demetra.
>>
>> The plugin is open-source, and the source code is available at
>> http://pythonid.dev.java.net. People willing to contribute to the
>> plugin development are very much welcome; if you're interested,
>> please contact me to discuss the details.
>>
AM> Maybe a few words about the infrastructure :). IMHO:
AM> - the bug tracker should be on jetbrains JIRA (like many other
AM> plug-ins already do :) ), not
AM> on dev.java.net .
AM> - The same about the forums/discussion lists: on the jetbrains lists
AM> is much more faster and
AM> comfortable :).
AM> - a better package name would be better: at the moment the plug-in
AM> is called "1548.jar(zip)" :).
AM> - a build.xml would help allot.
AM> - it could be monitored/build by the Team Server demo installation ?
AM> Thanks in advance,
AM>
AM> Ahmed.
AM>


0
Comment actions Permalink

The download file name is currently determined by the plugin repository,
not by the plugin developer. I'll see what we can do to improve this.

Well, the problem is not that much about the name that is used in the repository,
but about the name in the /config/plugins/ : from time to time, one needs to
do manually cleanup, and having numbers doesn't help. All the other plug-ins
use however their names(e.g. tostring-plugin.jar , junitgen.jar etc.)

As for build.xml and automated build - doing this cleanly would require
packaging openapi.jar and idea.jar into the plugin distrubution, which
is not allowed by the license and not a good idea in general. I'm not
using anything outside of the "extended API", but the extended API does
live in idea.jar.

I don't understand why should those files be "distributed". I only mean
to build that in an automated way - nothing more.
I also thought that this should not be a problem on your own server :).

As for tracker and mailing list: it doesn't seem to be possible to
disable individual project services on dev.java.net. It's possible that
we'll move away from dev.java.net entirely, but before that, setting up
a second issue tracker on jetbrains.net in addition to the one at
dev.java.net would only confuse people.

I don't think so, because:
1. you don't need to deactivate the tracker and the lists on dev.java.net (just don't use them).
2. the users won't be confused, because in the plug-in descriptor, you can specify
the correct locations. Just look at http://plugins.intellij.net/plugin/?id=631
At the moment there is:
Bugtracker: https://pythonid.dev.java.net/servlets/ProjectIssues
Forum: https://pythonid.dev.java.net/servlets/ProjectMailingListList
You could simply change that to the correct Jetbrains services.

Thanks in advance,

Ahmed.

0
Comment actions Permalink

Hello Ahmed,

>> The download file name is currently determined by the plugin
>> repository, not by the plugin developer. I'll see what we can do to
>> improve this.
>>
AM> Well, the problem is not that much about the name that is used in the
repository,
AM> but about the name in the /config/plugins/ : from time to time, one needs
to
AM> do manually cleanup, and having numbers doesn't help. All the other plug-ins
AM> use however their names(e.g. tostring-plugin.jar , junitgen.jar
AM> etc.)

All the other plugins were downloaded from the old repository.

The new repository has now been fixed to preserve the file names of the uploaded
plugins.

>> As for build.xml and automated build - doing this cleanly would
>> require packaging openapi.jar and idea.jar into the plugin
>> distrubution, which is not allowed by the license and not a good idea
>> in general. I'm not using anything outside of the "extended API", but
>> the extended API does live in idea.jar.
>>
AM> I don't understand why should those files be "distributed". I only mean
AM> to build that in an automated way - nothing more.
AM> I also thought that this should not be a problem on your own
AM> server :).

To build something in an automated way, it's necessary to provide all build
dependencies in an automated way. One of the dependencies for Pythonid is
idea.jar. I don't quite see a simple way to provide this automatically (downloading
idea-xxxx.zip from download.jetbrains.com hardly seems to be an optimal way).

And our own server runs standard Ant scripts - I don't think anyone would
be happy to have a build.xml that's buildable by our server but not by anything
else.

>> As for tracker and mailing list: it doesn't seem to be possible to
>> disable individual project services on dev.java.net. It's possible
>> that we'll move away from dev.java.net entirely, but before that,
>> setting up a second issue tracker on jetbrains.net in addition to the
>> one at dev.java.net would only confuse people.
>>
AM> I don't think so, because:
AM> 1. you don't need to deactivate the tracker and the lists on
AM> dev.java.net (just don't use them).
AM> 2. the users won't be confused, because in the plug-in descriptor,
AM> you can specify
AM> the correct locations. Just look at
AM> http://plugins.intellij.net/plugin/?id=631
AM> At the moment there is:
AM> Bugtracker: https://pythonid.dev.java.net/servlets/ProjectIssues
AM> Forum: https://pythonid.dev.java.net/servlets/ProjectMailingListList
AM> You could simply change that to the correct Jetbrains services.

I can change that, but I can't change the links that are shown on the http://pythonid.dev.java.net/
. So people coming to that page will be confused.

AM> Thanks in advance,
AM>
AM> Ahmed.
AM>
--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"




0
Comment actions Permalink

>>> The download file name is currently determined by the plugin
>>> repository, not by the plugin developer. I'll see what we can do to
>>> improve this.
>>>

AM> Well, the problem is not that much about the name that is used in
the repository,
AM> but about the name in the /config/plugins/ : from time to time, one
needs to
AM> do manually cleanup, and having numbers doesn't help. All the other
plug-ins
AM> use however their names(e.g. tostring-plugin.jar , junitgen.jar
AM> etc.)

All the other plugins were downloaded from the old repository.

The new repository has now been fixed to preserve the file names of the
uploaded plugins.

OK, thank you.


>>> As for build.xml and automated build - doing this cleanly would
>>> require packaging openapi.jar and idea.jar into the plugin
>>> distrubution, which is not allowed by the license and not a good idea
>>> in general. I'm not using anything outside of the "extended API", but
>>> the extended API does live in idea.jar.
>>>

AM> I don't understand why should those files be "distributed". I only mean
AM> to build that in an automated way - nothing more.
AM> I also thought that this should not be a problem on your own
AM> server :).

To build something in an automated way, it's necessary to provide all
build dependencies in an automated way. One of the dependencies for
Pythonid is idea.jar. I don't quite see a simple way to provide this
automatically (downloading idea-xxxx.zip from download.jetbrains.com
hardly seems to be an optimal way).

Well, if this is the problem, than I suppose one should be allowed use the jars
from it's licensed version if IntelliJ for automated plug-in builds too.

And our own server runs standard Ant scripts - I don't think anyone
would be happy to have a build.xml that's buildable by our server but
not by anything else.

Well, shouldn't they be generic/configurable? :).


>>> As for tracker and mailing list: it doesn't seem to be possible to
>>> disable individual project services on dev.java.net. It's possible
>>> that we'll move away from dev.java.net entirely, but before that,
>>> setting up a second issue tracker on jetbrains.net in addition to the
>>> one at dev.java.net would only confuse people.
>>>

AM> I don't think so, because:
AM> 1. you don't need to deactivate the tracker and the lists on
AM> dev.java.net (just don't use them).
AM> 2. the users won't be confused, because in the plug-in descriptor,
AM> you can specify
AM> the correct locations. Just look at
AM> http://plugins.intellij.net/plugin/?id=631
AM> At the moment there is:
AM> Bugtracker: https://pythonid.dev.java.net/servlets/ProjectIssues
AM> Forum: https://pythonid.dev.java.net/servlets/ProjectMailingListList
AM> You could simply change that to the correct Jetbrains services.

I can change that, but I can't change the links that are shown on the
http://pythonid.dev.java.net/ . So people coming to that page will be
confused.

IMHO not. On that page (http://pythonid.dev.java.net/), one can state with bold that
for bugs and discussions what URLs to use :).

Ahmed.

0
Comment actions Permalink

>>>> As for tracker and mailing list: it doesn't seem to be possible to
>>>> disable individual project services on dev.java.net. It's possible
>>>> that we'll move away from dev.java.net entirely, but before that,
>>>> setting up a second issue tracker on jetbrains.net in addition to the
>>>> one at dev.java.net would only confuse people.
>>>>
>> AM> I don't think so, because:
>> AM> 1. you don't need to deactivate the tracker and the lists on
>> AM> dev.java.net (just don't use them).
>> AM> 2. the users won't be confused, because in the plug-in descriptor,
>> AM> you can specify
>> AM> the correct locations. Just look at
>> AM> http://plugins.intellij.net/plugin/?id=631
>> AM> At the moment there is:
>> AM> Bugtracker: https://pythonid.dev.java.net/servlets/ProjectIssues
>> AM> Forum: https://pythonid.dev.java.net/servlets/ProjectMailingListList
>> AM> You could simply change that to the correct Jetbrains services.
>>
>> I can change that, but I can't change the links that are shown on the
>> http://pythonid.dev.java.net/ . So people coming to that page will
>> be confused.

IMHO not. On that page (http://pythonid.dev.java.net/), one can state
with bold that
for bugs and discussions what URLs to use :).

Well? Any news on this? (a project for pythonid in the jetbrains JIRA?)

I would really like to submit many issues, but the dev.java.net it's even
worse than a plain simple "issues.txt" file :).

Thanks in advance,

Ahmed.

0

Please sign in to leave a comment.