Historical Downloads
Jun 02, 2019 iX Developer 2.4. Configure operator panels and PC operated control applications. 4.0 (6 votes) 2.40.44 Beijer Electronics AB. Review Comments Questions & Answers Update program info. Old versions. IX Developer 2.2 iX Developer 2.1 iX Developer 2.0. No specific info about version 2.4.
We're constantly shipping new versions since 2007! If you really need historical packages you'll find them below, however definitely consider upgrading to the latest and greatest.
Show all versions
SonarQube 7.7
March 20, 2019 - Quality Gate in Pull Requests, Injection Flaw rules for PHP & BitBucket Server supportCommunity EditionSonarQube 7.6
January 28, 2019 - Drop of modules, simplification of Quality Gates, taint detection in collectionsCommunity EditionSonarQube 7.5
December 20, 2018 - Scala and Apex analysis, enhanced security reports & new language rulesCommunity EditionSonarQube 7.4
October 29, 2018 - Ruby and open-sourced VB.NET analysis, import of issues from 3rd-party Roslyn analyzersCommunity EditionSonarQube 7.3
August 13, 2018 - Support for Kotlin and CSS languages, detection of Security HotspotsCommunity EditionSonarQube 7.2.1
June 19, 2018 - Analysis of Go code, detection of SQL injections, analysis of pull requestsCommunity EditionSonarQube 7.1
April 17, 2018 - Homepage selection, project badges, new webhooks console, 'New Code' measures without SCMSonarQube 7.0
February 2, 2018 - Live update of project measures and quality gate status, read-only built-in 'Sonar way' quality gateSonarQube 6.6
October 20, 2017 - New Measures page, 'Edit Quality Profile' permission, enhanced 'Projects Management' page, notification for failed background tasks, authentication for WebhooksSonarQube 6.5
August 3, 2017 - Show leak on Projects space, understand the history of a project, read-only built-in quality profiles with highlighting on 'Sonar way' ones, onboarding for new usersSonarQube 6.4
June 2, 2017 - Tag of projects, enhanced 'Projects' page with more details/filters and with visualisations, efficient UX for issue multiple locations, private vs. public projectsSonarQube 6.3.1
April 12, 2017 - Project Activity page, remove noise on the leak period for newly activated rules, embed SonarPHP and SonarPython and SonarFlexSonarQube 6.2
December 14, 2016 - New Projects page, consolidated coverage, webhooks, authentication by HTTP header, rating support in Quality GatesSonarQube 6.1
October 13, 2016 - Redesign of the Settings domain, improvements on the project home page, first steps towards clusteringSonarQube 6.0
August 4, 2016 - Tracking of file move/renaming, better management of quality profiles and new rules, “Project Creator” permissionSonarQube 5.6.7
September 25, 2017 - Leak concept, SonarQube Quality Model, increased Scalability and Security, and always more Developer-Oriented FeaturesSonarQube 5.5
May 3, 2016 - New SonarQube Quality Model, new Measures project page, Compute Engine in a dedicated processSonarQube 5.4
March 9, 2016 - New “Code” page, “My Account” space, cross-module duplications, OAuth API for Identity providersSonarQube 5.3
January 3, 2016 - New project homepage, cross-project duplication, access tokensSonarQube 5.2
November 2, 2015 - Scanners no longer access the database, “My New Issues” notification, technical debt displayed in Issues pageSonarQube 5.1.2
July 27, 2015 - UI refresh, issues tags, auto-assignment of issues, new Rules page, Java 7+ support onlySonarQube 5.0.1
February 24, 2015 - New Issues page, Git/SVN built-in support, end of Maven 2 supportSonarQube 4.5.7
April 8, 2016 - SQALE Rating and Technical Debt Ratio, active severity filter and display of remediation functions for rules pageSonarQube 4.4.1
September 26, 2014 - Management of rule templates and custom rules, new Component Viewer, improved multi-language support, built-in Web Service API pageSonarQube 4.3
July 31, 2014 - Quality Gate concept replacing Alert concept. Technical Debt UX integration.SonarQube 4.2
March 26, 2014 - Multi-language support, tags for rules, new visual measure filter representationsSonarQube 4.1.2
February 20, 2014 - Tracking added technical debt, Elasticsearch integration, Bubble Chart, new “Administer Issue” permissionSonarQube 4.0
November 7, 2013 - Technical debt based on SQALE model, issue exclusion/inclusion, code coverage exclusion, project provisioning, end of support of WAR modeSonarQube 3.7.4
December 20, 2013 - Bulk change for issues, ability to save/edit issues filters, new permissions to run analyses, bulk update of project permissionsSonarQube 3.6.3
August 14, 2013 - Search engine & changelog for violations, tracking of new coding rules, highlighting of variables/functions in source code viewerSonarQube 3.5.1
April 13, 2013 - Tracking of unit tests, new rules on unit tests, new exclusion settings, enhanced email notificationsSonarQube 3.4.1
January 8, 2013 - New service to query measures, ability to compare projects, list of recent projects, alerts on measure variationsSonarQube 3.3.2
November 21, 2012 - Support of modules with different languages, overall coverage by unit and integration tests, enhanced file exclusions, new Java rulesSonarQube 3.2.1
October 3, 2012 - Technical debt based on SQALE model, issue exclusion/inclusion, code coverage exclusion, project provisioning, end of support of WAR modeSonarQube 3.1.1
June 25, 2012 - Global dashboards, rules for unit testsSonarQube 3.0.1
May 14, 2012 - Encryption of database password, TimeMachine available as widgets, 40 new bugsSonarQube 2.14
March 19, 2012 - Detection of cross-project duplications, user information from third-party systems, email notification on new violationsSonarQube 2.13.1
January 31, 2012 - New search engine, ability to change severity, group reviews by action plans, new widgets to track project activitySonarQube 2.12
November 30, 2011 - Support Java7 projects, new hotspot widgets, improve detection of duplicationsSonarQube 2.11
October 3, 2011 - Encryption of database password, TimeMachine available as widgets, 40 new bugsSonarQube 2.1
August 18, 2011 - Encryption of database password, TimeMachine available as widgets, 40 new bugsSonarQube 2.9
July 18, 2011 - Improve manual code reviews, track Quality Profile changesSonarQube 2.8
May 19, 2011 - Manual code review, analysis of Ant multi-modules projects, new tool to compare Quality profilesSonarQube 2.7
April 1, 2011 - Coverage of recently changed code, better integration of SCM Activity pluginSonarQube 2.6
February 18, 2011 - Ant task and Java standalone task to analyze projectsSonarQube 2.5
January 14, 2011 - Differential views, tracking of violations through time, new coding rules for Java projectsSonarQube 2.4.1
November 14, 2010 - Customizable dashboards, update center, architecture rules for Java projectsSonarQube 2.3.1
October 22, 2010 - Export/import Quality profiles, allow multiple configuration of the same coding ruleSonarQube 2.2
July 15, 2010 - User favourites, user filters to define its own queriesSonarQube 2.1.2
May 20, 2010 - Search for project usage/dependencies, new rules to detect unused Java private/protected methodsSonarQube 2.0
March 10, 2010 - Chidamber and Kemerer Metrics, Dependency Structure MatrixSonarQube 1.12
December 7, 2009 - Wrapping-up 1.x seriesSonarQube 1.0.2
December 14, 2007 - Where it all started!
Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upHave a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
commented Sep 14, 2016
enough said. |
added this to the 0.20.0 milestone Sep 14, 2016
This was referenced Sep 14, 2016
Open
Closed
commented Sep 15, 2016 • edited
edited
What is the suggested replacement for the deprecated .ix ? Is it .loc ?For me .ix works 5-10% faster than .loc :BTW, passing a list into the indexer adds another 25-50% overhead: |
commented Sep 15, 2016
yes .loc and .iloc are the expected replacements. Timings are expected to eventually be faster, though a single sub-millisecond access difference is pretty meaningless in any real usecase. |
commented Sep 15, 2016
@jreback Having terabytes of data and processing it with a help of Dask DataFrame which uses Pandas DataFrames as chunks turns 'milliseconds' into minutes... |
commented Sep 15, 2016
@frol doesn't matter how much data you have. you are almost certainly ineffeciently using indexing operations. |
commented Sep 15, 2016
@frol the indexing code paths are going to be rewritten in C/C++ as part of the pandas 2.0 effort, so the microperformance should improve by a factor of 10 or more. Some refactoring or Cythonization may be able to give some quick perf wins in .loc or .iloc |
commented Sep 15, 2016
Question on .ix deprecation-- suppose you want to set the first row of a DataFrame in a particular column with a value (assume that the index is not an Int64Index). Then you can currently use: df.ix[0, 'colname'] = 5 In the future can you safely do: df.iloc[0].loc['colname'] = 5 (this seems to beg for SettingWithCopyWarning)? Or is the only proper option going to be df.loc[df.index[0], 'colname'] = 5 ? |
commented Sep 15, 2016
Our experience has been that mixing positional and label indexing has been a significant source of problems for users. Here you might want to do df['colname'][0] |
commented Sep 15, 2016 • edited
edited
unambigously safe setting (may be better syntactically nicer in 2.0) or |
commented Sep 15, 2016
@jreback Thanks, makes sense. |
commented Dec 25, 2016 • edited
edited
@jreback I think you have a typo with square brackets used instead of parens? should be |
commented Dec 26, 2016
@johne13 yes that was a typo, thanks! |
added a commit to jreback/pandas that referenced this issue Jan 11, 2017
DEPR: deprecate .ix in favor of .loc/.iloc
added a commit to jreback/pandas that referenced this issue Jan 11, 2017
DEPR: deprecate .ix in favor of .loc/.iloc
added a commit to jreback/pandas that referenced this issue Jan 12, 2017
DEPR: deprecate .ix in favor of .loc/.iloc
added a commit to jreback/pandas that referenced this issue Jan 12, 2017
DEPR: deprecate .ix in favor of .loc/.iloc
referenced this issue Jan 12, 2017
ClosedDEPR: deprecate .ix in favor of .loc/.iloc #15113
added a commit to jreback/pandas that referenced this issue Jan 12, 2017
DEPR: deprecate .ix in favor of .loc/.iloc
referenced this issue Jan 12, 2017
ClosedReindex versus ix gotchas documentation text does not match example code #15116
added a commit to jreback/pandas that referenced this issue Jan 12, 2017
DEPR: deprecate .ix in favor of .loc/.iloc
added a commit to jreback/pandas that referenced this issue Jan 12, 2017
DEPR: deprecate .ix in favor of .loc/.iloc
added a commit to jreback/pandas that referenced this issue Jan 12, 2017
DEPR: deprecate .ix in favor of .loc/.iloc
added a commit to jreback/pandas that referenced this issue Jan 17, 2017
DEPR: deprecate .ix in favor of .loc/.iloc
added a commit to jreback/pandas that referenced this issue Jan 18, 2017
DEPR: deprecate .ix in favor of .loc/.iloc
closed this in 99afdd9
Jan 18, 2017
commented Jan 25, 2017 • edited
edited
This looks like it will be really painful for me. Rather than removing ix entirely, could it be switched to a function with keyword only args? Then I can take a dangerous df.ix[[0,2], ['foo', 'bar']] and in a fairly straightforward fashion convert it into an unambiguous index without having to repeat my index name or us the df.get_loc ? |
commented Jan 25, 2017
@DavidEscott well you are only delaying the inevitable, so you have some choices
no, converting .ix to a function is not possible, its an indexer, eg. ix[ ] , which is syntactically different. |
commented Jan 25, 2017
@DavidEscott you're more than welcome to monkey-patch in your own function that does what you want. Since .ix has been a significant source of bugs and user problems, we no longer wish to support it |
added a commit to AnkurDedania/pandas that referenced this issue Mar 21, 2017
DEPR: deprecate .ix in favor of .loc/.iloc
added a commit to ajcr/100-pandas-puzzles that referenced this issue May 11, 2017
referenced this issue Jun 13, 2017
ClosedPandas .ix indexer is deprecated #224
This was referenced Jun 26, 2017
Closed
Merged
commented Jan 27, 2018
@wesm I understand that this is not an easy function to maintain, but still I find it unfortunate as it was a VERY expressive way to manipulate DataFrames... I hope someone will be able to make a code snippet to replace ix via monkey-patching? |
commented Jun 6, 2018
I just found a use case that makes ix quite valuable to me. I have a Dataframe df such that df['mask'] is a boolean mask that I'd like to filter df on. With ix , I can do df[df.mask,:n] to get the first n columns, filtered by mask . Now the best way seems to be df.loc[df.mask,:].iloc[:,:3] , which just reads terribly. Using df.get_loc as an indexing workaround feels very kludgy whereas the ix solution made for elegant code.Of course I can assign a temporary df2 = df.loc[df.mask] and work from there, but that's inelegant as well. |
commented Jun 7, 2018
@JonathanTay To support the boolean indexing case with first-n-columns, in addition to df.loc[df.mask, :].iloc[:, :n] you can use the (perhaps prettier, although same length) df.iloc[df.mask.values, :n] or df.loc[df.mask, df.columns[:n]] Yes it's 7 more characters than df.ix[df.mask, :n] but generally not having to worry about subtle bugs from .ix inference is worth the typing. |
commented Jul 17, 2018 • edited
edited
Can .ix can be replaced by an .loc chained with an .iloc , or a simple .loc and .iloc ?If so, why not have a wrapper around this and keep backward compatibility, and a useful method? |
commented Jul 18, 2018
@ManuelLevi The issue is, each call can be replaced with .iloc, .loc, or a combination, but there's no good way for .ix to tell which to use.E.g. if you provide a DataFrame with the Index([0, 2, 4, 6, 8]), and call .ix[:4] on it. Did you want .ix to implicitly use .iloc (returning the first 4 elements) or .loc (returning the first 3 elements)? |
commented Jul 20, 2018
@Liam3851 I see what you mean. I usually use .iloc and .loc combined, but the impact this will have is greater than me. I believe it impacts all the pandas' community.A quick search for df.ix on GitHub shows almost 4M results. Maybe half a million notebooks and almost 200k python files will break after this. Many of these opensource tutorials and libraries people are counting on.Could there be a simple way to change the function behaviour instead of removing it? Maybe assume integers to always be locations, and other types to always be a label? |
commented Jul 20, 2018
This is such a great feature, would be a shame to get it lost... Please consider some of the suggestions above as a way to ease maintenance |
commented Jul 20, 2018
@ManuelLevi As I understand it, ix treats anything that could be a label, as a label. This was a source of bugs. For example, if a Series s is indexed by integers [5,3,2,4], then should s.ix[0] return the 0th element or raise KeyError? What if s.index = ['a','b','c'] or [0,1,2,3]? @Liam3851 has a point that the bugs and unexpected behaviour just keep coming once you allow the ambiguity. For example, label based indexing (loc) takes both end points, while position-based (iloc) takes the start but not the end. |
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment