<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>RStudio on Firas Sadiyah</title>
    <link>https://firas.phd/tags/rstudio/</link>
    <description>Recent content in RStudio on Firas Sadiyah</description>
    <image>
      <title>Firas Sadiyah</title>
      <url>https://firas.phd/favicon.png</url>
      <link>https://firas.phd/favicon.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 23 Jan 2024 14:57:54 +0000</lastBuildDate>
    <atom:link href="https://firas.phd/tags/rstudio/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using reticulate in RStudio with pyenv</title>
      <link>https://firas.phd/posts/pyenv_rstudio/</link>
      <pubDate>Wed, 28 Apr 2021 00:00:00 +0000</pubDate>
      <guid>https://firas.phd/posts/pyenv_rstudio/</guid>
      <description>&lt;p&gt;When developing in Python, it is generally a good practice not to rely on the Python version that ships with the operating system (OS). This is to ensure that the system version of Python remains relatively &amp;lsquo;clean&amp;rsquo; for the OS processes. In addition, by installing a custom version(s) of Python, we open many possibilities. For one, it gives us control over which specific version(s) to use in our projects, and two, by using a virtual environment manager, we ensure that each project has access to its own tailored list of packages. One way of achieving this is by using &lt;a href=&#34;https://github.com/pyenv/pyenv&#34;&gt;pyenv&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
