![]() ![]()
#Visual studio vs visual studio code for python full#I also sent off for an 'HP Prime G2' and a 'TI-nspire CX-II CAS' this morning when I read they were both going to incorporate the full Python interpreter in an upcoming firmware update.Whether you’re brand new to learning Python or are in need of a home to write your Python code, choosing a code editor to get started with can be a tough decision. Once I am comfortable with the basics then I will have a look at whatever dialect of Python it is (perhaps 'microPython'?) the Casio calculators support and see how that lends itself to common mathematical problems-basic things like a programme to solve quadratic equations or perform iteration would be an obvious starting point. I thought in order to become accustomed to Python I would transcribe the more useful of these scripts into the new language. In regards projects I have written many, many Perl scripts over the years to help automate common command-line tasks such as A/V encoding and tagging, the parsing of eBooks and so on. I can see how this keeps you focussed on the task at hand but does seem a slightly odd approach when one is very used to VisualStudo or (peripherally in my case!) the various Borland programming suites. The system also appears to keep at least one project open at all times and you do not close projects and open others but simply switch between them. ![]() At first this is somewhat frustrating, but once you are familiar with the required syntax I can imagine that process offers a great deal of power. For instance you seem to have to hand-edit your project file to get the debugger running properly. One thing I simultaneously like about VSC, while also being somewhat intimidated by is the depth of granularity it has and the immediate control over things you are given. It seems alongside VSC that 'Pycharm' has a large following so I will clearly have to investigate that further as well!!! Therefore I wonder if anyone could give me their perspective on whether it is 'better'/more convenient to learn and programme in Python using 'Visual Studio Code' or rather stick to 'Visual Studio 2017/2019'? Absolutely any advice would be most gratefully received.ĮDIT: Many thanks indeed to everyone who has commented so far. ![]() Critical to this discussion, VSC also offers an official (MS-maintained) Python expansion and I have read many posts/comments that praise this combination. However it is also rather granular and requires some familiarity with hand-editing its workspace and debugging definitions before you can get down to programming. ![]() A little exploration has shown this to be an extremely capable programmer's text editor that incorporates many of the ease-of-use features which make the fully-fledged VS so attractive. However I have also recently become aware of the-somewhat confusingly named-'Visual Studio Code'. However, by all accounts the native Python support in VS is now excellent and of course comes within an environment to which I am already very familiar. #Visual studio vs visual studio code for python install#Previously you were forced to install 'PTVS' to achieve the same end and what little experimentation I made with this plug-in was not entirely satisfactory. I already own a licence for 'Visual Studio 2017 Enterprise' ( not the 2019 release as it has been some time since I have felt the desire to programme, although I may pick up a new Enterprise licence if the bug really grabs me again.) That suite now comes as standard with a Python IDE integrated into its larger structure. When properly starting out with Python I wanted to do so in the best, or at least most convenient way. However I never managed to find a really rock-solid IDE and graphical Debugger that I liked for Perl and this is something I have regretted over the years. I know it is entirely feasible to programme with nothing more than a basic text editor and the Python interpreter package, using 'PDB' as a console debugger. However, Casio recently added Python support to their graphical calculators and I thought I would use this impetus to finally knuckle down to Python! Accordingly I have been looking at IDE's. #Visual studio vs visual studio code for python how to#Sadly on every occasion I sat down to make a positive start I was quickly persuaded that anything I might want to do with Python I already knew how to do in much more comfort using Perl. Perhaps because of this I have never learned Python, although I have tried to do so many times. I have done so entirely as a hobbyist with the luxury to dabble as I chose in the programmes that interested me most at the time. I have been programming in BASIC, Assembler, C/C++, and Perl for more than forty years when it comes to the older languages. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |