** Description changed:

  When creating a new project by selecting "Project -> Version Control ->
  New from repository..." in a remote Subversion repository that contains
  a Python project, Eric fails to automatically identify the source files
  as Python, and places them all into the "Others" category in the Project
  Viewer.
  
  Then, in this view, all the files remain in a status in which it is not
  possible to rename, delete from the project or delete the file (the
  options are disabled). This means that there is no way to move them to
  the appropriate "Sources" view, except by manually adding them into this
  category but then having them all duplicated into the "Others" tab.
  
  If one would then create the project manually from an existing checkout
- (working copy) of a project, then there will be no possibility to use
- the VCS feature, since the program does not have any possibility to put
- an existing project into an existing version control system except by
+ (working copy) of a project, then there will be no chance to use the VCS
+ feature, since the program does not have any possibility to put an
+ existing project into an existing version control system except by
  creating a new repository.
  
  The only way around this is to create the project manually and not using
  the version control feature at all.
  
  The package is Eric v4.1.1-ubuntu1, in Ubuntu Hardy.
  Version Numbers:
    Python 2.5.2
    Qt 4.4.0
    PyQt4 4.3.3
    sip 4.7.3
    QScintilla 2-snapshot-20070923
    eric4 4.1.1 (r1972)
  
  Platform: linux2
  2.5.2 (r252:60911, Apr 21 2008, 11:12:42) 
  [GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)]

** Tags added: eric ide python repository subversion svn

-- 
Creating new project from svn repository does not identify Python sources
https://bugs.launchpad.net/bugs/251769
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to