This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 257333 - Create New Project does not respect selected default Python platform
Summary: Create New Project does not respect selected default Python platform
Status: CLOSED WORKSFORME
Alias: None
Product: python
Classification: Unclassified
Component: Platform (show other bugs)
Version: 8.1
Hardware: All All
: P3 normal (vote)
Assignee: Lou Dasaro
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-29 18:52 UTC by jpek
Modified: 2017-06-23 08:06 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Shpws the error (31.83 KB, image/png)
2016-01-09 22:47 UTC, Lou Dasaro 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jpek 2015-12-29 18:52:55 UTC 
The working Python version and path of a program are not the same as selected in Python Platform Manager. The platform selections must be done in Project Properties, but nothing indicates that Platform Manager is a wrong place for these settings.

I suggest an informative text is added to the Platform manager: 
"Note: The project platform must be changed in the project properties window".

(I have lost days because of this problem.)

- By the way, the Help button of Platform Manager rings the bell without any information.
Comment 1 Lou Dasaro 2016-01-09 22:47:47 UTC 
Created attachment 158075 [details]
Shpws the error

Thank you for your report. Anomaly Verified on all OSs. Steps to recreate:
Invoke Tools->Python Platforms and change the default. Click "Close".
Invoke File->New Project->Python Project - Ant
Expected result: The platform shown in the New Project wizard should be the one you chose as default.
Actual result: The default Python Platform is NOT preselected in the New Project wizard.
Click "Manage" to verify...see attachment
Comment 2 Jenselme 2017-06-22 20:07:30 UTC 
I cannot reproduce. I assume this was fixed in the current version or by some late developments. Closing this. If you still have this issue, please reopen and accept my apologies.
Comment 3 Jiri Kovalsky 2017-06-23 08:06:32 UTC 
Thanks for your evaluation Julien. Reporter, if you think your issue is still valid and needs to be addressed, don't hesitate to reopen it with additional information. Closing for now.