Back to working on a local Python setup and got a quick refresher on something easy to forget My pytest coverage config (in pyproject.toml) wasn’t being picked up in VSCode. CLI? Perfect. VSCode? Different story. Everything looked right… and it was. The catch: VSCode was running pytest from a different working directory and missing the pyproject.toml configuration. Fix: // .vscode/settings.json { "python.testing.cwd": "folder_where_pyproject_is_stored" } Nothing broken — just a good reminder: Same tools, same config… context still matters. #SoftwareTesting #BackendDevelopment #CleanCode #Debugging #Productivity #Python #Pytest #DevEx #DeveloperExperience #Testing
Karilys Collazo’s Post
More Relevant Posts
-
Killpy Launches Unified CLI for Python Environment Cleanup 📌 Killpy revolutionizes Python dev cleanup by unifying environment deletion across 11 package managers - from Conda to Pipenv - in one CLI. It smartly targets obsolete artifacts while sparing active setups, slashing disk bloat with zero-risk automation. Perfect for devs drowning in 10–40GB of stale virtual environments. 🔗 Read more: https://lnkd.in/d4n_iGqk #Killpy #Python #Cli #Virtualenvironment #Packagemanager
To view or add a comment, sign in
-
⚠️ Medium Risk Vulnerability Alert! The Claude SDK for Python has a memory tool path validation race condition that allows sandbox escape. This issue is related to API security and can lead to unrestricted resource consumption. It's been patched in version 0.87.0. Stay safe and keep your systems updated! #ClaudeSDK #Python #APIsecurity #OWASP #CVE2026-34452 https://lnkd.in/g26q6ZAn
To view or add a comment, sign in
-
Log 2/100: Telnetting into the Switch Python Library: telnetlib Today, I wrote a script to Telnet into my lab switch, but it kept crashing. After some troubleshooting, I found the exact issue: Python is just too fast. The script kept pasting the username before the switch had even generated the login prompt. The Fix: I added an extra line to the script (read_until) to force Python to wait and read the output until it actually saw the word "login:", and then asked it to paste the username. I applied the same logic to the Password prompt as well. Suddenly, the script started working flawlessly. The Takeaway: Writing the code is the easy part. Anticipating timing issues and making sure the script actually works without breaking in production is the tough part! The scirpts executes the show version command on the switch. Git Hub Repo: https://lnkd.in/gFkfNyWm Git hub Profile: https://lnkd.in/gjJJJQeT #Python #NetworkAutomation #NetDevOps #NetworkEngineering #100DaysOfCode #ArubaCX #CodingJourney
To view or add a comment, sign in
-
-
Follow up to my last post, this is a complete walkthrough of my File Engine, including missing implementation details. 🔺User interacts with the program via interactive text input 🔺User can select to open a file or search a file 🔺All locations of a single file name are shown next to it if searched a directory (current or custom) 🔺O(1) file Lookup 🔺User can select a file to read 🔺All .PDF and .DOCX files are converted to .TXT and all the generated files are stored in the same directory as the original file 🔺The program does it all, quick and accurate. ---- #CPlusPlus #Python #BackendDevelopment #FullStackDeveloper #SoftwareEngineering #SystemDesign #TechProjects #DataStructures #GitHubProjects #BuildInPublic #Engineering #ComputerScience
To view or add a comment, sign in
-
💻 Local vs Server: The Real Python Experience Working on Python projects locally feels easy — everything runs perfectly on your machine. But once you deploy the same code on a company server, reality hits: • Hard-coded paths or environment-specific settings break. • Dependencies installed locally may not exist on the server. • A requirements.txt file becomes mandatory to ensure all packages and versions are installed correctly. ✅ Lesson learned: Local testing is just the beginning — making your code robust, portable, and server-ready is the real challenge. #Python #SoftwareDevelopment #Deployment #ProgrammingTips
To view or add a comment, sign in
-
For the peeps vibing their : be sure careful of the version of your APIs and underlying tools. You need to explicitly specify them as a part of your build plan. Otherwise your favorite LLM may default to something else. For example, I’ve seen python syntax differences and generated code using deprecated versions. Think latent bugs and features disappearing when it used to work. Hoping this saves a few hours of frustration for those in the network.
To view or add a comment, sign in
-
I was able to craft a snap for a Python app called pyfiglet. I was able to follow along using this tutorial -> https://lnkd.in/gJuQjFB2 This involved installing Snapcraft and LXD, defining the package information, troubleshooting target platform. Seeing the result was a great feeling!
To view or add a comment, sign in
-
-
🚀 Shemul v1.0.1 is live from March 20, 2026 Your favorite project-aware CLI for Python just got smoother ⚙️ Organize all your repetitive commands in one place with shemul.json and run them with a clean, simple CLI 💻✨ No more messy scripts. No more forgotten commands. 📦 Install / Update: 👉 https://lnkd.in/gXhn-iSE 🌐 Learn more: 👉 https://lnkd.in/g58VTVDv #Shemul #Python #CLI #DevTools #OpenSource #Automation #STechBD
To view or add a comment, sign in
-
-
🚀 Day 6 of #111DaysOfLearningForChange – Code for Change Built my first CLI-based To-Do App using Python 🧠💻 📌 What I learned today: • File handling using JSON • Structuring a CLI application • Managing state (tasks) with persistent storage • Using match-case for cleaner control flow 🛠️ What I built: A command-line To-Do app with features: • Add tasks • View tasks • Mark tasks as complete ✔️ • Delete tasks • Data stored in a JSON file ✨ Key takeaway: Building projects makes concepts like file handling and control flow much clearer than just theory ⚡ Challenge faced: Handling task IDs and updating data correctly after deletion #111DaysOfLearningForChange #CodeForChange #Python #CLI #Projects #LearningInPublic
To view or add a comment, sign in
-
-
Specially for my dear readers I prepared simple performance test for C and PyPy 🤗 Test is quite simple. It shows that there's no staggering performance gap between machine code compiled from C source and one compiled from Python source. Notice that PyPy test includes compilation time too, so I made two tests for C, one for execution time only and another for both execution and compilation time.
To view or add a comment, sign in
-
Explore content categories
- Career
- Productivity
- Finance
- Soft Skills & Emotional Intelligence
- Project Management
- Education
- Technology
- Leadership
- Ecommerce
- User Experience
- Recruitment & HR
- Customer Experience
- Real Estate
- Marketing
- Sales
- Retail & Merchandising
- Science
- Supply Chain Management
- Future Of Work
- Consulting
- Writing
- Economics
- Artificial Intelligence
- Employee Experience
- Workplace Trends
- Fundraising
- Networking
- Corporate Social Responsibility
- Negotiation
- Communication
- Engineering
- Hospitality & Tourism
- Business Strategy
- Change Management
- Organizational Culture
- Design
- Innovation
- Event Planning
- Training & Development