with PyPy's cpyext.
Cheers,
Nick.
--
Nick Coghlan
Red Hat Infrastructure Engineering Development, Brisbane
___
python-devel mailing list
python-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/python-devel
migration challenge. Does anaconda run on Python
3? Does yum?
It's that delta of Python applications that Fedora ships as required
components in the base OS, but Ubuntu does not, that will potentially
cause problems.
Cheers,
Nick.
--
Nick Coghlan
Red Hat Infrastructure Engineering Development
. For pure
Python code, Armin Ronacher's python-modernize can help flush out
legacy constructs that will fail under Python 3.
Cheers,
Nick.
--
Nick Coghlan
Red Hat Infrastructure Engineering Development, Brisbane
___
python-devel mailing list
python-devel
, not a reason to switch.
It is one of the reasons to switch for me.
One key advantage of Python 3.3+ is drastically reduced memory usage for
applications that deal almost entirely in unicode strings (courtesy of
PEP 393).
Cheers,
Nick.
--
Nick Coghlan
Red Hat Infrastructure Engineering Development
:)
I suspect adding component aliases wouldn't qualify as small,
though, since that's the kind of data model change that has
significant repercussions throughout the UI and query generation system.
Cheers,
Nick.
- --
Nick Coghlan
Red Hat Infrastructure Engineering Development, Brisbane
Testing
-INFO file
at the root, it's likely an sdist, if it doesn't, it's likely a raw
tarball.
Cheers,
Nick.
- --
Nick Coghlan
Red Hat Infrastructure Engineering Development, Brisbane
Testing Solutions Team Lead
Beaker Development Lead (http://beaker-project.org/)
-BEGIN PGP SIGNATURE-
Version
to migrate to wheel
based installation any time soon.
See discussion at
http://mail.python.org/pipermail/distutils-sig/2013-August/022450.html
for more details.
Cheers,
Nick.
- --
Nick Coghlan
Red Hat Infrastructure Engineering Development, Brisbane
Testing Solutions Team Lead
Beaker Development
Python feature releases minor releases usually confuses
people).
Cheers,
Nick.
--
Nick Coghlan
Red Hat Infrastructure Engineering Development, Brisbane
Testing Solutions Team Lead
Beaker Development Lead (http://beaker-project.org/)
___
python-devel
as a guide to what to copy into a fresh venv). If you get
that working, I'd be interested in a Python 3.5 venv and/or ensurepip
patch to do that by default, and only bootstrap from the embedded wheel
if there was no system pip available.
Cheers,
Nick.
--
Nick Coghlan
Red Hat Hosted Shared Services
comments.
Looks good to me from an upstream perspective - making it easier to
support other Python runtimes like PyPy and Jython is a nice added bonus.
Cheers,
Nick.
--
Nick Coghlan
Red Hat Hosted Shared Services
Software Engineering Development, Brisbane
Testing Solutions Team Lead
Beaker
the metadata version field
directly rather than needing to grab the release increment from the RPM
repo. (I think this situation provides a good practical use case for why
it's important to standardise this feature upstream, too).
Cheers,
Nick.
--
Nick Coghlan
Red Hat Hosted Shared Services
Software
/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list
python-devel@lists.fedoraproject.org
https
To download Python 3.4.0 visit:
http://www.python.org/download/releases/3.4.0/
==
Direct link to the What's New guide:
http://docs.python.org/3/whatsnew/3.4.html
Cheers,
Nick.
--
Nick Coghlan
Red Hat Hosted Shared Services
Software Engineering Development, Brisbane
Testing
On 03/17/2014 05:53 PM, Nick Coghlan wrote:
Direct link to the What's New guide:
http://docs.python.org/3/whatsnew/3.4.html
Rereading that, I remembered there's more to it for Fedora than just
hey, here's a shiny new version of Python 3 to be packaged, and I
don't mean the stuff Slavek
committed yesterday just by doing
`dnf update`.
I actually mentioned this in my recent SciPy keynote, on the grounds
that scientists may want to play around with the new matrix
multiplication operator without having to build Python from source :)
Cheers,
Nick.
--
Nick Coghlan
Red Hat Hosted Shared
This is also the part of the PEP most likely to break things, so
figuring out a way to test it in Fedora before it makes it into an
upstream CPython release would be a good idea...
Cheers,
Nick.
--
Nick Coghlan
Red Hat Hosted Shared Services
Software Engineering Development, Brisbane
HSS
rawhide would be wonderful. The patch is at last passing
Python's own test suite, so it shouldn't have broken anything too
dramatically.
Cheers,
Nick.
--
Nick Coghlan
Red Hat Hosted Shared Services
Software Engineering Development, Brisbane
HSS Provisioning Architect
to
announce this? python-announce-list?
You can get away with a lot on python-ideas, and you're likely to find
folks potentially interested in playing around with it there.
Cheers,
Nick.
--
Nick Coghlan
Red Hat Hosted Shared Services
Software Engineering Development, Brisbane
HSS Provisioning
to integrate it
nicely with COPR, or even tidy up the implementation to the point where
we can convince Clark to accept the feature as part of mock itself :)
Regards,
Nick.
--
Nick Coghlan
Red Hat Hosted Shared Services
Software Engineering Development, Brisbane
HSS Provisioning Architect
, rebuilding for an SCL could
be very cool. The How do we rebuild/repackage our dependencies? was
actually one of the problems we ran into when considering using SCLs
rather than putting up with running in an older version of Python.
Cheers,
Nick.
--
Nick Coghlan
Red Hat Hosted Shared Services
would definitely help with
future cleanups like those.
I'm not an approved packager myself, but there are some folks on the app
devel teams that I could potentially interest in that (e.g. Dan
Callaghan adopted the TG1 stack for EPEL 7, as we still need it for Beaker).
Cheers,
Nick.
--
Nick
for the things it
can automatically derive).
Regards,
Nick.
--
Nick Coghlan
Red Hat Hosted Shared Services
Software Engineering Development, Brisbane
HSS Provisioning Architect
___
python-devel mailing list
python-devel@lists.fedoraproject.org
https
,
Nick.
--
Nick Coghlan
Red Hat Hosted Shared Services
Software Engineering Development, Brisbane
HSS Provisioning Architect
___
python-devel mailing list
python-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/python-devel
On 4 Dec 2014 00:59, Donald Stufft don...@stufft.io wrote:
On Dec 3, 2014, at 9:51 AM, Nick Coghlan ncogh...@gmail.com wrote:
- (This is not really related to the switch, but more of a general
remark) In [4], it says that python 3 version of the executable gains a
python3- prefix
On 4 December 2014 at 23:10, Bohuslav Kabrda bkab...@redhat.com wrote:
- Original Message -
On Thu, Dec 04, 2014 at 12:51:40AM +1000, Nick Coghlan wrote:
On 4 Dec 2014 00:38, Bohuslav Kabrda bkab...@redhat.com wrote:
- (This is not really related to the switch, but more
if their dependencies aren't available in
Python 3 yet.
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list
python-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/python-devel
the default for the time being and instead
focus on enabling explicitly opting in to Python 3 in EPEL
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list
python-devel@lists.fedoraproject.org
https
opting in to running in the system Python
rather than explicitly running in Python 3.
Regards,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list
python-devel@lists.fedoraproject.org
https
On 28 January 2015 at 03:32, Toshio Kuratomi a.bad...@gmail.com wrote:
On Tue, Jan 27, 2015 at 10:50:07PM +1000, Nick Coghlan wrote:
What if, instead, we were able to add a new macro that let folks
*explicitly* opt in to running in the system Python, but then define
the recommended spec file
On 27 February 2015 at 11:02, Toshio Kuratomi a.bad...@gmail.com wrote:
On Feb 25, 2015 3:14 PM, Nick Coghlan ncogh...@gmail.com wrote:
For those not following along with the FPC ticket, Toshio and Tomspur
have a nice write-up of the options at
https://etherpad.mozilla.org/2Uqk0ikCll
I
On 5 February 2015 at 17:48, Nick Coghlan ncogh...@gmail.com wrote:
On 4 February 2015 at 21:01, Bohuslav Kabrda bkab...@redhat.com wrote:
- Original Message -
I don't really feel strongly about this, I agree that your solution has a
merit (and syspython *is* better than default_python
On 18 Jun 2015 10:02 pm, Matej Stuchlik mstuc...@redhat.com wrote:
We feel that that's perhaps a little tight schedule, where things could
go wrong easily. For that reason we'd like stay with Python 3.4 as system
python for Fedora 23, while providing Python 3.5 in a Copr. (Perhaps using
Miro's
as Python 3 maintainer to push it forward.
Regards,
Nick.
P.S. Miro's nightly SCLs at
https://copr.fedoraproject.org/coprs/churchyard/python3-nightly/ may
also have a part to play, although I'm not sure what that would be
just yet
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
a clearer entry point for Pythonistas already familiar with
Python's packaging tools into the RPM ecosystem.
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list
python-devel
On 11 June 2015 at 14:05, Jason L Tibbitts III ti...@math.uh.edu wrote:
NC == Nick Coghlan ncogh...@gmail.com writes:
NC I agree it doesn't make sense to include that information in the
NC Python packaging guidelines, but I think it does make sense to
NC provide such recommendations
the Python 3 as default
change, but didn't see anything.
Was there something there and I just missed it, or does something need
to be written up and passed to the folks responsible for creating the
release notes?
Regards,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
On 14 July 2015 at 21:19, Miro Hrončok mhron...@redhat.com wrote:
I would like to thank all the contributors, who are helping us with
this. We are working on a special Fedora Badge for this Python 3 effort [4].
Thanks for the update, and I love the badge idea!
Cheers,
Nick.
--
Nick Coghlan
etadata 1.2 spec [1]
While dropping the suffix entirely seems like a potentially attractive
option to me, it may also be ambiguous as to whether it's referring to
import package names (eg. "python2(pkg_resources)") or distribution
package names (e.g. "python2(setuptools)"
On 23 September 2015 at 02:54, Jason L Tibbitts III <ti...@math.uh.edu> wrote:
>>>>>> "NC" == Nick Coghlan <ncogh...@gmail.com> writes:
>
> NC> I just noticed that the packaging policy doesn't currently mention
> NC> dist-info directories, o
with the upstream metadata
generation?
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list
python-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/python-devel
model
adopting for the python3X releases in EPEL means there's a chance to
rebase the "default" version of other packages each time "X" is
incremented. While that won't be a big difference for the python34 and
python35 stacks, there will presumably be more significant v
gt; added a switch for those who want pythonXdist() Provides, but it is
> opt-in rather than opt-out. The option is only for distributions that
> intend to carry only one Python runtime per major version.
Very cool, thank you!
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com
On 11 Aug 2016 23:48, "Petr Viktorin" wrote:
>
> Hello,
> As of now, http://fedora.portingdb.xyz shows that we are 50% done porting
Fedora packages to Python 3. This is a big magic milestone; if you're
looking for a reason to celebrate, this is it! :)
Very cool!
> Now,
s to have a "tox" section in the
sidebar at
https://developer.fedoraproject.org/tech/languages/python/python-installation.html
that covers using these COPR builds with tox for cross-version
testing?
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list
python-devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/python-devel@lists.fedoraproject.org
le, it's just generating a new one based on the new
upstream metadata and the old supplemental metadata, and seeing if the
result still passes CI.
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
pyth
at to
me, and I see from https://fedoraproject.org/wiki/Category:ChangeAnnounced
that it's already been announced on fedora-devel.
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list -- python-devel@lists.fe
On 8 February 2017 at 13:44, Tadej Janež <tade...@nez.si> wrote:
> Nick,
>
> thanks for your thorough answer.
>
> On Mon, 2017-02-06 at 20:07 +0100, Nick Coghlan wrote:
>>
>> It's not specific to Fedora's Python 3 packaging as such, but it *is*
>> specific t
th '--upgrade' option.
This, on the other hand, is why having the system site-packages
visible is discouraged in general - it really is more complicated than
using an environment that only shares that standard library and the
language runtime.
Cheers,
Nick.
--
Nick Coghlan | nc
in most cases it's not what they
> should be doing (`pip install --user` is usually more appropriate).
>
> What do you think?
I guess when you're building an RPM you're not typically running as
root either, so standard RPM builds would still be fine. So +1 from
me.
Cheers,
Nick.
--
Nick Coghl
On 1 September 2016 at 22:04, Avram Lubkin <av...@rockhopper.net> wrote:
>
> On Thu, Sep 1, 2016 at 7:44 AM, Nick Coghlan <ncogh...@gmail.com> wrote:
>>
>>
>> The ideal point we'd like to get to is one where all distro provided
>> scripts a
ys.path, and then defining a custom path_hook to process it:
https://docs.python.org/3/reference/import.html#path-entry-finders
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list
python-
stream as an amendment to the distro recommendations in
PEP 394.
The nice thing about the design of pythonmux is that, if Python 2 is
installed, it will use it automatically in non-interactive mode for
maximum compatibility with existing scripts, but if only Python 3 is
available, it will implicitl
e contributed
> to the package's git.
+1 that sounds like an excellent idea :)
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list
python-devel@lists.fedoraproject.org
https://lis
On 3 October 2016 at 23:36, Tomas Orsava <tors...@redhat.com> wrote:
> On 09/27/2016 08:43 AM, Nick Coghlan wrote:
>>>
>>> P.P.S. I realize rh-python34 is available on RHSCL, but it didn't seem to
>>> support "python3" in scripts...
>&g
On 4 November 2016 at 02:16, Charalampos Stratakis <cstra...@redhat.com> wrote:
> And FESCo ticket about that[0]
>
> [0] https://pagure.io/fesco/issue/1642
Awesome, thanks for tackling this.
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Bris
ndencies (e.g. requirements.txt) are
intended for deployment rather than redistribution, and hence can (and
usually should) pin the exact combination of dependencies that was
tested.
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
in early December.
Regards,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
On 18 October 2016 at 00:49, Charalampos Stratakis <cstra...@redhat.com> wrote:
> The current URL should be https://beaker.qa.fedoraproject.org/ if that is the
> one you have in mind.
Indeed it is, thank you!
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisban
run that on the Red Hat internal instance instead)
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
m suggesting "Some libraries,
applications and operating system interfaces may not work correctly."
as that's literally the answer to "Why isn't the C locale allowed by
default anymore?".
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
an Python 3, so Armin did make some initial
attempts to get it working in the C locale on both 2 & 3. However, he
eventually gave the latter up as unsupportable and the error makes it
clear that "I don't need to support ASCII based locales on Python 3"
is a key
TF-8", 1);
}
(Plus error checking and the warning on stderr that this was being done)
I guess the next step would be for me to try this in a local clone,
and see what happens when running "LANG=C ./python -m regrtest" as
well as when running click.
Cheers,
Nick.
On 12 December 2016 at 19:59, Tomas Orsava <tors...@redhat.com> wrote:
> On 12/12/2016 05:39 AM, Nick Coghlan wrote:
>> On 11 December 2016 at 01:33, Donald Stufft <don...@stufft.io> wrote:
>> The benefit of that approach is that it would not only solve the
>
blindly upgrading everything
in --user can easily break previously working setups.
So if we wanted to offer this, it would likely need to be as a
standalone (pip installable?) script that was equivalent to the above
bash snippet.
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | B
On 12 December 2016 at 20:37, Petr Viktorin <pvikt...@redhat.com> wrote:
> On 12/10/2016 02:56 PM, Nick Coghlan wrote:
>> I also have an upstream motive for suggesting this, though: if we do
>> this in the more constrained environment of "Fedora users" an
On 15 December 2016 at 21:17, Toshio Kuratomi <a.bad...@gmail.com> wrote:
> On Mon, Dec 12, 2016 at 1:39 AM, Nick Coghlan <ncogh...@gmail.com> wrote:
>> I don't anticipate any major concerns with downstream redistributors
>> adding this behaviour, as the main thing
ner image atop a RHEL or
CentOS container host rather than running directly on the host.
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
en make sense to start using the "Local version identifier" feature
in PEP 440 to expose RPM release numbers to Python level tooling:
https://www.python.org/dev/peps/pep-0440/#local-version-identifiers
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
__
ady has to
getentropy.
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
/4197 but figured I should raise it here
as well, as if something like this was added, then Fedora could be updated
to use a standard symlink map when building RPMs, and the developer portal
could be updated with suggest `pip.conf` settings to use the system cert
bundle by default.
Cheers,
Nick.
-
On 24 December 2016 at 02:38, John Dulaney <jdula...@fedoraproject.org>
wrote:
> On Fri, Dec 23, 2016 at 05:37:51PM +1000, Nick Coghlan wrote:
>
> > I filed that idea on the pip issue tracker at
> > https://github.com/pypa/pip/issues/4197 but figured I should rai
delegation today:
https://mail.python.org/pipermail/python-dev/2017-April/147796.html
So with any luck, we should be able to get this change explicitly
approved by upstream within the next couple of weeks.
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
rovements to packaging collaboration across the RPM-based distros are
always going to get a big thumbs up from me :)
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list -- python-devel@lists.f
initions available to older EL releases).
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
On 11 August 2017 at 17:34, Nick Coghlan <ncogh...@gmail.com> wrote:
> The relocated "default Python module" proposal is at
> https://docs.pagure.org/fedora-python.fedora-python/default-python-module.html
>
> I'm not super fond of that auto-generated URL, nor do I lik
On 2 August 2017 at 21:34, Nick Coghlan <ncogh...@gmail.com> wrote:
> While working on
> https://fedoraproject.org/wiki/User:Ncoghlan/Default_python_module, I
> started getting annoyed at the lack of decent review and commenting
> features in MediaWiki, so prompted by
> ht
ator of
where to focus efforts if the goal is to make the tests more
efficient.
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe se
On 20 July 2017 at 16:12, Bohuslav Kabrda <bkab...@redhat.com> wrote:
> On Thu, Jul 20, 2017 at 7:51 AM, Nick Coghlan <ncogh...@gmail.com> wrote:
>> * checking for refleaks means we can't run parallel tests across
>> multiple processes. If we were to move refleak testi
any currently unqualified
description and files sections
A script like that may even do a tolerable job for packages that *do*
offer Python 3 subpackages (since those will already have qualifiers,
and will necessarily appear after any unqualified runtime and build
requirements for the
prefix and %py3_prefix), and either
leave the latter undefined for systems with no native Py3 stack, or
else set it to rely on EPEL, IUS, or a suitable software collection.
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
__
d a "sudo
make install" from the main Python development branch will mess with
the default symlinks if you didn't set a suitable `/opt/` prefix).
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list -
> /usr/lib. Because the components are modular and bundled in a non-RPM
> compatible fashion, it behooves developers to use a tool to segregate
> the tools as much as feasible from the Fedora underlying
> infrastructure. i.e., use pyvenv to build them in a contained
> environment
On 27 April 2017 at 23:04, Daniel P. Berrange <berra...@redhat.com> wrote:
> On Thu, Apr 27, 2017 at 04:32:09PM +1000, Nick Coghlan wrote:
>> Their approach means that any harm caused by "sudo pip install X" can
>> subsequently be fully reversed
ing the PEP 376 metadata.
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
les?
3. Would we allow daisy chaining of these private venvs via *.pth
files? (see https://github.com/berdario/pew#add)
4. How would we make this manageable across Fedora/EPEL/SCLo spec files?
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
ainer would *prevent* you from
including any regular userspace Python components - you'd only be able
to include the ones built specifically for that stream.
Does that approach sound sufficiently plausible to folks that I can
use it to provide feedback to the folks working on the modularity
tooling
On 15 August 2017 at 19:44, Nick Coghlan <ncogh...@gmail.com> wrote:
> So I decided to set up a build on ReadTheDocs instead, and that looks
> to have just worked, including the logo rendering:
> https://fedora-python.readthedocs.io/en/latest/
I couldn't get Pagure's webhooks t
any paths that would
later prove to be an absolute deal-breaker for updating the distro
level recommendations.
Cheers,
Nick.
[1] https://github.com/leapp-to/prototype/issues/126
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
pyt
ently change LC_CTYPE to the more
sensible setting.
The accepted version of the PEP upstream *only* sets LC_CTYPE, so the
chance of unintended side effects from the coercion is much lower that
it was with the approach that made the F26 Beta cut-off (which also
sets LANG).
Cheers,
Nick.
--
Nick Cog
On 2 June 2017 at 18:46, Nick Coghlan <ncogh...@redhat.com> wrote:
> On Fri, Jun 2, 2017 at 1:15 PM, Zbigniew Jędrzejewski-Szmek
> <zbys...@in.waw.pl> wrote:
>> It seems that right solution, that would work while the builders are
>> still not F26, would be to con
nstall directory to /usr/local in a way that "pipsi" detects)
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
On 1 May 2017 at 22:47, Nico Kadel-Garcia <nka...@gmail.com> wrote:
> On Sun, Apr 30, 2017 at 10:30 PM, Nick Coghlan <ncogh...@gmail.com> wrote:
>> If the intended benefit of this change remains unclear, it may help to
>> focus on a specific concrete case, which
the installed-via-pip versions easier to
identify even without checking the PEP 376 installation metadata)
Cheers,
Nick.
[1]
https://www.slideshare.net/ncoghlan_dev/developing-in-python-on-red-hat-platforms-devnation-2016
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
On 24 August 2017 at 19:02, Petr Viktorin <pvikt...@redhat.com> wrote:
> On 08/24/2017 10:13 AM, Nick Coghlan wrote:
>> My current thinking based on that discussion is that we're actually
>> going to need a module set that looks like this for F28+:
>>
>> * Platfor
On 21 August 2017 at 19:53, Petr Viktorin <pvikt...@redhat.com> wrote:
> On 08/18/2017 12:06 PM, Nick Coghlan wrote:
>> I couldn't get Pagure's webhooks to work properly (see
>> https://pagure.io/pagure/issue/2522), so revising the revised plan:
>> could someone with th
On 21 August 2017 at 19:46, Petr Viktorin <pvikt...@redhat.com> wrote:
> On 08/18/2017 01:38 PM, Nick Coghlan wrote:
>> Does that approach sound sufficiently plausible to folks that I can
>> use it to provide feedback to the folks working on the modularity
>> toolin
On 24 August 2017 at 21:28, Petr Viktorin <pvikt...@redhat.com> wrote:
> On 08/24/2017 12:22 PM, Nick Coghlan wrote:
>>> Stream names match the Platform module. We follow its policy here, even
>>> when
>>> it changes.
>>
>> Oh, interesting, I had tha
On 29 August 2017 at 19:33, Petr Viktorin <pvikt...@redhat.com> wrote:
> On 08/25/2017 10:23 AM, Nick Coghlan wrote:
>> Traditionally, that would have meant that we wouldn't get a Fedora
>> based Python 3.7 container out the door until the release of Fedora 29
>> in O
PR to fix that:
https://github.com/python/cpython/pull/4565
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to pytho
named
https://fedoraproject.org/wiki/Packaging:Python#Example_common_spec_file -
that is the setup.py based build process, but it isn't currently obvious
that `pyX_build` and `pyX_install` assume the use of a setup.py file.
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Austr
1 - 100 of 110 matches
Mail list logo